The Pre-Migration Checklist: What to Audit Before You Touch Your CRM
Every migration I’ve run into starts the same way. A business owner is ready to leave their old CRM, they’ve already picked the new platform, and they want to move this week. Nobody wants to spend time in the tool they’re about to abandon. That’s exactly where the real work is.
What Breaks During a Migration
When people move CRMs, they plan for the big visible pieces — contacts, pipelines, maybe email templates. What gets missed lives in the corners of the old system nobody opens anymore: the automation built for a workflow that changed eighteen months ago, the tags nobody remembers the purpose of, the custom fields three different people filled in three different ways.
That kind of thing lives outside any spreadsheet of “what we need to bring over” — and it surfaces three weeks after go-live, when someone asks why a client didn’t get a follow-up email, or why a report is missing half its data.
Audit Before You Migrate, Not During
The checklist below is what I walk every client through before we touch the new platform. It takes a day, sometimes two. That feels slow when you’re eager to be done with the old tool. It’s the part that determines whether the new platform works on day one.
- Every active automation. List what triggers it, what it does, and whether anyone still needs it. If nobody can explain why an automation exists, that’s your answer.
- Every tag and custom field. Pull a report and count how each one is being used. Tags with five contacts and no clear purpose don’t need to survive the move.
- Duplicate and stale contacts. Anyone who hasn’t opened an email or answered a call in over a year probably shouldn’t come with you.
- Every integration touching the CRM. Website forms, invoicing, calendar booking, text messaging — map what’s connected before you disconnect it.
- Who has access and why. A migration is a natural point to clean up logins nobody’s used in months.
- What reporting depends on. If you run monthly numbers off this data, know exactly which fields those reports pull from before they disappear.
“We Don’t Have Time for an Audit”
This is the objection I hear most, and I understand it. You’ve already decided to move. You want the new tool live, not a spreadsheet of everything wrong with the old one.
Skipping the audit trades a known cost now for an unknown one later. Every hour you don’t spend auditing the old system becomes an hour spent later troubleshooting the new one, usually while a client is waiting on something that fell through. I’ve watched businesses spend three months untangling a migration they rushed in three days. The audit is the cheapest hour in the whole process.
What a Clean Audit Buys You
A clean audit means the new platform launches with only what still matters. It means the automations you rebuild are the ones you use, not the ones you inherited from a workflow nobody follows anymore. And it means when something breaks in week two — something always breaks in week two — you already know what depends on what, so you can fix it in an hour instead of a week.
The migration itself is the easy part. Copying data from one system to another is mechanical work. The audit is where you decide what you’re building on.
Set aside the day. Open the old system before you open the new one.
Related reading:
How to Consolidate Your Business Tools Without Losing Your Data
What Happens When Your CRM, Email, Invoicing, and Scheduling Don’t Talk to Each Other
Why Small Businesses Are Paying for Five Tools When They Need One
Book a free discovery call to see what this looks like for your business.