Migrating to a new CRM: the checklist that saves your data

A CRM migration starts by exporting the old system, before you pay for the new one. Then migrating in the right order, verifying with three numbers, and running a month in parallel.
Skipping any of those steps costs exactly the data you were changing systems to use better.
The most common mistake is starting by configuring the new CRM. It feels productive and ends with part of your history stranded in a system you no longer have access to.
Step 1: what should you export before doing anything?
The export from your current CRM is the first action, not one of them. The reason is simple: until the file is yours, you depend on someone else’s access.
What the export must contain:
- 1
Contacts and companies
With every field, including ones that look useless — you can filter later.
- 2
Deals
With stages, values and dates. This is the hardest thing to rebuild by hand.
- 3
Activity history
Calls, emails, notes. Often exported as a separate file — check for it.
- 4
Custom fields
The field list and their values. Without it the import turns your data into mush.
Step 2: what should you NOT move?
The urge to move everything is understandable and harmful. A base where half the records are dead corrupts every report in the new system and teaches the team not to trust the numbers.
Workable boundaries: contacts from the last 12–24 months, all open deals, full purchase history. Dead leads with no activity, duplicates and fields nobody filled in stay in the export file — not in the new CRM.
Step 3: migrate in the right order
Order matters, because objects reference each other:
- Companies — the top level.
- Contacts — attached to companies.
- Deals — attached to contacts and companies.
- Activities — attached to deals.
Breaking that order produces the worst kind of result: the data appears to be there, but the relationships are lost, and a customer record opens with no history.
Step 4: how do you verify with three numbers?
There’s no automatic «everything transferred». The working check is three numbers before and after:
- contact count;
- open deal count;
- total value in open deals.
If all three match, the structure came across. Then open five random records and read them: numbers won’t reveal a shifted field where a city landed in «job title».
Step 5: a month running in parallel
You don’t switch the old CRM off immediately — you leave it read-only for a month. Because missing data surfaces not during verification but when a specific person needs a specific history, usually in week two or three.
That month costs one extra subscription and regularly saves weeks of manual reconstruction.
Migration checklist
- Export contacts, companies, deals, activities and the custom-field list.
- Open every file and confirm the data is actually there.
- Decide what isn’t moving (dead leads, duplicates, empty fields).
- Migrate in order: companies → contacts → deals → activities.
- Compare the three numbers before and after.
- Manually check five random records.
- Migrate integrations and confirm nothing is duplicating.
- Keep the old CRM read-only for a month.
- Only then cancel the subscription.
Frequently asked questions
-
01 Where does a CRM migration start?
With a complete export from the old system, before you've even bought the new one. The export is your insurance: until it's on your own disk, any access problem with the old CRM becomes data loss.
-
02 What should you move and what should you leave?
Move open deals, contacts from the last 12–24 months and full purchase history. Don't move dead leads, duplicates or fields nobody ever filled in — in the new system they only corrupt your reporting.
-
03 How long should you keep the old CRM running?
At least a month in read-only mode. Missing data doesn't surface during checks but when a specific person needs a specific history — usually in week two or three.
-
04 How do you verify everything arrived?
Compare three numbers before and after: contact count, open deal count, and total value in open deals. Then open five random records and check by hand — automated checks don't catch shifted fields.
-
05 Do you need a contractor?
For a base of a few thousand contacts, usually not — a CSV export and the built-in importer will do. A contractor earns their fee when you have custom fields, object relationships and integrations to carry across.



