Digital transformation in PE portfolio companies: assess the archive before you modernize

What digital transformation looks like in a PE portfolio company

In a sponsor-backed company, digital transformation is a funded program to replace the systems and manual workarounds that will not carry the business through its next stage of growth. It is often front-loaded into the early years of the hold, so the benefits show up in the numbers before exit.

Most programs combine several of these workstreams:

• ERP replacement: moving off an on-premise or heavily customized accounting and operations system.
• CRM consolidation: one pipeline and one customer record after add-ons arrive with their own tools.
• Service platform migration: helpdesk, ITSM or field service tools rebuilt on a single platform.
• Content and collaboration: file servers and legacy document stores moved to cloud storage, and email tenants merged.
• Data and reporting: a warehouse and BI layer so the board and management see the same numbers.
• AI use cases: document processing, service automation and copilots built on cleaner data.

The pressure behind these programs is arithmetic. Bain's Global Private Equity Report 2026 estimates that a deal which needed 5% EBITDA growth a decade ago to reach a 2.5x return over five years now needs about 12%, which pushes sponsors toward operating programs they can control.

Why decommissioning is the moment that matters

Every transformation ends with old systems being switched off, and that is when years of operating history are most at risk. Migration scopes are designed around what the new platform needs to run: open orders, active customers, current price lists and perhaps a few recent years of transactions. Older history stays behind in the legacy system, and once its license, server or support contract ends, recovering it can become expensive or impossible.

That older history is often what AI developers value most. Quotes that turned into orders or were lost, cases that escalated before they were resolved, project files, approvals and change orders show how a business really operates over time. AI labs and data buyers training agents to carry out multi-step tasks look for this kind of permissioned, rights-cleared material, and very little of it exists on the public web.

So the checkpoint is a single rule: no system is decommissioned until its full history sits in storage the company controls and someone has decided whether it is worth assessing for a license. The same rule applies to smaller cost-out programs, covered in the guide to software rationalization for cost reduction.

Timeline: the archive checkpoint against the cutover plan

Plan the checkpoint in weeks relative to cutover, inside the workplan the program team already runs. The timings below are a planning guide; adapt them to your program.

Who needs to be in the room

Five people decide whether history survives a transformation, and the operating partner is often the one who can get them into the same meeting.

• CFO: owns the budget and the decommissioning sign-off, and is one of the executives who can sponsor a licensing discussion.
• CIO or IT director: knows which systems hold what, how far back, and who can run exports.
• Program lead or systems integrator: controls migration scope and the cutover plan.
• General counsel or outside counsel: reviews customer contracts, employee notices and privacy commitments.
• CEO: decides whether the company wants to explore a license at all.

If you are the operating partner on the program, the operating partner referral guide explains how your side of the introduction works.

Rights checks before any history is reused

Archiving records is routine; offering them for AI training is a separate decision that turns on what the company promised. FTC staff have stated that companies' commitments not to use customer data for undisclosed purposes, such as training models, are enforceable whether they appear in privacy policies, terms of service or promotional materials. Read those documents, together with customer contracts and confidentiality clauses, before anyone discusses licensing.

Records the company created about its own operations are the strongest candidates. Material that belongs to clients, consumer personal data and protected health information need consent, a licensing basis or de-identification, and some of it will stay out of scope. Redaction and de-identification requirements are agreed with the company before any work starts, and nothing is delivered without an executed agreement and the company's authorization.

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

What to preserve before anything is switched off

Use this list for each retiring system. The company keeps the files in its own storage; the operating partner never receives or reviews them.

• Legacy ERP: transactions, purchase orders, quotes, change orders and approval history, with dates.
• CRM: accounts, opportunities with won or lost status and reasons, activity history and notes.
• Helpdesk or ITSM: full ticket threads, status changes, escalations and resolution codes.
• File servers and document stores: project folders, SOPs and templates, with the folder structure intact.
• Email and chat from tenants being merged or closed, within the company's retention policy.
• Engineering: repositories, pull request history and issue trackers.
• An export register listing system, years covered, record counts, format, storage location and owner.

What to say at the transformation steering committee

What the checkpoint gives the sponsor

Preserving and assessing the history changes three things. The company keeps an option it would otherwise lose at shutdown. The exit story gains a documented records asset, which matters when buyers assess AI readiness at exit. And if the company qualifies and signs, it receives a one-time payment at one all-in price, with SourceX's fee included and no separate charges.

The route from there is short to describe. After you register, you introduce the company by referral link or referral form; SourceX qualifies it on size, history, data breadth and rights; the company completes its data inventory; and price and terms are agreed before buyers review anything. The guide on assessing portfolio company data opportunities covers that review in more depth.

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. The reward becomes payable only once the buyer has paid and SourceX has received its fee, no reward is guaranteed, and it never reduces what the company receives.

When the checkpoint does not apply

Skip the licensing assessment, though not the export, when:

• The company never reached 50+ full-time employees at peak (contractors excluded), or has only a short operating history.
• The legacy system mainly holds clients' own data, such as a platform the company hosted for customers.
• The records are mostly consumer personal data or medical records without a licensing basis.
• The history was already deleted, or a former vendor holds it and will not export it.

Next step

Add the archive gate to the next transformation charter you review, then check the first company against who qualifies or the company fit checker. If it fits, register as a partner and introduce the company, or have the CEO apply at sourcex.si/apply with your referral link.