CRM consolidation after an acquisition: how to keep the activity history

Why the acquired CRM's history is at risk

Consolidation projects are scoped around what the combined sales team needs on day one: accounts, contacts, open opportunities and active owners. Activity history is the largest and messiest part of an org and the easiest to cut, so it is often summarized, partly migrated or left in an instance that is switched off when the license renewal arrives.

That history is the record of how deals actually moved. Each logged email, call, task and stage change shows what a rep did, in what order and with what result. For the combined company it explains past wins and losses. For AI developers training agents to do sales and service work, it is a scarce kind of example. Epoch AI researchers have projected that language models could fully use the stock of public human-written text sometime between 2026 and 2032 if current trends continue. It is a forecast with wide uncertainty, but it explains why non-public business records attract interest.

If the deal team asks what that history might be worth, the guide to how data assets are valued in M&A walks through the cost, market and income approaches.

What counts as activity history?

Activity history is everything that records what happened to a record over time, not only its current state. Agree a written definition with the client before scoping, because each platform stores it differently.

The CRM consultant referral overview describes which of these records most often signal a company worth introducing.

Consolidation timeline: what to do before and after cutover

Anchor the plan to the cutover date and work backwards. The weeks are approximate; compress them for small orgs.

The license renewal date is the real deadline. Find it in week one, because a short extension is often the difference between a careful export and a rushed one.

Who to talk to

• Integration lead or IMO head: owns scope and the cutover date.
• CRO or head of sales: decides which history the combined team needs every day.
• RevOps lead: knows the field mappings, the automation and where data quality breaks down.
• CFO: controls license renewals and archive budgets, and can weigh a one-time licensing payment against the cost of keeping history.
• General counsel or privacy lead: confirms what customer contracts and privacy notices allow.
• The sponsor's operating partner, when the acquirer is PE-backed: often tracking several integrations at once.

What to preserve: the export checklist

• Every object exported with original record IDs and owner IDs, so history can be relinked later
• Activity and timeline records, including completed tasks and past events
• Field and stage history for opportunities, leads and cases
• Email bodies and attachments logged to records, not only metadata
• Call recordings and transcripts, together with the notice or consent records that applied when they were made
• Picklist values, stage definitions and the sales process documentation that explains them
• A user list mapping former owners to roles and teams
• Automation and workflow definitions, documented before they are switched off
• A reconciliation report comparing record counts before and after
• A named owner and storage location for the archive after decommissioning

If the acquired company also runs its own ERP, coordinate with the finance workstream; the companion guide to ERP consolidation after acquisitions lists the ledger and workflow history worth keeping.

Privacy and contract limits

CRM data holds personal information about business contacts and sometimes consumers, so what the company promised them matters. FTC staff have stated that commitments not to use customer data for undisclosed purposes, such as training models, are enforceable whether they appear in a privacy policy, terms of service or promotional materials. Any licensing conversation therefore starts with the company's own notices and customer contracts, reviewed by its counsel.

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

Your part is the archive and the introduction, nothing more. CRM records are never exported, sampled or summarized for SourceX; any redaction and de-identification rules are settled between the company and SourceX before work starts, and delivery follows only an executed agreement and the company's authorization.

What to say to the client

When an introduction makes sense

Use two simple rules. If the combined company has 50+ full-time employees at peak (contractors excluded), several years of activity history across the CRM and connected tools, rights to license the material and an executive willing to consider an exclusive license, an introduction is reasonable. If the CRM served mainly as a contact list with little logged activity, or the records are mostly about consumers, preserve the history for operational reasons and stop there.

The who qualifies page has the full baseline, and the company fit checker gives a preliminary, non-binding read without asking for contact details.

Consultants who introduce a company earn 25% of the eligible platform fees SourceX collects on its licensing deals, capped at $100,000 per company. The reward becomes payable only once the buyer has paid and SourceX has received its fee; a meeting or a signed contract alone does not trigger it, and rewards are not guaranteed. If you hold a CRM vendor partner certification or work under a client contract with conflict clauses, read those terms first.

Next step

Find the acquired org's license renewal date and put the full export on the project plan. Then register as a partner so your introduction is tracked from the first conversation.