CRM migration checklist
Twenty steps in five stages, from the decision to the weeks after the switch. Tick each one as it is done: your progress stays in this browser, and the list prints cleanly for the team.
- Free
- No sign-up
- Runs in your browser
- 5 min
Your preparation
Next step to do
We know why we are changing CRM and what must be better afterward.
How to use it.
- 1
Go through the five stages
Before anything moves, the data, the new system, the test and the switch. The order matters: each stage protects the next.
- 2
Tick what is truly done
The panel shows how far along you are and the next step that is still open. Your ticks are kept in your browser for the next visit.
- 3
Share it
Print the list and bring it to the kickoff meeting, so everyone sees the same steps and who owns them.
Why CRM migrations go wrong, and how the list prevents it
A CRM migration rarely fails on the day of the switch. It fails weeks earlier, when nobody decided which fields to keep, or weeks later, when the team quietly goes back to spreadsheets because the reports no longer match. The list is built around those two moments.
The data stage carries the most risk. A migration copies everything, including the duplicates, the contacts who left five years ago and the fields no one fills in. Cleaning before the move costs a fraction of cleaning after, and mapping every old field to a new one, or deciding to drop it, removes most surprises.
The test is the step most often skipped. Importing a sample, checking it record by record and letting two or three people do their real work in the new system for a few days reveals what a demo never shows: the automation that did not fire, the report whose total is off, the field that was truncated.
The switch itself should be dull. The team is already trained, the old system is frozen in read-only so no data is entered in two places, and someone is on hand to answer questions for two weeks. A date to review what is missing closes the project properly.
Migrations the list is made for
- 01
From spreadsheets to a first CRM
The same stages apply: the spreadsheet is the old system, and the cleanup is usually the largest part.
- 02
From one CRM to another
For example to Zoho CRM, HubSpot, Salesforce, Pipedrive or Dynamics 365, whichever direction you move in.
- 03
From a CRM to a custom build
When a system built around your process replaces a product that no longer fits.
- 04
After a merger
Two companies, two CRMs and one set of clients to bring together without duplicates.
Next step
Have the migration done for you
We move your data, rebuild your pipelines and automations in the new CRM, test it with your team and stay on hand in the weeks after the switch.
How long does a CRM migration take?
It depends on the volume and the state of the data, on how many tools are connected and on how much history you bring. The cleanup and the test usually take longer than the import itself.
What do we do with the history?
Decide it on purpose. Open deals and active contacts always come along. Old emails and closed deals can be brought in, archived in a file, or left in the old system kept in read-only for a time.
Can we keep working during the migration?
Yes. The team keeps using the old system until the day of the switch. It is then frozen in read-only so that nothing is entered in two places.
Where are my ticks saved?
In your browser, on this device only. Nothing is sent to us. Clearing your browser data or using another device starts the list over.
Can you run the migration for us?
Yes. We handle the export, the cleanup, the mapping, the trial import, the rebuild of automations and the training, and we stay available after the switch.
Other free tools.
Each one answers a different question before a CRM, automation or AI project.
Want a person to look at your result?
Bring it to a free call. We will tell you what we would do first, and what we would leave alone.
What would you fix first?
On the call we walk through your sales process and find where leads and follow-ups get lost.