CRM migration: planning the move without data loss
Switching CRM is rarely one click on 'export'. For contacts, deals, history and interfaces to fit together again in the new system, you need clean mapping, a test run and a clear cutover date. This guide shows what matters during the move, tool-agnostic and with an eye on HubSpot.
Why a move is more than export and import
Almost every CRM can hand out its data as a CSV. That is why a switch looks easy at first glance: export, import, done. In practice, exactly what makes a CRM valuable gets lost along the way. The link between person and company, the connection between deal and contact, the history with its dates. A well-kept customer record turns into loose rows in a spreadsheet.
A migration starts right here. It transfers not just the records but their relationships and their history, and it makes sure the systems that used to sit on the old CRM talk to the new one again afterwards. The raw data transfer is the smallest part of that. The work sits before it, in the cleanup and in deciding what belongs where.
If your concern is less the move itself and more the lasting connection of several systems, the CRM integration is the right frame. And if the old system is mainly full of duplicate and outdated records, it is worth cleaning the CRM data first, ideally before the move.
What actually comes along in a move
Contacts are only the tip. A CRM is made of several layers, and each one needs its own decision during the move.
Contacts and companies
The easy part, as long as the link between person and company comes along. That is exactly where many CSV imports fail: the contacts land in the new system, but without the company behind them.
Deals and pipelines
Open and won deals have to go into the right pipeline and stage of the new CRM. That assumes the stages are mapped cleanly beforehand, otherwise every deal ends up in the wrong column.
Activities and history
Notes, calls, tasks and email threads are what make a CRM usable in the first place. Whether and how far they come along depends on what the old system hands out through its API.
Custom fields
Self-created fields, dropdowns and custom objects rarely have an exact match in the new CRM. Here each field gets its own decision: where it goes, whether it is merged or dropped.
Attachments and documents
Quotes, contracts and files on the records are easily forgotten. Taking them over is possible, but needs its own step, because they do not sit in the normal data export file.
Automations and interfaces
Workflows, forms and connected systems do not simply move along. They are rebuilt and re-wired in the new CRM, otherwise nobody writes the right data after the move.
Where a move goes wrong
These points show up in almost every migration. Knowing them beforehand means planning for them, instead of hunting for them in the data after go-live.
Duplicates from two sources
If data already sits in the new system alongside the old CRM, say from a newsletter tool, the import creates duplicate contacts. Before the migration you need a clear rule for what to match on, usually the email address, and what wins on a hit.
Field mapping without a plan
Every field in the old system needs a target in the new one or a deliberate decision to drop it. Where that is not settled up front, data lands in the wrong field or in a free-text note, and the reporting in the new CRM no longer adds up.
Lost timestamps
If the history is imported without its original date, every old item suddenly looks brand new in the new CRM. For reporting and for judging how warm a contact is, that is a real problem.
Required fields and validation
The new system rejects records that leave required fields empty or use the wrong format. Old data sets are rarely that clean. Without cleanup first, the migration breaks off midway or quietly leaves records behind.
IDs and relationships
Every CRM assigns its own internal IDs. During the move the relationships between contact, company and deal have to be translated to the new IDs. Get that wrong and the records are there, but without their context.
Consent and GDPR
Marketing consent and the legal status of a contact have to travel across correctly. Anyone who no longer knows after the move who agreed to the newsletter has a data protection problem instead of a new CRM.
How a CRM move runs
Five phases in which the data transfer itself is the shortest. The rest is preparation and safeguards.
Inventory
First we look at what sits in the old CRM: which objects, how many records, how clean the data is and which systems are connected. The result is an honest list of what comes along and what stays in the archive.
Mapping and cleanup
Field by field we decide where it goes in the new CRM. In parallel, duplicates are merged and obvious junk is sorted out. This step is the largest, and it decides the data quality in the new system.
Test migration
A slice of the real data moves into the new CRM, and we check: are the relationships right, are the timestamps correct, do the required fields catch what they should? Whatever shows up here gets fixed before the full move runs.
Cutover
On the cutover date the full data set moves, the interfaces are switched over to the new CRM and the old system is set to read-only. The team works in the new CRM from here, the old one stays reachable as a fallback.
After go-live
In the first days after go-live we check that every interface writes, that no records are stuck and that the team gets along. Small corrections to fields and workflows are part of it, that belongs to the move and is not a sign of a fault.
All at once or step by step
For the switch itself there are two paths. Which one fits depends on the data volume and how much risk the running business can take.
Big bang
Everything moves on one cutover date, and from then on the team works only in the new CRM. That is simpler to plan and spares you a parallel operation where data on both sides can drift apart.
Fits when
the data set is manageable, the test migration ran clean and a short weekend is enough for the switch.
Gradual
Both systems run in parallel for a while and are kept in sync while area after area moves over. That lowers the risk of one big outage, but it requires an interim sync that has to be built and watched.
Fits when
many users, large data volumes or critical processes are involved and a standstill on the cutover date would be too costly.
Re-wiring the interfaces
The part that most often falls through the cracks during a move is the connections to other systems. The old CRM rarely stood alone: a form on the website created contacts, the newsletter tool synced subscribers, the ERP wrote orders back, the phone system logged calls. After the move, each of these connections points at nothing.
So every migration includes an inventory of the connected systems. Each interface is switched over to the new CRM and tested one by one before the old path is shut off. When moving to HubSpot this is often the more demanding part, because some connections run through a ready connector and others have to be built by hand.
What those connections look like in detail, which run through a marketplace connector and when a custom interface is worth it, is covered in the guide on HubSpot interfaces.
How to tell a clean migration
- Before the real move, a test migration ran on real data, and its results were checked, not just the import started.
- Relationships between contact, company and deal stand in the new CRM just as before, and the history carries its original date.
- Duplicates were merged before the import, instead of carrying doubled records into the new system.
- All connected systems write into the new CRM after go-live, and the old one stays reachable as an archive for a while.
Whether the switch is the right step at all, or whether the existing system can still be saved, is settled fastest in a sober inventory. That is exactly what the CRM consulting is for.
Common questions about CRM migration
Planning a CRM switch?
Tell me briefly which system you want out of and where it should go. In the intro call we look at how much history and which interfaces are attached and whether a big bang or a gradual move is the more honest path for your case.
- Free intro call, about 15 minutes
- A clear read on what comes along and what belongs in the archive
- An honest look at effort, history and interfaces before anything moves