CRM data cleanup before migration: what to fix, what to keep, and what to assess first

What should you clean up in a CRM before migration, and what should you keep?

Clean up duplicates, broken fields and obviously dead test data. Do not purge closed-lost deals, old activities, notes or inactive accounts until someone has assessed whether that history has value. The rule is simple: assess before you purge.

Pre-migration cleanups usually aim to cut record counts to reduce migration cost and speed up the cutover. That instinct is sound for junk, but the same pass often deletes the longest, most connected history in the company: the trail of how deals were won and lost. For a RevOps consultant, a short screen with the owner before deletion costs an hour and keeps an option open.

What is safe to remove, and what is not?

Separate hygiene from history. Hygiene fixes the data; history is the data.

The assess-before-purge screen in five questions

Run this with the owner or revenue leader before any bulk delete. If any answer is yes to the first two, pause the purge.

• History: does the CRM hold several years of deals, activities and cases, going back before the current sales team?
• Outcomes: are won, lost and escalated outcomes recorded, with reasons?
• Breadth: does the CRM connect to other systems such as finance, support or marketing automation?
• Rights: did the company create these records, and do customer contracts and privacy notices allow them to be licensed?
• Sponsor: can you reach an owner, CEO, CFO or authorized representative who could decide?

The company must also meet the baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations and the right to license. The who qualifies page has the details.

How do you run the cleanup without destroying value?

Follow this order. The point is that archival copies exist before anything is deleted.

1. Take a full export of every object, including attachments, with record IDs and a field dictionary, before the cleanup begins.
2. Agree the delete list in writing with the owner, naming each object and the filter used.
3. Do duplicate merges first, and store the mapping of merged IDs to surviving IDs.
4. Delete only the categories marked safe in the table above.
5. Migrate what the new CRM needs for daily work, and archive the rest to storage the company controls.
6. Keep the export until the owner has decided whether the history is worth screening, even if the new CRM never imports it.

For a specific move off Salesforce, what history gets left behind in a Salesforce to HubSpot migration shows where the gaps usually appear. If the same project retires a second system, the Jira and Confluence migration page covers the engineering side.

What mistakes do cleanups make most often?

Illustrative: a mid-sized services firm

Illustrative and fictional. A 180-person IT services firm is moving from one CRM to another. The migration plan proposes dropping opportunities older than three years and all activities older than 18 months. The consultant proposes one extra step: export first, then ask the owner whether the history is worth a screen. The firm keeps the export, imports the recent year, and the owner later chooses to check eligibility. Nothing is promised; the company decides.

What do you say to the owner?

Use the introduction email builder to draft it with the owner's approval. You never handle or describe the records.

Which questions should the owner answer before you start?

Ask these in the kickoff call, so the archive decision is made on purpose and not by whoever writes the filter.

• Who owns the old CRM contract, and when does access end?
• Is any business unit, brand or acquired company history stored in the same instance?
• Do customer contracts restrict how account and contact data can be used or shared?
• Which integrations write into the CRM, such as billing, support or marketing tools, and will they be retired too?
• Who inside the company can run exports and confirm they are complete?

Answers to the rights questions matter most. If customers or an outsourcer own the data, or the instance is mostly consumer personal data, the screen ends there and the cleanup proceeds as normal.

How do partner rewards work for a RevOps consultant?

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. Payment happens only after the buyer pays and SourceX receives its fee; a screen, meeting or signed agreement alone does not trigger it, and no reward is guaranteed. The reward is never deducted from what the company receives. Consultants should also disclose the arrangement to clients where their own engagement terms require it. The program terms govern the details.

When is it not worth raising?

Skip it for a CRM under a few years old, one that is mostly consumer contacts, or a company well below 50 full-time employees at peak. Also skip it when a court, trustee or assignee controls the assets and has not been involved. The day 1 readiness guide covers when to hold legacy systems during acquisitions, and cutting cloud storage costs covers the same assess-first rule for storage.

Next step

Add the five-question screen to your next migration plan. If a client passes, register as a partner and make the introduction, or point the owner to sourcex.si/apply. The RevOps consultant page explains the role in more depth, and data licensing during a CRM migration covers timing.