System decommissioning after acquisition: what to keep before switching off

Why decommissioning is when an add-on's history disappears

When an add-on moves onto the platform's CRM, help desk, ERP or email tenant, most integration plans migrate only open records and active accounts. Closed tickets, lost deals, finished projects and departed employees' mailboxes stay in the legacy system, which is then cancelled to capture the synergy. Before decommissioning, keep a complete export of each system, because that closed history is often the most licensable part of the acquired company's records.

It is also the part buyers value most. AI developers training agents need records of work that reached an outcome: a ticket resolved or escalated, an opportunity won or lost, an order approved or held. Researchers at Epoch AI project that, if current trends continue, language models will fully use the stock of public human-written text sometime between 2026 and 2032, a forecast with wide uncertainty (Epoch AI). Non-public operating records fill a gap the public web cannot.

For operating partners this is a value-creation question as much as an IT one. McKinsey's 2026 private markets report argues that, with multiple expansion and cheap leverage fading, operational value creation is now likely the primary source of private equity returns (McKinsey Global Private Markets Report). An archive preserved during integration keeps an option open that costs little to hold.

Decommissioning timeline: what to do and when

Tie records decisions to the calendar the integration management office already runs.

What a complete export includes

One rule saves most archives: if the migration only moves what is open, archive everything that is closed.

Export options and retention after cancellation vary by vendor and contract tier, so read the vendor's own documentation and your contract rather than assuming. The guide to preserving company records before shutting down systems covers formats and storage in more depth.

Who to talk to

• The integration lead or IMO: owns the cutover plan and can add archive scope without slowing the migration.
• The platform CIO or CTO: decides storage, access controls and who holds admin credentials after cutover.
• The platform CFO: books the synergy savings and can approve a few extra weeks of a legacy subscription if the export needs them.
• General counsel: checks litigation holds, retention obligations and the acquired company's customer contracts.
• The add-on's former leadership: knows which archives go back furthest and which systems were retired before the deal.

Who can authorize a license afterwards depends on how the deal was structured. In a stock purchase the acquired entity usually still holds its records; in an asset deal it depends on what the purchase agreement transferred, which the guide to excluded assets in an asset sale explains. Deal counsel should confirm either way.

What to say to the platform CIO

Preservation checklist before switch-off

• Every legacy system has a named owner and documented admin credentials.
• Deletion and retention policies are suspended until the export is validated.
• Departed employees' mailboxes are retained, not deleted along with their licenses.
• Exports include metadata, attachments, internal notes and full history, not just current-state reports.
• Record counts in the export match counts in the source system.
• Exports are stored in two company-controlled locations with access logging.
• A short manifest lists each system, date range, record counts and export date.
• Counsel has confirmed legal holds and any customer contract limits.
• The add-on has been run through the company fit checker before the vendor contract ends.

How the referral works for a sponsor

Your team makes the introduction; the company's own staff handle exports, the data inventory and any delivery. SourceX qualifies the company against the baseline on who qualifies, the company agrees price and terms, AI labs and data buyers review, and data moves only after an executed agreement and the company's authorization, under redaction rules agreed before work begins.

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, and the reward becomes payable only after the buyer pays and SourceX receives its fee. It is never deducted from what the company receives, and no reward is guaranteed. How a platform and its add-ons are treated as referred companies is set by the program terms, so check them before planning a portfolio-wide approach, along with your own firm's policies on fees connected to portfolio companies. The hub for private equity operating partners covers the wider portfolio playbook.

When the archive is not a licensing candidate

• The add-on's records mainly belong to its clients, as at agencies, outsourcers and some IT service firms, and those clients have not consented.
• The history is mostly about consumers or patients rather than the company's own work; the guide to business records vs personal data explains why that changes the analysis.
• The company has already licensed the same data for AI training.
• The archive was purged before the deal, or the vendor has already deleted the tenant.

A small add-on that never reached 50+ full-time employees at peak (contractors excluded) may not qualify on its own. Screen it with the fit checker rather than assuming either way, and keep the archive under the retention policy in the meantime.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Next step

Add an archive line to the next integration steering committee agenda. For any add-on with deep history, register as a partner and introduce the company before its legacy contracts end.