How to Migrate a CRM Without Losing Customer History, Conversations or Tags

Most data loss in a CRM switch is not a technical failure. It happens because someone exported the contact list, imported it, and only found out weeks later that notes, email threads, deal history or opt-out records stayed behind. This guide covers how to plan the move so that doesn’t happen, whichever CRMs you are moving between.

What do you need to do before migrating a CRM?

Take an inventory, decide what moves, and freeze changes. Before anything is exported, list every type of data the old CRM holds, who uses it, and which automations depend on it. That inventory becomes the checklist you test against at the end, so nothing is forgotten because nobody remembered it existed.

1. Count your records. Note the number of contacts, companies, deals, notes, tasks and files today. You will compare these counts after import.
2. List every field. Export the field list, including custom fields, and mark each one keep, merge or drop.
3. List every tag and list. Tags often carry meaning (customer type, source, consent) that automations rely on.
4. List every automation. Workflows, sequences, round-robin rules and integrations. They never move by export; they have to be rebuilt.
5. Find your consent records. Opt-outs, unsubscribes and do-not-contact flags must move with the contacts. Losing them means texting or emailing people who said no, which breaks TCPA in the US, CASL in Canada, PECR in the UK and the Spam Act in Australia.
6. Take a full backup. Keep a complete, dated export of the old system even after the move, in case a question about a customer comes up later.
7. Set a change freeze. Agree a date after which nobody adds new fields or automations in the old CRM.

Which data transfers cleanly and which needs rebuilding?

Records transfer; behaviour doesn’t. Contacts, companies, custom fields, tags and deals move cleanly with a mapped CSV import. Conversation history, emails, call recordings and files usually need an API-based transfer or have to be attached as notes. Automations, user permissions and integrations always have to be rebuilt in the new system.

A done-for-you CRM migration covers all of these, including the history that a simple CSV import leaves behind.

How do you keep conversation history when switching CRMs?

Export it separately from the contacts, then attach it to the matching contact in the new CRM. Most CRMs don’t include messages in a standard contact export, so the history is pulled through the old system’s API or its full data export, matched to each contact by email address or phone number, and written into the new CRM.

How it arrives depends on the new system. Some CRMs, including GoHighLevel, let messages be written into a contact’s conversation through the API, so the thread looks much as it did before. Where that isn’t possible, the history goes in as a dated transcript note or a file on the contact. Either way, your team can open a customer and see what was said before the switch. Decide which approach you need before the project starts, because it changes the effort involved.

How should you map fields, tags and pipelines?

Build a mapping sheet with one row per field: the old field name, the new field name, the field type and any clean-up rule. Create every custom field, tag and pipeline stage in the new CRM first, then import against that sheet. Importing first and tidying later is how fields end up in the wrong place.

• Clean before you map. Merge duplicate contacts, standardise phone numbers to the international format (+1, +44, +61, +971 and so on), and fix obviously broken emails.
• Simplify tags. “Lead-FB”, “fb lead” and “Facebook Lead” should become one tag.
• Map pipeline stages one to one. If the new pipeline has fewer stages, decide where each old stage lands and write it down.
• Keep source data. Original lead source, created date and owner are easy to lose and hard to recover.

For a worked example of this mapping between two specific systems, see our HubSpot to GoHighLevel migration guide.

What is the safest way to cut over to the new CRM?

Move in phases with a short overlap, not in one weekend. Import a test batch first, then the full historical data, then run both systems side by side for a few days while new leads go to the new CRM. Switch off the old one only after the final changes are moved across and the checks below pass.

Phone numbers and email sending domains need their own plan. Porting a business number to a new provider usually takes days to a few weeks, and the new CRM’s sending domain needs its DNS records in place before campaigns go out, so start both early.

How do you check that nothing was lost after the migration?

Compare counts, then check real customers. Record counts tell you whether everything arrived; spot checks tell you whether it arrived correctly. Do both before the old CRM is switched off, while you can still go back and fix gaps.

• Counts: contacts, companies, deals by stage, notes, tasks and files, old against new.
• Spot checks: open 20 to 30 real customers, including your oldest, your biggest and a few with long histories, and compare them field by field.
• Consent: confirm that every contact who opted out in the old CRM is marked do-not-contact in the new one.
• Automations: run each one with a test contact and check the messages, tasks and stage changes it makes.
• Reports: rebuild your key report (for example deals won last quarter) in the new CRM and check it gives the same number.

How long does a CRM migration take?

For most small and mid-sized businesses, one to four weeks. Data volume matters less than you would expect; the time goes into history transfer, rebuilding automations and integrations, and the overlap period. A clean contact list with a few pipelines moves quickly, while years of emails, calls and custom logic take longer.

If you are moving off a system your team built in-house, read our separate guide to migrating from a homegrown CRM, because the export and logic steps are different. If GoHighLevel is the destination, our GoHighLevel migration service covers the move, and CRM setup covers building the new system around how your team actually sells.