CRM service
CRM migration
Moving to a new platform with the history intact. Mapped before anything transfers, tested on a sample, and run with a way back if it goes wrong.
The part of a migration that goes wrong is never the contacts
Contacts and companies move cleanly almost everywhere. Both systems have a name field, an email field and a company field, the mapping is obvious, and the import succeeds. That is the part people worry about, and it is the part that is fine.
What goes missing is everything hanging off those records. Activity history arriving with the wrong timestamps or no owner. Notes landing as one undated block per contact. Attachments that were never in the export to begin with. Close dates reset to the day of the import, which quietly destroys every historical conversion report you had. Custom fields dropped without comment because the target platform had no matching type.
None of that shows up on import day. It shows up six weeks later when somebody tries to pull last year’s numbers and cannot, by which point the old system may already be cancelled. So the mapping gets agreed and tested on a sample before the real run, and the old platform stays readable until you have signed off that the new one is complete.
What is included
What a migration engagement covers
A field-by-field map
Every field in the source matched to a destination, with the ones that have nowhere to go flagged and decided before the run rather than after it.
History, notes and attachments
Activity records, call logs, emails, notes and files moved with their dates and their owners, which is the part most migrations quietly skip.
Deal and pipeline history
Stages matched across platforms and close dates preserved, so your historical conversion and cycle length reports still mean something afterwards.
De-duplication
Duplicates found and merged before the import rather than multiplied by it, with the merge rules agreed with you in advance.
A sample run
A representative slice moved into the new system so you can open real records and inspect them before committing to the full transfer.
A rollback plan
The old system stays intact and readable throughout, with an agreed point at which we would stop and revert.
Integrations reconnected
The tools that fed the old CRM pointed at the new one, so forms, billing and support do not go dark on cutover day.
A sign-off checklist
A written list of what moved and what did not, which you check against before anybody cancels the old licence.
How it runs
How a migration runs
Audit the source
What you actually have: record counts, custom fields, attachment volume, and the integrations quietly writing into the system.
Map and agree
The field map goes to you in writing. Anything without a home gets a decision before the run, not during it.
Sample and verify
A slice moves first. You open real records in the new system and confirm the history looks the way it should.
Full run and sign-off
The complete transfer, then a checklist you tick before the old platform gets cancelled.
CRM migration questions
How long does a CRM migration take?
Two to four weeks is normal between two mainstream platforms. Most of that is mapping and verification rather than the transfer itself, which often runs overnight. Heavy customisation, large attachment volumes or a decade of history push it to six weeks or more.
Will we lose data?
Not if the mapping is done first. The honest answer is that some things cannot move perfectly between any two platforms, because the systems model them differently. The point of the mapping stage is that you learn which things those are, and decide what to do about them, before the transfer rather than after.
Can we keep using the old CRM during the move?
Yes, and you should. The old system stays live and readable until you have signed off the checklist. Anything entered during the transfer window gets caught by a delta run just before cutover, so the last few days do not go missing.
What about our integrations and forms?
They get inventoried during the audit, because these are what break most visibly. Website forms, billing, support tooling and marketing automation all get repointed and tested as part of the cutover rather than discovered afterwards.
Which platforms do you migrate between?
Any direction between the eleven I work in: HubSpot, Pipedrive, Zoho CRM Plus, monday CRM, Freshworks, Freshsales, Close, Brevo, EngageBay, Streak and Leadfeeder. Moves off older or in-house systems are possible too, though those need a closer look at what can actually be exported before I can quote.
Move without losing the history
Tell me what you are on now and where you want to go. You get a written view on what will move cleanly and what will not.