CRM Migration Checklist: Move Without Losing Data

Key takeaways

• Most CRM migrations go wrong before any data moves: nobody decided what to leave behind, so every mess gets copied into the new system.
• Run the move in six stages: plan, clean, map, test, cut over, adopt. The test stage is the one teams skip and regret.
• Do at least two full trial imports into a sandbox and have reps check their own accounts before you set a cutover date.

Picture a 40-person sales team that has spent four years in one CRM. The contract renews in six weeks, leadership has picked a new platform, and someone says, “Can’t we just export everything and import it?”

You can. You’ll also spend the next quarter finding out what didn’t come across. This checklist covers how to switch CRMs without losing history, breaking reports or annoying your reps.

Decide what you’re actually moving

Before touching a CSV, answer one question: what does the new system need on day one to run the business?

Usually that’s active accounts and contacts, open opportunities, the last 12 to 24 months of activity, and the closed-won history you use for reporting. Everything else is optional.

Old leads from 2019, duplicate accounts and free-text fields nobody reads don’t belong in the new CRM. A migration is the one moment you can leave them behind without an argument.

Stage 1: plan the scope

Name one owner for the migration. It’s usually RevOps or a sales ops lead, and it can’t be “the team”.

Then write down:

• Which objects move (accounts, contacts, leads, deals, activities, notes, attachments, custom objects).
• Which integrations touch the CRM today: marketing automation, email, calendar, billing, enrichment, support.
• Which reports and dashboards leadership actually opens.
• A hard date when the old CRM contract ends, and a buffer before it.

That last item matters. Teams that plan to cut over on the day the contract expires have no room for a failed trial.

Stage 2: clean before you move

Dirty data is cheaper to fix in the old system, where people still know what the fields mean. Merge duplicates, standardise countries and picklists, and reassign records owned by people who’ve left.

We’ve written a full CRM data hygiene checklist for this. For a migration, the short version is: dedupe first, then required fields, then formats.

Skip perfection. You’re aiming for “clean enough that the mapping makes sense”, not a flawless database.

Stage 3: map fields and objects

This is where most of the real work sits. Build one mapping sheet with a row per field: old object, old field, new object, new field, transformation, and who approved it.

The tricky ones are always the same:

Item	Why it bites	What to do
Picklist values	Old and new lists don’t match one to one	Map each value explicitly, add an “Other” bucket
Lead vs contact	Platforms model people differently	Decide where each record type lands, in writing
Record owners	Users must exist in the new CRM first	Create users before importing, map by email
Dates and time zones	Imports can shift timestamps	Test with records you can check by eye
Activity history	Emails and calls may need a separate tool	Confirm what’s importable before promising it
Custom objects	No native equivalent in some platforms	Decide whether to rebuild or retire them

If you’re still choosing a platform, our comparison of Salesforce, HubSpot and Zoho covers how each handles objects and customisation.

Stage 4: test with trial imports

Never run the real import first. Use a sandbox, or a copy of the new CRM, and do at least two full trial runs.

Reps are your best QA. They know their accounts, and they’ll spot a wrong owner or a missing note in seconds. Give them a short window and a simple way to flag issues.

Expect the first trial to look bad. That’s the point of it.

Stage 5: cut over without a mess

Once a trial passes cleanly, set the date. A sensible sequence:

Keep the old system read-only for a few months after cutover. It’s your safety net when someone asks “where did that note go?”

Stage 6: drive adoption

A migration isn’t done when the data lands. It’s done when reps trust the new CRM enough to stop keeping notes in spreadsheets.

Run a short training on the three things each role does daily. Retire old dashboards so there’s only one source of truth. Review usage after 30 days and fix whatever people are working around.

This is also the best time to get the data ready for automation. Our CRM AI readiness checklist shows what to have in place before you point agents at your records. If you want help with the move itself, our implementation team handles platform migrations, and the same approach applies whether you’re moving to HubSpot or Salesforce.

The bottom line

A CRM migration is a data-quality project with a software switch at the end. Decide what moves, clean it, map it carefully, trial it twice, then cut over with a short freeze and a real adoption plan.

If you’d like a second pair of eyes on your plan before you commit to a date, book a free 30-minute consultation and we’ll go through it with you.