Post-merger integration data migration: what to migrate, archive or retire

Decide per system: migrate, archive or retire

Post-merger integration data migration works when every acquired system gets one of three dispositions before anyone builds a field map: migrate it into the platform, archive a complete export, or retire it with sign-off. The detail most plans miss is that a migration normally moves open records and the fields the platform needs. Closed tickets, lost opportunities, finished projects and attachments stay behind and disappear with the source system unless someone decides to archive them.

For buy-and-build teams the stakes rise with every add-on. Each acquired company brings its own email tenant, chat workspace, CRM, accounting file and service desk, often with a decade of history. Switching those systems off is a real synergy. Deleting their history by default is a value leak, because the same history carries legal retention value, diligence value at exit and, increasingly, licensing value. AI developers building agents need records of real work with outcomes attached, the kind of post-training data that exists mostly inside companies.

What to have before the first mapping workshop

Gather these before the integration management office (IMO) books its first session with the acquired company's IT lead and controller.

• A system register for the acquired company: every tool with a login, who pays for it, the admin owner, the first year of records and rough volumes (mailboxes, tickets, accounts, repositories)
• The retention schedules of both companies, plus any litigation holds or regulator requests in force
• The purchase agreement's IP and data representations and, in a carve-out, the transition services agreement with its end dates for shared systems
• Customer contracts with data-use, return or deletion clauses
• Renewal and cancellation dates for every acquired-company subscription, including tools paid on corporate cards
• A named decision owner per system, with legal sign-off reserved for anything marked retire

The three-way rule and its four tests

Run each system through four tests in order. The first decides whether live records migrate; the other three decide whether the history must survive.

1. Operational need. Will the combined business use these records in daily work after cutover? If yes, migrate the live records.
2. Legal and contractual retention. Do tax, employment or industry rules, customer contracts or a litigation hold require the history? If yes, archive at minimum.
3. Diligence and dispute value. Would a future acquirer, auditor or opposing counsel ask for it? Revenue history, customer correspondence and warranty files usually do. If yes, archive.
4. Licensing value. Does it hold several years of the company's own operational records with outcomes attached, such as resolved and escalated tickets, won and lost deals, approved and rejected changes? If yes, archive a full-fidelity export.

Retire a system only when all four tests come back no.

Retention cuts both ways. For businesses covered by California's privacy statute, the notice at collection must state how long each category of personal information is kept, and collection, use and retention must be reasonably necessary and proportionate (Cal. Civ. Code 1798.100 et seq.). Keep-everything is therefore not a safe default for consumer data. Separate business records (tickets, projects, deal history, internal discussion) from consumer personal information, and let counsel set the rule for the second group. This is general information, not legal, tax or financial advice.

How to run the migration step by step

1. Freeze destructive changes on day one. Pause deleting retention policies, workspace closures, plan downgrades and seat cancellations on acquired-company systems until each system has a disposition.
2. Finish the system register within two weeks. Chase the tools that sit on corporate cards or in a founder's name; they are the ones most often cancelled without an export.
3. Score every system in one working session. Put the acquired company's controller, IT lead and one business owner per function in the room and apply the four tests.
4. Sign off dispositions. The IMO lead approves migrations and archives; counsel signs anything marked retire.
5. Specify archive exports. Ask for full-fidelity exports with metadata, thread structure, attachments and user mappings, prove they open without the source application, and store them in company-owned storage with restricted access.
6. Migrate in waves and reconcile. Compare record counts, spot-check histories, and keep the source read-only through at least one month-end close.
7. Retire on a logged date. Record what was deleted, when, and on whose approval.
8. Update the portfolio records map. The exit data room and any later licensing review should start from it; the checklist on data retention before selling a business lists the categories buyers ask for.

The guides on CRM consolidation after an acquisition and ERP consolidation and ledger history go deeper on those two systems.

Common mistakes in PMI data migration

A short message to the acquired company's leadership sets the tone early:

Illustrative example: a managed IT services add-on

Illustrative only; the companies are fictional. Harbor Ridge IT, a fictional managed services platform, acquires a 140-person regional MSP with nine years of history. The integration team applies the four tests:

When the fictional platform screened itself for licensing two years later, the archived ticket history and runbook versions were the records that mattered, and they still existed.

Where licensing fits in the integration plan

Once dispositions are set, the operating partner holds what a licensing screen needs. A combined company or add-on can be a candidate when it is a US business with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license what it holds, and an owner, CEO, CFO or authorized representative willing to sponsor the application. The company fit checker gives a preliminary, non-binding read, and who qualifies sets out the full baseline.

The partner's part stays narrow: introduce the company and pass on basic fit information, never records. SourceX then qualifies the company, the company builds its data inventory, price and terms are agreed, buyers review, and delivery happens only after an executed agreement and the company's authorization. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; no reward is guaranteed. The role is described in referral opportunities for PE operating partners.

Next step

Add a licensing-value column to the disposition sheet before the next add-on retires anything. If the platform or an acquired company passes the screen, register as a partner and make the introduction, or have the CEO apply at sourcex.si/apply with your referral link.