Clean data before CRM migration: a practical guide
Most CRM migrations that disappoint do not fail on the technology. They fail on the data. The platform goes live on time, the integrations work, and then users log in, find the same duplicate accounts and half-empty records they had before, and quietly go back to their spreadsheets. If you clean your data before a CRM migration rather than after, you migrate less, you migrate better, and go-live lands on a foundation people trust from day one.
In short
- Clean CRM data before migrating, not after, because migrating dirty data recreates duplicates and inconsistencies in the new system, where fixing them disrupts users who depend on it.
- A pre-migration cleanup has seven steps: profile, deduplicate, standardise, validate against the destination, enrich critical gaps, archive what you do not need, and test with a trial run.
- For a mid-sized CRM, plan an afternoon for a baseline scan, one to two weeks to bulk-merge core tables, and a few days for formats and rules.
Why you clean before you migrate, not after
It is tempting to move everything across and tidy it up later, once the new system is live. In practice, later rarely comes, and the mess is harder to fix once it is tangled up with live processes and real users.
Migrating dirty data simply recreates every problem in a new place. Duplicate accounts get duplicated again. Inconsistent formats stay inconsistent. Orphaned records that pointed nowhere in the old system point nowhere in the new one. Worse, the new environment is now in daily use, so every cleanup you attempt risks disrupting someone’s work. Cleaning at the source, before the move, means the problems are dealt with once, in a controlled way, before anyone depends on the data.
You pay to store, migrate and license every record you bring across. Moving thousands of duplicates and dead contacts is paying to transport rubbish. Cleaning first means you move a smaller, healthier dataset, which is faster to migrate and cheaper to run.
What dirty data actually costs a migration
Before you can clean data, it helps to know what you are looking for. In most CRM systems the same handful of problems show up again and again.
Duplicates
The same customer, contact or account entered two, three or more times, usually because exact-match rules never caught small differences in spelling, formatting or naming. Duplicates split a customer’s history, break reporting, and get two salespeople calling the same prospect.
Incomplete records
Accounts with no country, leads with no source, contacts with no email. Every gap is a segment you cannot target and a report you cannot trust.
Inconsistent formatting
Countries written five different ways, phone numbers in half a dozen styles, company names with and without their legal suffix. To a computer these are all different values, so grouping, filtering and deduplication all suffer.
Invalid data
The stuff that looks fine but is not: malformed email addresses, numbers where text should be, dates that cannot be real.
Orphaned relationships
Records that reference a parent account or owner that no longer exists, which quietly break as soon as they land in the new system.
The pre-migration data cleaning checklist

A dependable clean-up follows a clear sequence. You can run this yourself or have a partner run it for you, but the steps are the same.
- 1
Profile and assess
Before you touch anything, measure the problem. How many duplicates, how many incomplete records, how many invalid emails, how many orphaned links. Profiling turns a vague sense that the data is messy into a concrete scope you can plan around.
- 2
Deduplicate and merge
Identify duplicates using fuzzy and phonetic matching, not just exact matches, so Jon Smith and John Smith, or Microsoft A/S and Microsoft AS, are caught. Then merge them safely, keeping the richest field values and preserving the full activity history so nothing is lost.
- 3
Standardise formats
Bring countries, phone numbers, currencies, job titles and company names into a consistent format. This is what makes the data groupable and reportable once it is in the new system.
- 4
Validate against the destination
Every target CRM has required fields, picklists and formats. Validate your cleaned data against them before you import, so records are not silently rejected or truncated during the migration.
- 5
Enrich and fill critical gaps
Where key fields are missing and the information exists elsewhere, fill the gaps. Focus on the fields that drive segmentation, routing and reporting.
- 6
Archive or exclude what you don’t need
Not every record deserves a seat in the new system. Old, inactive or irrelevant data can be archived rather than migrated, which shrinks the move and keeps the new environment clean.
- 7
Map and test with a trial run
Map old fields to new, run a test migration on a sample, and check the results before the full load. A trial run surfaces mapping problems while they are still cheap to fix.
Cleaning as you move, not just before
The strongest migrations treat data quality as part of the move itself, not a separate project bolted on the front. This is how Techdio approaches it. Our Data Quality App for Dynamics 365 handles the profiling, deduplication, standardisation and validation, while our Migr8 migration toolset performs a structured, one-to-one migration into Dynamics 365 that preserves history and integrity. Clean and migrate become one process rather than two, which is faster and far less risky than cleaning in one tool and moving in another.
It also sets you up for what comes after go-live. Because the same data quality rules that cleaned the data can keep running inside the new system, quality does not immediately start sliding back. You arrive clean and you stay clean.

Common mistakes when cleaning before a migration
Four patterns account for most failed cleanups, all avoidable.
Cleaning in the target instead of the source
Migrating dirty data “to fix later” means the mess arrives in your new system with new record IDs, broken assumptions and no baseline. Clean where the data lives today; migrate the clean result.
No baseline measurement
If you do not know the duplicate rate and completeness numbers before you start, you cannot prove the cleanup worked, or notice when it regresses. Scan first, clean second.
Ignoring the integrations
A perfect one-time cleanup is undone in weeks if the ERP connector or web forms keep writing unmatched records. Fix the inbound flows as part of the migration, not after it.
The big-bang cleanup
Trying to fix every field on every table before go-live stalls migrations for months. Prioritize what the new system’s day-one processes actually need: the tables you migrate, the fields your workflows read. The rest can be cleaned on a schedule after go-live.
How long does pre-migration cleaning take?
Less than most teams fear, if it is tooled properly. A realistic budget for a mid-sized CRM with 100,000 to 1M records:
One afternoon
A full duplicate scan and completeness baseline.
One to two weeks
Review and bulk-merge duplicates on the core tables (Accounts, Contacts, Leads). The review is human time; the merging is automated.
A few days
Standardize formats and fix rule violations in bulk.
The work that takes months in horror stories is almost always manual, spreadsheet-driven cleanup. With detection, merge and standardization automated, data cleaning stops being the reason a migration slips.
Not migrating, just cleaning? Use the standalone CRM Data Cleanup Checklist.
Frequently asked questions
Timing
Should I clean my data before or after the CRM migration?
Before. Cleaning after go-live means fixing problems while users depend on the system, which is slower, riskier and usually gets deprioritised. Clean at the source, migrate the healthy result.
How long does pre-migration data cleaning take?
It depends on the size and state of the data, which is why profiling comes first. Profiling gives you a realistic timeline instead of a guess, and archiving records you do not need often shrinks the job considerably. For a mid-sized CRM, plan an afternoon for the baseline, one to two weeks for the core tables and a few days for formats and rules.
Automation and after go-live
Can data cleaning be automated?
Largely, yes. Deduplication, standardisation and validation can all be automated with the right rules, with human review reserved for the borderline cases. Automation is what makes cleaning a large dataset practical.
What happens to data quality after we go live?
Without ongoing rules, it decays, because new data flows in through imports, forms and manual entry every day. Continuous rules that run at the point of entry and on a schedule keep a freshly migrated system clean over time.
Can duplicates be stopped at the source during and after the migration?
Yes. The Data Quality App can refuse the save for end users and integrations alike, and specific service accounts can be allowed to create duplicates that are merged automatically afterwards by your master-record rules. See the comparison with native duplicate detection.
Migrating to a new CRM? Start with the data.
A clean migration is the difference between a system people trust and one they work around. If you are planning a move to Dynamics 365, or cleaning up before one, Techdio can profile your data, show you exactly what you are dealing with, and clean it as part of the migration.
Improve your data quality in Dynamics 365
The Data Quality App keeps records complete and correct with data quality rules at the point of entry, finds duplicates with fuzzy and phonetic matching, resolves them with bulk merge and measures your data health over 30, 60 and 90 days. Native in your own environment, free for 15 days.
