Migrating Customer Data to a New CRM
The demo decides which CRM you buy; the migration decides whether you keep it. Most projects fail here — not on features, but on six years of customers in three spreadsheets, vehicles under two spellings, and job history nobody has cleaned since 2021. This is the sequence that moves data without losing it.
1 · Audit before anything moves
- List every source. CRM exports, invoicing tools, spreadsheets, the scheduling app someone's cousin built — all of it, including the "temporary" file from 2022.
- Count and compare. Customer rows, vehicles or equipment, open jobs per source. If two sources both claim 1,200 customers, find out which 300 overlap before you import anything.
- Declare a system of record. For each data type — contacts, vehicles, jobs, invoices — name the one source that wins on conflict. Everything else becomes a supplement.
- Define what "clean" means for you. Required fields, phone format, naming conventions. Decide now, because the import will enforce whatever you decide — or enforce nothing.
2 · Clean the data you're carrying
- Dedupe first Merge duplicate customers before export, not after import — deduping inside the new system is harder because you no longer know which record is the original.
- Standardize formats Phones, emails, addresses, and dates in one shape. Mixed formats are the top reason field mapping quietly truncates data.
- Archive the dead Five-year-old prospects with no job history add noise and cost. Export them cold-storage, then migrate the living.
- Verify key identifiers VINs, equipment serials, plate numbers — one wrong character orphans a service history that took years to accumulate.
3 · Map fields explicitly — in writing
Build a one-page table: source column → destination field → transformation, if any. Every column in the export must land somewhere or be deliberately discarded. The deliberate discards matter as much as the mappings: "old_full_address_notes" either becomes a history note or gets archived — it must never silently vanish. If your new vendor handles the import, review their mapping sheet line by line anyway; it is your data, and you are the only party who knows what "customer note (2023)" contains.
4 · Trial import, then cut over
- Full trial into a sandbox. Not a sample of 50 rows — the entire dataset, so row counts, rejected-record logs, and relationship links get validated for real.
- Spot-check relationships. Open ten random customers: do their vehicles, open jobs, and invoices still hang together? Relationships are where imports break quietly.
- Run both systems for one week. Enter new work in both. Parallel running costs a week; a botched cutover costs a season.
- Freeze, final-sync, switch. One scheduled hour where the old system goes read-only, deltas transfer, DNS or bookmarks change, and the new system opens for business.
5 · After the move
Keep the old system exported and untouched for at least one billing cycle — questions will surface ("what was the total on invoice 4471?") and the answer should be findable. Then confirm the boring things daily for two weeks: invoices numbering correctly, reminders firing, reports matching last month's totals within rounding. For hands-on help, our service tiers cover migration as part of onboarding, and support answers within 24 hours when a number looks wrong. The CRM selection checklist covers the questions to ask before you get here.