How to migrate your CRM without losing history

Teams rarely abandon a migration because the import failed. They abandon it because reps opened the new system, could not see what was said to a customer last month, and quietly went back to the old one.

Start with the record model, not the data

Before exporting anything, decide what a contact, a company, and a deal mean in the new system. Most legacy CRMs have accumulated custom fields that encode a process nobody follows any more. Migrating those forward just moves the mess.

The order that works

• Import companies first, then contacts, then deals — so relationships resolve as you go
• Bring conversation history with the contact, not as a separate archive
• Map old pipeline stages to new ones explicitly; do not let a default swallow them
• Import open items (deals, tasks, unpaid invoices) before closed ones
• Run one week in parallel, with the old system read-only

Decide what not to bring

Contacts that have not been touched in three years are not assets, they are noise that makes search worse. Archive them somewhere retrievable and start clean. The same goes for pipeline stages nobody uses and custom fields that are empty on ninety percent of records.

A migration is the cheapest opportunity you will ever get to delete things.

Make the first week obviously better

Adoption is won in the first few days. Make sure the inbox is connected, the pipeline reflects how the team actually sells, and at least one manual chore is already automated. If the new system is only as good as the old one on day one, people will drift back.