Buy-and-build IT integration: what to do with each add-on's legacy systems

Why each add-on integration sets a records deadline

Every add-on integration ends with a decommission date, and that date is also the last day the add-on's history can be exported. When the platform moves an add-on onto its ERP, email tenant, CRM and helpdesk, the migration usually carries only what the combined business needs day to day: active customers, open tickets, opening balances and current-year ledgers. The old systems are then switched off.

The history left behind is often the most valuable part: years of resolved tickets, won and lost quotes, approvals and the email threads that explain them. AI labs and data buyers license records like these because they show multi-step work with outcomes, which is thin on the public web. Once a subscription lapses or a server is wiped, that option is gone; deleted archives are a red flag that stops a data licensing review.

The pressure to find value during the hold is real. Bain & Company's Global Private Equity Report 2026 estimates that a buyout which needed about 5% EBITDA growth a decade ago to reach a 2.5x return over five years now needs about 12%. A buy-and-build thesis already counts on integration savings; keeping each add-on's licensing option open costs little if planned before cutover.

What is the archive-before-decommission gate?

It is one rule: no add-on system is switched off until its history has been assessed and someone with authority has decided what to keep. Put it in the integration management office (IMO) cutover checklist, next to data mapping and user-acceptance testing.

A system clears the gate when all five boxes are ticked:

• Logged: the system, its oldest record date, its record types and its admin owner are on the add-on's inventory.
• Exported: a complete export exists, not just the records being migrated, and someone has opened it to confirm it is readable.
• Owned: the team knows which legal entity created and holds the records, and whether customer contracts limit their use.
• Decided: the entity's authorized signer has chosen keep, assess for licensing, or retire, in writing.
• Timed: the vendor contract end date and any post-termination deletion window are on the cutover calendar.

The gate is designed not to move a go-live date: exports can run alongside migration testing, and only the final shutdown waits for a signature.

Which add-on systems hold history worth assessing?

The gap between what a system holds and what integration keeps is where history gets lost.

Records that belong to the add-on's own clients (an agency's client deliverables, for example), consumer personal data and patient records are red flags unless consents, a licensing basis or de-identification are in place. Keep them under the entity's retention rules and out of licensing talks until then.

When should the platform team act on each add-on?

Tie each records action to your integration calendar; the order matters more than the exact weeks.

The IT due diligence checklist adds data rights and licensability questions to the diligence stage, so the system list arrives before close rather than after. When an add-on's ledgers are being folded into the platform ERP, the guide to ERP consolidation in PE portfolios covers which ledger history to keep.

Who can authorize a license for an add-on's records?

Permission runs entity by entity, because each add-on arrived with its own contracts, customers and staff. SourceX needs an authorized sponsor (owner, CEO, CFO or authorized representative) for whichever entity actually holds the records.

Read each add-on's old privacy policy and customer terms too. Staff at the Federal Trade Commission have written that a company's promises about how customer data will be used, including promises not to use it for training models, are enforceable whether they appear in privacy policies, terms of service or marketing. That post is staff guidance rather than a rule, but it is a good reason to check what each add-on told its customers before anyone discusses licensing. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

Who to bring into the conversation

• Platform CEO or CFO: decides whether licensing fits the plan and may sign for merged entities.
• CIO, VP of IT or IMO lead: owns the cutover calendar and the gate.
• The add-on's president or founder: knows which archives matter and where old systems live.
• The MSP or systems integrator: sees retention settings and export options first.
• Deal counsel: settles entity, contract and earnout questions.

Make the introduction to the authorized signer. You never handle, export or describe the records.

What to say at the integration steering meeting

Raise it as a sequencing question, not a sales pitch.

For the founder, keep it shorter:

How the introduction works for each add-on

Introduce add-ons in the order their systems are scheduled to go dark.

1. Register as a partner and use the network opportunity finder to think through the platform and each add-on as separate candidates.
2. Check each entity against the baseline on who qualifies: a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data and an authorized sponsor.
3. Send the signer your referral link so the entity applies at sourcex.si/apply with your credit attached, or submit it through the referral form.
4. SourceX qualifies the entity on size, history, data breadth and rights.
5. The company completes a data inventory covering each system and its years of history.
6. SourceX and the company agree one all-in price and the license terms; nothing binds until the company signs.
7. AI labs and data buyers review the opportunity; when a deal closes, data is delivered under the agreed redaction rules and the company is paid.

Being acquired does not rule an add-on out: operating, acquired and wound-down companies can all qualify if the data still exists. An add-on that never reached 50+ full-time employees at peak does not meet the baseline on its own; ask SourceX how records now held inside the platform are treated.

How partner rewards work across a platform and its add-ons

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward becomes payable only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger it, and rewards are not guaranteed. Because the reward is a share of SourceX's fee, it never reduces what the add-on or platform receives.

Whether a merged add-on counts as its own referred company is set by the program terms and your partner agreement, so confirm it before assuming separate caps, and check your firm's policy on fees connected to portfolio companies.

When to leave an add-on out

Skip the introduction, but still apply the gate, when:

• Its records mostly belong to its clients and those clients have not consented.
• Its data is mainly consumer personal information or patient records with no licensing basis.
• The old systems were already shut down without exports.
• Nobody with authority will sign, or an open earnout dispute makes the timing wrong.
• The same records were already licensed for AI training.
• The owner will not consider an exclusive license for an agreed term.

If an add-on is being closed rather than merged, work from the IT wind-down checklist instead; a closure has different custody and approval steps.

Next step

Add the archive-before-decommission gate to the next add-on's cutover plan this quarter. When an add-on clears the gate and the fit screen, register as a partner and introduce it, one entity at a time. For portfolio-wide context, see referral opportunities for private equity operating partners.