CRM Data Migration Checklist

A CRM data migration is the move of your contacts, deals, notes and history from an old system into a new one without losing or scrambling any of it. For a service business, it runs in 3 phases (before, during and after the cutover) and typically takes a few days to a few weeks, depending on volume.

Most owners spend weeks choosing the new system and an afternoon moving into it. That is backwards. A rushed import can bury years of customer history under duplicates and broken stages. The checklist below is the order we follow when a client changes systems. It is the same approach behind our CRM and tech setup.

Why a CRM Data Migration Needs a Checklist

Most bad migrations do not fail on import day. The import finishes, the totals look close, and everyone moves on. The damage shows up a month later, when someone cannot find a customer's last estimate or a report says half your leads came from "Unknown."

The old system grew by habit. Fields were added for one campaign and never used again. Stages got renamed halfway through a year. The same customer was entered 2 different ways by 2 different people. A migration copies all of that into the new system unless someone decides, field by field, what comes along and what stays behind.

So expect the real work to be decisions, not clicks. Also settle which system you are moving to before any of this starts, because switching platforms halfway means redoing the field map from scratch. We go deeper on this in our post on HubSpot vs Salesforce.

Before the Migration: Your CRM Data Prep Checklist

Most of a migration's success is decided before a single record moves. Start with the data itself.

• Export everything, including contacts, deals, notes, activities and custom fields, and save a dated copy that nobody edits.
• Decide what not to bring, such as leads with no contact in years, test records and fields nobody has filled in since they were created.
• Clean duplicates and dead contacts by merging records that share an email or phone number and archiving bounced or disconnected ones.
• Standardize phone and address formats so every number and street follows one pattern before it lands in the new system.

Clean data still breaks if the team has not agreed on where it goes. These 3 decisions come next, and they need sign-off from whoever runs sales.

• Define the field map, a simple sheet that lists every old field, the new field it moves to and every field that gets dropped.
• Agree on stage names and write one sentence for each that says what has to happen before a deal can enter it.
• Set the cutover date and a short freeze window, often 1 to 3 days, when nobody edits records in the old system.

When something looks off after the import, the field map is usually where it went wrong, so keep that sheet open until the project is done. This ties directly into HubSpot vs GoHighLevel, which we cover in a separate post.

During the CRM Migration: Import, Check and Reconnect

Import day should be the calmest part of the project if the prep is done. Move in small steps you can check, not one giant upload you cannot undo.

• Import in batches, starting with a small test file, so a mistake touches a handful of records instead of all of them.
• Load contacts first, then deals, then activities, because deals and activities need a contact to attach to.
• Keep the old system's record ID in a field on every new record, so you can trace any problem back to where it came from.
• Spot-check 20 records by hand against the old system, including some of your oldest and messiest ones.

Once the records look right, point every connection that fed the old CRM at the new one.

• Reconnect forms, phone tracking, calendar booking and email so new leads land in the new system from the first hour.
• Rebuild the automations one at a time, such as lead alerts and follow-up reminders, instead of copying them blindly.
• Test each one with a real lead, submitted the way a customer would, and confirm it shows up with the right source and stage.

Plan on finding at least one connection you forgot, usually a form on an old landing page or a booking link in an email signature. List every place a lead can enter before you switch.

After the CRM Migration: Run Both Systems and Compare

The cutover is not the finish line. For the first few weeks, the new system is on probation.

• Run both systems for 2 weeks, with the old one set to read-only so nobody enters new data there by accident.
• Compare counts by stage and by lead source between the 2 systems, and chase down every gap.
• Retire access to the old system once the counts match, and keep a final export on file.
• Train the team on the differences, especially renamed stages, new required fields and where old notes now live.
• Review the first month's reports with fresh eyes, since a report that looks too good or too empty usually points to a mapping error.

Counts by source matter more as lead volume grows. Take an anonymized NJ HVAC client whose Local Services Ads categories grew from 4 to 11 and whose absolute-top impression share rose from 12.56% to 30.37%. That meant more kinds of jobs and more leads arriving through a channel that charges per lead. At that volume, a sloppy source field or a broken stage would hide which paid leads turned into work. In one recent engagement, we matched charged leads to booked jobs for a NJ HVAC company.

What Usually Goes Wrong in a CRM Data Migration

Most problems trace back to a step that got skipped under time pressure. In our experience, these cost the most.

• Duplicates multiply because the same customer came in from 2 places, such as the old CRM and a separate email list.
• Notes and activity history land on the wrong record, or on no record at all, because deals were loaded before contacts.
• Lead sources collapse into one generic value, so reports can no longer show which marketing produced jobs.
• Stages get matched by name instead of meaning, so a deal that was only quoted shows up as won.
• Automations fire on old records and send a welcome email to customers who have been with you for 5 years.
• A form or phone line never gets reconnected, and leads quietly pile up in a system nobody checks.

Custom fields are where the industry makes the biggest difference. A home services company might track service address, equipment age and warranty dates. A law firm tracks matter type, intake source and conflict checks. These rarely have a clean match in a new system. The same problem looks different by vertical, as our page on CRM and tech built for law firms shows.

How Long Does a CRM Data Migration Take?

Volume and history set the pace. In our experience, a small service business with a few thousand contacts, one pipeline and light automation can finish the move in a few days of focused work. A company with years of activity history, several pipelines and dozens of automations should plan on a few weeks.

Either way, add the 2-week parallel run on top. The timeline stretches most when cleanup gets left for import day, because removing duplicates and mapping fields need decisions from people who are busy running the business. Put that time on their calendars up front and the rest moves quickly.

A clean migration is not really about the software. It is about ending up with a pipeline you can trust, where every lead has a source and every closed job traces back to the marketing that produced it. That is the difference between counting leads and counting business. We have seen this play out firsthand, as our post on real estate marketing that generates listings explains.

Frequently Asked Questions

What data should you migrate to a new CRM?

Move contacts, open and closed deals, notes, activity history and any custom fields your team actually uses. Leave behind test records, contacts with no activity in years and fields nobody fills in. Keep a full export of the old system on file, even for data you do not import, so you can pull something back later if a question comes up.

Should you run the old and new CRM at the same time?

Yes, for a short window. Keeping the old system read-only for about 2 weeks lets you compare counts by stage and source and catch records that did not come across. Do not let anyone enter new data in the old system during that time, or you will end up with 2 versions of the truth and more cleanup at the end.

Can you do a CRM data migration yourself?

Many small businesses can, if the data is modest and one person owns the project from start to finish. The export and import tools in most CRMs are straightforward. What takes skill is the field map, the stage definitions and rebuilding the automations and connections so nothing breaks. If you have years of history or several lead sources feeding the system, outside help is usually worth it.