Moving to a new CRM is mostly a data project, and the people who use the system decide whether it succeeds. This checklist covers what to decide before, during and after the move.
Key takeaways
- Clean and deduplicate data before you move it, not after.
- Agree a field map with the people who use the CRM and get sign-off.
- Run a test migration on a sample, then the full move, and keep the old system read-only for a while.
Why migrations go wrong
Most CRM migrations fail quietly. The records arrive, but notes are missing, owners are wrong, deals sit in the wrong stage and the team stops trusting the new system. The cause is usually not the tool. It is the lack of a plan for the data and the people.
Before the move
- Agree why you are moving and what must be better afterwards.
- List every object you use: contacts, companies, deals, tickets, products, quotes, custom objects.
- Decide what history to bring: notes, emails, calls, tasks, attachments and stage changes.
- Clean the data first: merge duplicates, archive dead records, fix owners and required fields.
- Map every field from the old system to the new one, and get the map approved by the people who use it.
- List the integrations, forms and automations that touch the CRM today.
During the move
- Build the new system’s pipelines, fields and permissions before importing anything.
- Run a test migration with a sample of real records and check them with users.
- Keep the original record IDs in a field on the new records, so anything can be traced back.
- Migrate in a sensible order: companies, then contacts, then deals, then activities, so relationships link up.
- Freeze changes in the old system during the final run, or plan a short catch-up import.
After the move
- Reconcile counts by object and spot-check records with the team.
- Reconnect integrations and forms, and test each one end to end.
- Rebuild the reports people rely on and compare them with the old system.
- Train each team on its own daily tasks, not on every feature.
- Keep read-only access to the old system for a period in case something is missing.
A note on attachments and email history
Attachments and email history are often the slowest and most fragile part of a migration. Decide early whether they all need to move, whether a link back to the archive is enough, or whether only recent years matter.
FAQ
Can email history and attachments be migrated?
Often, yes, depending on what the old and new CRMs allow through their APIs. Confirm it early because it affects the approach.
Should we clean our data before or after the migration?
Before. Moving duplicates and bad data into a new system makes them harder to fix later.
What happens to our integrations?
Each integration needs to be pointed at the new CRM or rebuilt. List them all during planning so none are missed.
How long it takes
The size of the database matters less than the number of objects, custom fields and integrations. A careful test run is the best estimate you can get, because it shows the real problems in your data before the final move.
Our CRM migration services cover HubSpot, Zoho, Salesforce, SuiteCRM and SugarCRM, starting with a field map you approve before anything moves. If you are staying on SuiteCRM and upgrading, see how to plan a SuiteCRM 7 to 8 upgrade.