CRM Migration for Service Businesses: What to Do Before You Switch
Switching CRMs without a plan is how service businesses lose their best leads. Here's the pre-migration checklist that keeps your pipeline intact.
If you're a plumber, HVAC contractor, electrician, or roofer who has decided their current customer-management system isn't working anymore, moving to a new one can feel like a clean slate. What usually happens instead: the contacts move, the mess stays, and within a few weeks you're wondering where the active leads went.
The platform rarely causes these problems. The missing pre-migration work does. A clean, well-staged migration protects the pipeline you already have, gets the new system running faster, and means your follow-up automations fire correctly on day one instead of three weeks in. Here's what to do before you touch the export button.
Why CRM Migrations Go Wrong
The most common failure looks like this: a contractor exports all contacts into a spreadsheet, imports them into the new system, and discovers the data is unusable — no consistent stage labels, duplicate contacts, missing phone numbers, and three different versions of the same customer's record.
From there, automations break because they're firing based on stages that don't exist in the new setup. Active leads vanish in the import. Staff spend weeks manually re-tagging records instead of following up on open jobs. The new platform ends up feeling harder to use than the old one, even though nothing about the platform itself is the problem.
The issue is the same every time: the migration moved the mess rather than fixing it first.
Step 1: Audit Your Data Before You Export
Before you touch the export button, open your current system and take stock of what you actually have.
Look for:
- Duplicate contacts — the same person entered more than once from different sources (a phone call, a form submission, and a manual entry by a technician on the job).
- Inconsistent or missing stage labels — contacts marked "Open," "Pending," "In Progress," or nothing at all, when what you need is clean buckets like New Lead, Quoted, Booked, Completed, and Cold.
- Bad contact data — phone numbers with no area code, emails without a domain, addresses that are blank or wrong.
- Old completed jobs still marked active — records that should be in a "Past Customer" or archive bucket but are sitting in the live pipeline.
This audit tells you how much cleanup is needed before you migrate. A small service business with a few hundred contacts can usually get through it in a few focused hours. For larger or more complicated databases, Lumen's CRM cleanup and migration service handles the full audit and cleanup before data moves anywhere.
Step 2: Clean and Stage First, Move Second
Once you know what you have, clean it in place — before the export. The goal is to arrive at a database where every contact has a correct name, phone number, and email; one consistent stage label; and at least one tag for service type or lead source.
This matters because the automations in the new system are going to fire based on those stage labels. If your "Quoted" contacts aren't actually tagged "Quoted," the quote-follow-up sequence either fires for the wrong people or doesn't fire at all.
The full cleanup process — deduplication, stage cleanup, fixing broken contact data, and archiving stale records — is covered in detail in the guide to CRM cleanup for service businesses. The short version: clean first, then migrate.
Step 3: Map Your Pipeline Stages Before You Build Anything
Before you configure anything in the new system, decide what your pipeline stages need to be and write them down. Stage names that seem obvious today become ambiguous the moment a second person starts managing the system.
A basic pipeline for a home service business:
- New Lead — first inquiry, no outbound response yet
- Contacted — you've replied; waiting on their response
- Quoted — estimate sent; awaiting a decision
- Booked — job is on the calendar
- Completed — job is done; review request pending
- Cold — no response after follow-up; ready for a reactivation pass later
- Past Customer — completed job, more than one interaction
Map these out before you start building in the new platform. Every automation you connect — the quote follow-up sequence, the booking confirmation, the post-job review request, the cold lead reactivation sequence — depends on a stage transition to trigger. If the stages shift after the automations are live, the workflows break.
Step 4: Handle Your Active Pipeline Carefully
Your active pipeline — anything currently in Quoted or Booked — is the part that most service businesses handle worst in a migration. These contacts are mid-conversation. Moving them without tracking their status carefully is how you drop a job you'd already lined up.
Before migrating, pull a manual list of every contact in an active stage. Verify each one: is the quote still open? Is the job still on the calendar? Then migrate those records first, separately from the bulk contact import, and confirm each one lands in the correct stage in the new system before anything else goes over.
Active leads go in first. Never after the bulk import.
Step 5: Set Up Automations Before You Go Live
This is the step most businesses skip. They migrate the data, start entering new leads into the new system, and plan to build the automations over the following weeks — during which time leads are falling through because nothing is triggering.
Before you start using the new system for live leads, configure the automations that need to catch them:
- New inquiry → automatic acknowledgment based on whether the contact came in by phone or form
- Quote sent → follow-up sequence that runs for several days and stops the moment they reply
- Job complete → review request sent the next day
- New contact → staged to the correct pipeline step automatically based on lead source
A business automation workflow built on top of a clean CRM is what makes consistent follow-up happen without relying on manual memory. But it needs to be in place the day the new system goes live, not three weeks later when several leads have already slipped.
If automated texts are part of your follow-up system, they fall under the federal TCPA — the FCC's rules on unwanted calls and texts govern consent requirements and how you can message a contact. Any email sequences that go out through the new system need to comply with the FTC's CAN-SPAM requirements, including a working unsubscribe mechanism. Getting this right from day one is easier than correcting it after launch.
What to Measure After the Migration
A successful migration means the system is in place to be evaluated. Once you're live in the new CRM, track:
- How quickly new inquiries are receiving a first response
- Whether the quote follow-up sequence is firing on schedule for each "Quoted" contact
- How many leads are moving from Quoted to Booked versus going cold
- Whether review requests are going out after completed jobs
These are the signs the system is doing its job. If any of them are breaking, the cause is usually a stage-mapping issue or a gap in automation — both fixable early before they affect too many leads. If you're not sure where the pipeline is breaking down, a workflow audit maps the full sequence from first contact to closed job.
FAQs
How do I know if it's time to migrate to a new CRM?
The clearest sign is that you can't trust the data. If you can't quickly see which leads are active, which were quoted but haven't responded, and which are past customers due for a seasonal check-in, the system isn't doing its job. A secondary sign is that the automation options in the current platform are too limited to build the follow-up you need.
What happens to active leads during a CRM migration?
If you handle them separately — pulling a manual list and migrating them first, before the bulk contact import — they move intact. The risk is treating them like all other contacts and letting them get lost in the shuffle. Confirm each active-pipeline contact landed in the correct stage in the new system before you go live.
Do I need to clean up my CRM before migrating?
Yes. Migrating a messy CRM gives you a messy CRM in a new platform. Stage cleanup, deduplication, and fixing bad contact data should happen in the current system before export — not after import. If the database is large or complicated, Lumen's CRM migration service handles the audit, cleanup, and move as a single project.
Can I run two CRMs at the same time during the transition?
For a short cutover window, yes — but set a firm end date. Running both in parallel indefinitely means contacts get entered in both systems and neither stays accurate. A cleaner approach is to migrate the active pipeline, verify it in the new system, then stop entering anything in the old one.
What should be automated in the new CRM from day one?
At minimum: an automatic acknowledgment for new inquiries, a quote follow-up sequence that stops on reply, and a post-job review request. Those three handle the highest-value follow-up moments and can be configured before the migration runs. Add additional layers — cold lead reactivation, seasonal check-ins — once the core pipeline is running cleanly.
If you're switching CRMs and want to make sure your data moves cleanly and your follow-up automations are ready from the start, Lumen can scope the full migration. Book a free strategy call to map out the project.