Add-on acquisition integration checklist: keep the history you are about to migrate

Why an integration checklist needs a records lane

Add-on integrations run on a clock set by the synergy case: the add-on's finance, CRM, support and HR systems are folded into the platform's, and the old subscriptions are cancelled. Migrations often carry open records (active customers, open tickets, the current year's ledger) and can leave the history behind. That history, years of tickets with resolutions, deals with outcomes and projects with their approvals, is what AI buyers value, because it shows how real work was done.

A records lane is a short parallel workstream that catalogs each add-on system before migration. It adds one cataloging task to the integration plan and keeps the archive available to assess later. For private equity operating partners running several add-ons a year, it also builds a portfolio-wide picture of what history exists. Software acquirers face the same problem with retired product lines, covered in the guide on vertical market software acquirers.

The integration checklist

Before signing

• Integration lead and integration management office cadence named before the purchase agreement is signed
• IT diligence systems list confirmed with the add-on's own staff, including tools paid on personal or departmental cards
• Deal structure noted, because an asset deal moves only the listed records (see who owns business records after an asset sale)
• Services the seller will provide after closing, and for how long, agreed in a transition services agreement where needed

Day one to day 30: control and people

• Bank accounts, signatories and payment approvals moved to platform controls
• Payroll and benefits continuity confirmed for the first pay cycle
• Employee announcement, manager briefing pack and a named contact for questions
• Top customers and suppliers contacted by their usual relationship owner
• Admin credentials for every add-on system moved to platform-controlled accounts

Days 30 to 90: finance, customers and policies

• Chart of accounts mapped and the close calendar aligned to the platform
• Customer contracts reviewed for assignment, confidentiality and data-use terms
• Pricing, discount authority and credit terms harmonized
• Privacy policy and customer terms harmonized without quietly widening how existing data may be used

Days 90 to 180: systems migration

• Migration plan per system, with cutover dates and a rollback plan
• Data mapping signed off by the business owner of each system
• Decommission date set only after the records lane signs off that system

Records lane: start before day 30, finish before any decommission

• Each add-on system cataloged: name, purpose, earliest record date, rough volume and business owner
• Export route recorded: built-in export, vendor request, database backup, or none known
• Retention and auto-delete settings recorded; ask counsel before changing any that exist for legal or privacy reasons
• Read-only archive destination agreed for anything not migrated in full
• Client-owned or third-party data flagged, with the contract that governs it
• Categories of personal data noted (customer contacts, employee files), with no samples copied
• Archive completion signed off by the system owner before the subscription ends
• Archive added to the platform's records register

On the privacy item, FTC staff have warned that adopting more permissive data practices, such as using consumers' data for AI training, and telling people only through a quiet, retroactive change to terms or a privacy policy may be unfair or deceptive (FTC staff post, February 2024; staff guidance, not a rule). Harmonize documents going forward and keep the add-on's earlier versions on file. This is general information, not legal, tax or financial advice; confirm privacy changes with counsel.

Once an archive looks promising, the data opportunity handoff checklist covers what to prepare for an introduction.

How to use the results

Red flags to escalate

• Admin access still held by the founder, a departed employee or an outside IT contractor.
• Company records kept in personal email or personal cloud storage accounts.
• Tools cancelled at renewal during the integration, before anyone checked the export.
• Client data mixed into the add-on's own operating records with no way to separate it.
• Records already licensed for AI training under an earlier agreement.
• After an asset deal, history left behind in the seller's retained entity.
• An add-on that never reached 50+ full-time employees at peak (contractors excluded). It does not meet the licensing baseline, even if its archive is worth keeping for its own use.

For a divestiture rather than an acquisition, the same logic runs in reverse; see the guide to carve-out data separation.

Next step

Add the records lane to your next integration plan before the first decommission date. If an add-on's archive looks deep, register as a partner and introduce the company, or have its CEO apply directly at sourcex.si/apply.

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 is payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. If you act for a fund, read the guide to management fee offsets and referral income before registering.