Migrating Data to a New CRM: A Step-by-Step Checklist

A guide to CRM data migration: defining scope, cleaning, field mapping, trial imports, validation and go-live planning.

“We’ll just push the spreadsheet across, it will take an hour.” It is the most commonly heard and most commonly wrong sentence in CRM projects. Migration is not a technical job but a decision-making job: deciding what to migrate takes longer than migrating it.

1. Narrow the scope

You do not have to bring everything. Answer these:

  • Will records untouched for two years be migrated?
  • Are closed deals and cancelled quotes needed?
  • Do free-text notes matter more than structured fields, or the other way round?
  • Could data you only need for archive purposes go to a backup rather than the CRM?

A practical rule: every unnecessary record you migrate erodes the team’s trust in the CRM a little further.

2. Clean before you move

Migrating dirty data means spreading dirty data across two systems. Merge duplicates, normalise phone numbers and drop empty records before the import. Skip this and the CRM looks “messier than the old system” from day one.

3. Write down the field mapping

Put every field from the old system and its counterpart in the new one into a table. For fields with no counterpart there are three options: create a custom field, fold it into a notes field, or do not migrate it. Do not start importing before that decision is written down.

4. Run a trial import

  1. Load a sample of 50–100 records first.
  2. Have two people from the team use those records for real work (call them, create a quote).
  3. Feed the problems found back into the mapping table.
  4. Delete the sample and try again with the corrected mapping.

In projects that skip the trial, the problems always surface on go-live day.

5. Validation: what will you count?

  • Record counts: do source and target totals match? Any difference should be explainable.
  • Critical field completeness: has the share of records with a phone number dropped after migration?
  • Sample comparison: open 20 random records side by side in both systems.
  • Relationships: are contact–company and quote–contact links intact?

6. The go-live plan

To reduce surprises on the day:

  • Put the old system into read-only mode to stop double entry.
  • Leave time for one final incremental import (records created between the freeze and the switch).
  • Open a “data issue” channel for the first week so the team reports problems in one place.
  • Keep a backup of the old system for at least a year.

Frequently asked questions

Who should carry out the migration?

The vendor can do the technical import, but scope and mapping decisions must come from your team, who know the process. Those decisions cannot be outsourced.

When should we switch the old system off?

Parallel running should last a few weeks at most. A long parallel period leads to the team half-using both.

Can we migrate historical call recordings?

Audio files are usually left behind because of size; if access is needed, the old system’s archive is retained and only metadata is kept in the CRM.

Next step: to plan a sample import with your own list, request a demo.