Switch in stages, never in one weekend. So first you list everything the old system does, including the small jobs nobody mentions. Then you build an import you can run more than once, and you bring consent and permissions across with the records. You rebuild automations from how the work runs today. And then you run both systems on real work, pick a switch-off date, and keep the old data readable afterwards.
Inventory what the old system actually does
A lot of times we see a migration go wrong because of something nobody ever wrote down. The reminder that goes out at 7am. The webhook still pointing at an old form. The one report finance opens on the last working day of the month.
Before you touch any data, build four lists: records, jobs, integrations and permissions. Then walk through them with the people who use the system every day, and not just the person who bought it.
| What to list | Why it breaks a switch | Where it usually hides |
|---|---|---|
| Record types and fields | Custom fields drop on import without warning | Admin settings, not the main views |
| Files and attachments | Stored apart from the records, so links break | Contracts, ID documents, signed quotes |
| Conversations | Email and SMS history is often the only record of a promise | Inbox threads tied to a user, not a contact |
| Automations and scheduled jobs | Reminders stop, or go out twice while both systems run | Workflow builders, calendar automations |
| Integrations and webhooks | Forms keep posting to the system you turned off | Website forms, ad platforms, payment tools |
| Reports and saved views | Finance and sales lose their monthly numbers | Saved filters owned by one person |
| Roles and permissions | Everyone gets admin "for now" and keeps it | User list, hardly ever checked |
When not to migrate at all
If the tool you've got does the job and the problem is really how people use it, switching costs you money and changes nothing. Move when the system stops you doing work you need to do. Say it can't handle the roles you need, it can't join your data up, or you're paying for more and more tools that don't talk to each other. Those are real reasons to move. "I don't like how it looks" isn't.
Build an import you can run twice
A one-off import is a gamble. An import you can run again is something you can test, fix and rerun until the numbers match.
Three things make that work. Give every record a fixed ID from the old system, so when you run it again it updates the record instead of making a copy. Run it in a test copy first. And check it with counts instead of gut feel, so contacts in, contacts out, and a written reason for every gap.
You'll be cleaning as you go. Duplicate contacts, dead email domains and half-finished deals are much easier to sort before they land than after. Be clear about what you're leaving behind as well. Old leads from four years ago usually belong in a CSV export stored away, and not in your new CRM setup and migration.
Carry consent and permissions across, not just the records
Marketing consent is data too. If your old system recorded who opted in, when, and to what, that proof has to arrive with the contact. What ends up happening otherwise is you import a contact without it and then email someone who unsubscribed two years ago.
Be exact about what the consent covers. Under UK PECR, automated marketing calls need the person's specific prior consent, and general marketing consent is not enough (ICO guidance). Take the same care with unsubscribe flags, do-not-contact markers and anything a client asked you to delete.
Permissions need the same care. Match the old roles to the new ones before launch, and decide who can see money, client documents and message history. When we do it, it runs on Agentryx One with clear permissions and we run it for the client. The data is still theirs, and if they leave we export it for them.
Rebuild automations from the process, not by copying
If you copy twelve old workflows into a new tool, you copy twelve old guesses about how the business works. Write down what each automation is for in one sentence, and then rebuild only the ones you still need.
Watch out for double sends. While both systems are live, the same enquiry can set off a reminder in each one. So decide early which system sends messages out during the overlap, and set the other one to internal alerts only.
Volume costs you money as well. In Zapier, each successful action step counts as a task, triggers and filters don't, and when you hit your plan limit new runs are held unless you pay for extra tasks (Zapier help centre). Running both systems can double your action count for a month. So budget for it, or you'll find the limit on a Monday morning. And if you're rebuilding anyway, that's a good time to ask if those chains should be workflow automation you own instead of steps you rent.
Run old and new side by side before switching off
Running both side by side is the part people skip, and it's the part that saves them. Pick a slice of real work, put it through the new system, and keep the old one open but read-only where you can.
Test real cases and the ways things fail, and not just the version where everything goes right. A booking that gets cancelled. A payment that fails. A client who replies to an email thread from three weeks ago. We test edge cases and failure paths before anything touches a customer, because the errors that cost you are always the ones nobody practised.
Put a switch-off date in writing and name the person who makes the call. If the overlap has no end date, you end up with two systems forever, and that's the problem you started with.
What our own migration out of GoHighLevel taught us
We moved our own CRM out of GoHighLevel into a system we built, and it's complete, confirmed by the owner on 2 October 2026. Doing it on ourselves changed how we scope it for clients.
The main thing we learned was about counts. The owner reset the CRM on purpose on 26 September 2026, so the import counts show what that migration carried across, not what's in there today. Those records must not be imported again. If that note hadn't been written down, a tidy-up later on could have pulled old data back in and messed up the live set.
So keep a migration log. What ran, on what date, what it carried, and what's now out of scope for good. Treat it as part of the handover documents, not a side note.
Go/no-go checklist before you switch off
- Record counts match between old and new, with a written reason for every difference.
- Files open from the new records, not from old links.
- Consent and unsubscribe states are there and spot-checked against the old system.
- Every live form, ad platform and payment tool now posts to the new system.
- One system owns outgoing messages, with no double sends in the last two weeks of the overlap.
- Roles and permissions are set per person, with no blanket admin.
- Finance can rebuild last month's numbers in the new system.
- The team has been trained and has written documents.
- A full export of the old system is stored somewhere you can still read in two years.
- One named person owns the first two weeks after launch.
If you can't tick all ten, you're not ready to turn the old system off. You're ready to make the overlap longer.
Your next step this week
Spend an hour filling in the table above for the system you want to replace, and then ask two people on your team what breaks if it disappears on Friday. That list is your scope. If it shows a bigger problem than one tool, read how to choose a CRM for a service business before you commit, or compare the options in our CRM migration guide. When you want someone to look over the plan with you, book a call and we'll go through it together.



