ERP consolidation in a PE portfolio: assess each legacy archive before shutdown

What ERP consolidation does to legacy archives

ERP consolidation moves each add-on from its own system onto the platform's ERP, and most programs carry over only master data, open transactions and a limited slice of history. The rest stays in the legacy system until its license or hosting contract lapses, then disappears unless someone keeps a complete export. For an operating partner, the consolidation calendar is therefore also a list of dates after which an asset may no longer exist.

The asset is the record of how each business actually ran: years of orders, purchase approvals, credit holds, pricing exceptions, returns and supplier disputes, plus the email, Teams threads, tickets and documents that explain them. AI developers training agents to do this kind of work need exactly those connected histories. SourceX licenses them, rights-cleared and with the company's approval, to AI labs and data buyers; the company keeps ownership and receives a one-time payment only if it decides to sign.

Why operating partners are well placed to catch this

You sit above the integration program, so you see what entity-level teams do not: the full list of systems scheduled to go dark, the TSA and license end dates, and which executives can sign for which legal entity. You also own the value creation plan, and operational levers carry more weight than they used to. McKinsey's Global Private Markets Report 2026 says multiple expansion and cheap leverage, which accounted for 59 percent of PE returns between 2010 and 2022, have faded, leaving operational value creation as the likely primary source of returns.

A buy-and-build platform that keeps acquiring add-ons can accumulate several generations of systems, each with its own archive, so the retirement list is worth reading as an inventory of records as well as a cost line.

Which entities in the program are worth screening

Screen per legal entity, not per platform. Each referred company is assessed on its own merits, so an add-on with a long history can matter even after it has been folded into the platform.

The who qualifies page sets out the full baseline. Note which legal entity holds each add-on's records today, because that entity's sponsor is the person who would sign.

The archive-before-retire rule

Use one rule across the portfolio: no legacy system is decommissioned until its archive has been screened and the entity's sponsor has made a decision. The screen is five checks, run by the program office for every system on the retirement list.

• Records: which years does the legacy system hold, and which surrounding systems hold the context (mailboxes, Teams, shared drives, tickets)?
• Export: can a complete export, including attachments, notes and audit history, still be produced before the license or hosting contract ends, and who will run it?
• Entity: which legal entity owns these records today, after any mergers or asset transfers?
• Rights: do customer, supplier or government contracts restrict use of the records, and are any record sets mainly health or consumer personal data?
• Sponsor: who is authorized to sign for that entity (owner, CEO, CFO or authorized representative), and have they been asked?

If all five pass, the entity is a candidate for an introduction. If the export check fails, fix that first: a preserved export keeps the option open even if the sponsor decides later.

When to raise it in the consolidation timeline

The best moment is data migration scoping, when the team is already deciding how much history to carry over.

Before hardware leaves, walk the program office through the ITAD data destruction checklist. If an MSP is running migrations for several entities, its team often sees the retirement list first; the guide on additional revenue streams for MSPs explains how they approach introductions.

How the introduction works for each entity

You or the entity's sponsor starts the process, and nobody on your team handles records.

1. Register as a partner and send the entity's sponsor your referral link, or submit the entity through the referral form.
2. SourceX reviews size, operating history, breadth of systems and rights with the sponsor.
3. The entity completes a data inventory: each system, its date range, what it records and how it can be exported.
4. SourceX and the sponsor agree one all-in price and the license terms before any buyer sees the opportunity.
5. AI labs and data buyers review it; once an entity is deal-ready, buyers typically respond within about two weeks.
6. The entity signs, the data is prepared under redaction rules agreed in advance and delivered, and the entity receives a one-time payment.

Redaction and de-identification requirements are settled with the entity before work starts, and nothing is delivered without an executed agreement and the sponsor's authorization. The assessment guide for private equity teams covers the review in more depth.

What to say to the platform CFO

Raise it at the steering committee or the weekly program review, framed as a decision to log before each shutdown date rather than as a new workstream.

How partner rewards work in a portfolio

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. Payment follows only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement on its own does not trigger it, and no reward is guaranteed. The reward is a share of SourceX's fee and never reduces what the entity receives.

The cap applies per referred company, and the program terms define what counts as one, so check them before assuming each add-on is separate. Check your fund's own policies on fees connected to portfolio companies before you register, and disclose any reward to the relevant board.

When an archive is not worth the effort

Skip the introduction, and simply keep a standard retention export, when:

• The add-on's records mainly belong to its clients, as at many agencies and outsourcers, and those clients have not consented.
• The legacy data is mostly protected health information or consumer personal data with no licensing basis.
• The archive was already deleted, or the vendor will not produce a complete export.
• The entity has already licensed the same records for AI training.
• The entity never reached 50+ full-time employees at peak and holds only a short history.
• The platform is in a live sale process and the deal team wants no new contracts before signing.

Next step

Ask the program office for the retirement list and run the five checks on the next system due to go read-only. Use the network opportunity finder to map which sponsors you can reach, then register as a partner. The referral overview for private equity operating partners covers other portfolio moments worth screening.