Post-merger integration checklist, with a data asset workstream
A post-merger integration checklist should give every workstream an owner and dates: governance and the IMO, day-one readiness, people, customers, finance, IT and systems, and synergy tracking. Add a data asset workstream that inventories the acquired company's systems, confirms who holds rights to the records, and places a retention hold before any legacy system is retired.
Why integration checklists need a data asset workstream
Integration plans exist to capture synergies, and systems consolidation is a typical source of them: one ERP, one CRM, one email tenant, one ticketing tool. A standard migration moves what operations need, such as open orders, open invoices, active customers and opening balances. The acquired company's history stays in a legacy system that is switched off a few months later.
That history deserves a decision of its own. Years of the acquired company's tickets, project files, email and deal records are the kind of real work records that AI labs and data buyers license. The data asset workstream makes sure someone decides what the history is worth before it is retired, and it applies the same discipline to the platform's own legacy systems.
Use the checklist as written or merge its data asset section into your existing IMO tracker. The data opportunity handoff checklist for an acquisition integration covers the handoff to SourceX in more detail.
Who in the IMO owns legacy data decisions
| IMO role | Owns | Data asset task |
|---|---|---|
| IMO lead | Integration plan, cadence, escalations | Adds the data asset workstream to the charter and the tracker |
| IT integration lead | System consolidation and retirement dates | Maintains the system inventory and enforces the retention hold |
| Finance integration lead | ERP migration, close, reporting | Confirms how much history migrates and where the rest is archived |
| General counsel or deal counsel | Contracts, privacy, purchase agreement terms | Confirms rights to the acquired records and any restrictions on them |
| Functional leads (sales ops, support, engineering) | CRM, ticketing and code migration | Flag records that carry outcomes, such as resolved tickets and closed deals |
| Operating partner | Value creation plan and the sponsor's view | Decides whether to raise licensing with the CEO and makes the introduction |
The checklist
Governance and IMO (pre-close)
- Integration charter approved, with an IMO lead and a steering committee cadence
- Workstream leads named, each with decision rights and a weekly status report
- Synergy targets baselined by workstream, each with an owner
- Risk and issues log opened, including legacy system risks
Day-one readiness
- Legal entity, signing authority and bank access confirmed
- Employee, customer and supplier communications approved
- Email, identity and network access working for day-one users
- Critical vendor and customer contracts reviewed for change-of-control terms
People and organization
- Leadership structure and reporting lines announced
- Retention plans agreed for key staff, including the acquired company's system administrators
- Payroll and benefits harmonization plan agreed
Customers and commercial
- Account ownership and coverage map agreed
- Pricing, contract templates and billing alignment planned
- Customer communications and escalation paths live
Finance and reporting
- Opening balance sheet and purchase accounting underway
- Chart of accounts mapping and a shared close calendar agreed
- Decision recorded on how many years of ERP history migrate
IT and systems
- Application inventory for both companies, with a target state for each system
- Migration sequence and cutover dates agreed
- Decommissioning plan with dates, owners and contract end dates
Data asset workstream
- Inventory: every acquired system listed with its owner, administrator, years of history, export route and renewal date, including archives inherited from the target's own earlier acquisitions
- Rights owner: confirmation of which entity owns the records after closing, and whether any were excluded or carved out in the purchase agreement
- Contributors: a check on material created by contractors; the US Copyright Office's circular on works made for hire explains that work employees create within their jobs belongs to the employer, while contractor work counts as made for hire only in listed categories with a signed agreement, so other contractor material may need a written assignment
- Privacy commitments: every privacy policy and set of terms the acquired company published, with dates; FTC staff have stated that promises not to use customer data for undisclosed purposes, such as training models, are enforceable
- Retention hold: no legacy system decommissioned until a full export is verified and a written keep, archive, license-review or destroy decision is logged
- Screen: the acquired company and the platform each checked against the SourceX baseline: a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to its records and an authorized sponsor
- Decision: the operating partner and CEO decide whether to explore licensing before the first legacy retirement date, and report it through the quarterly board meeting agenda
Synergy tracking and close-out
- Synergy realization reported against baseline every month
- Integration lessons logged for the next add-on
- IMO handover to business-as-usual owners, including the custodian of the legacy archive
This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.
How to use the results
| Result | What it means | Next action |
|---|---|---|
| Inventory complete, rights clear, company meets the baseline | The records may be licensable | The operating partner raises it with the CEO and makes the introduction |
| Inventory complete, rights unclear | Contracts, contractor terms or privacy notices need review | Counsel reviews before any introduction; the retention hold stays on |
| Legacy retirement within 30 days and no verified export | The history is at risk | Pause decommissioning until the export is verified |
| Acquired company small on its own, platform large | The platform's records may be the stronger candidate | Screen the platform, and ask SourceX during qualification how the add-on's history is treated |
| Records mainly belong to clients, or are mostly consumer or health data | Unlikely to be licensable | Record the decision and move on |
Red flags that stop the data asset workstream
- The legacy tenant is already inside its deletion window, or its administrators have left.
- The seller kept the historical records as an excluded asset.
- A transition services agreement controls the systems and ends before an export can be taken; the guide to what happens to data when a TSA ends covers that case.
- The acquired company has already licensed the same data for AI training.
- Nobody at either company can run exports.
How an operating partner makes the introduction
- Confirm that the CEO and the authorized sponsor of the entity that owns the records are open to a conversation.
- Submit the company through your referral link or the referral form, with basic fit information only.
- SourceX qualifies size, history, data breadth and rights, and the company builds a metadata-only data inventory; the IMO's system list is a useful starting point.
- Price and terms are agreed, AI labs and data buyers review, the deal closes and the company is paid; the IMO never sends records to anyone as part of the introduction.
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, and no reward is guaranteed. The operating partner referral page explains the program for sponsors.
Next step
Add the data asset workstream to your IMO tracker before the first decommissioning date is set. When a company passes the screen, register as a partner and draft the CEO's introduction with the introduction email builder. The full criteria are on the who qualifies page, and an incoming finance lead can build the same inventory using the new CFO first 90 days guide.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
When should the data asset workstream start in an integration?
Before closing if possible, and no later than the first IMO planning session. Its main job is to hold legacy systems until their history has been exported and assessed, so it has to exist before the IT workstream sets decommissioning dates. Starting late usually means finding the most valuable archive after its subscription has already lapsed.
Who should own the workstream in a small integration team?
In a lean IMO, the IT integration lead can maintain the inventory and the retention hold, the finance integration lead can handle ERP history, and the operating partner can sponsor the licensing decision. What matters is one named owner with the authority to stop a decommissioning date when an export has not been verified.
Does the deal structure change who can license the acquired company's records?
It can. In a stock purchase the acquired entity generally keeps its own records, while in an asset purchase the agreement lists what transfers and what the seller keeps. Contractor agreements, customer contracts and privacy notices can add further limits. Have deal counsel confirm ownership and restrictions before anyone raises licensing with the CEO.
Can we consolidate onto one ERP and still keep licensable history?
Yes, because migration and preservation are separate decisions. Move what operations need into the platform ERP, then keep a verified full export or a read-only archive of the legacy system with a named custodian. The history stays available for audits, disputes and a possible licensing review, and the legacy subscription can still be cancelled on schedule.
Is the data asset workstream the same as data migration?
No. Data migration moves the records the combined business needs to operate, such as open orders, active customers and balances. The data asset workstream decides what happens to everything else: years of closed tickets, finished projects, old email and deal histories. It needs a named owner and a seat in the IMO cadence rather than a separate team.
Related pages
- Data Opportunity Handoff Checklist for Acquisition Integration
- Quarterly board meeting agenda template with a data asset update
- What happens to data when a transition services agreement ends
- Referral opportunities for private equity operating partners
- Prepare an owner-approved company introduction email
- Which US businesses are a fit for a SourceX data licensing introduction
Free resources
- Business valuation calculator — Enterprise and equity value from EBITDA, your multiple, cash and debt.
- Portfolio data opportunity scanner — Screen several companies in one session.
- Working capital calculator — Net working capital, current ratio and quick ratio.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment