What to do with old CRM data after a migration: keep, archive, delete or assess

Four options for legacy CRM data, and the one most plans forget

After a CRM migration, the old data can be kept running read-only, archived as a complete export, deleted under a retention policy, or assessed for licensing before either of the last two. Most cutover plans cover the first three. The fourth matters because the history left behind in a legacy CRM is often the part richest in outcomes: closed-lost deals, loss reasons, resolved cases and years of logged activity.

Assessment does not replace archiving. It is a question to answer before the archive is finalized and before anything is deleted.

Why a migration leaves most of the history behind

Migration scope is set by what the new system needs on day one, not by what the old one holds. Teams typically move active accounts, open opportunities, current contacts and a recent slice of activities, then leave the rest where it is. Common leftovers:

• Closed-lost and older closed-won opportunities, with their stage histories and loss reasons.
• Activity and email logs older than the cutoff year.
• Field history tracking, which rarely maps cleanly onto a new platform.
• Attachments, notes and call summaries stored as files.
• Custom objects built for one team or one process that the new design dropped.
• Inactive users, retired picklist values and old stage definitions that explain what the records meant at the time.

That last group is easy to overlook. Without the old stage names and user list, an opportunity record from years ago is a row of codes. Chat tools raise the same problem during platform changes; see what happens to Slack history in a move to Teams.

What old CRM history is worth assessing

Records that capture a decision and its outcome carry the most weight for AI training and evaluation, because they show how real sales and service work unfolded step by step.

The 90/60/30-day countdown before the old CRM goes dark

Use the decommission date as day zero and work backwards. The owner and project team do the work; a consultant can write each step into the cutover plan.

If the switch-off date is under 30 days away, compress the list: secure the complete export first and make every other decision afterwards. The data inventory builder helps the sponsor list the systems and records the archive covers.

What to preserve in the final export

• Every standard and custom object, not only the migrated ones
• Field history and audit tables
• Attachments, files, notes and email content
• Metadata as it stood: stage names, picklist values, record types and validation rules
• The full user list, including inactive users, so owner IDs still resolve
• An export log with dates, record counts and who ran each job

How long to keep the archive depends on what is in it. The page on how long to keep business records after closing explains which rules set retention periods for each record type.

Rights and privacy checks before any licensing work

A CRM holds personal information about customers' staff and prospects, and the company has usually made commitments about how that information is used. FTC staff stated in January 2024 that companies' promises not to use customer data for undisclosed purposes, such as training models, are enforceable, whether the promise appears in a privacy policy, terms of service or promotional material. The post is staff guidance rather than a rule, but it signals how the agency reads privacy promises.

Before an assessment goes further, the company should check what its privacy notice and customer contracts said, and SourceX agrees de-identification and redaction requirements with the company before any work begins. Two situations usually stop the process: a CRM that mainly holds other businesses' customer data, as at agencies that run CRMs for clients, and a CRM that is mostly consumer personal information with no licensing basis.

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

How a CRM consultant raises it without touching the data

Your role ends at the introduction. Any export for licensing is run by the company itself, after a license is signed and the owner approves delivery, never by the implementation partner, even one that already holds admin rights on both systems. The CRM consultant partner page covers the wider program, and the guide to introductions during a CRM migration covers handling the topic inside a live project.

Wording like this works in a steering meeting:

If the sponsor wants it in writing, use the introduction email builder to prepare a note for their sign-off.

Illustrative: a distributor switches CRMs

Illustrative, fictional example. A 180-person industrial distributor moves from an on-premises CRM it has used for over a decade to a cloud platform. The migration plan carries three years of activities and all open deals. At the 90-day mark the RevOps lead lists the four options, and the CFO agrees to a fit check. At day 30 the company runs a complete export with stage history, quotes and service cases intact. The old instance is cancelled on schedule, and the licensing decision is made later from the archive without delaying go-live.

How rewards work

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 paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed.

The reward comes out of SourceX's fee, so the client's proceeds are unchanged. If you are billing the client for the migration, disclose the partner relationship in writing first, so the suggestion is never mistaken for part of your implementation advice.

Next step

Add the four-option question to your next cutover plan. When a client clears the baseline on who qualifies, sign up as a SourceX partner and send the introduction before the decommission date.