Help for owners
My CRM is full of duplicate contacts and wrong data
Short answer
A CRM fills with duplicates when records arrive from several sources, forms, imports, integrations and staff typing, with no single rule for what counts as the same person. Clean up in order: back up, decide the matching rule, merge a small batch, then fix the sources so the mess does not return.
Does this sound like your situation?
- The same customer appears two or three times with different details.
- Emails bounce because addresses are old or mistyped.
- Phone numbers, names and company names are in different formats.
- Reports of contacts, leads or revenue are inflated or contradict each other.
- Salespeople phone the same person twice.
Why does this happen?
Many sources write to the same list
Website forms, imports, event lists, email tools, a billing system and staff all create contacts. Each uses a different spelling or a different email, so none matches an existing record.
There is no single matching rule
Email is the common key, yet people use two addresses, share a company inbox or change jobs. Matching on name alone merges strangers, and matching on exact email misses real duplicates.
Integrations create instead of update
A link that looks up a contact by a field that is empty or formatted differently creates a new record every time, and the duplicates multiply with each run.
Free-text fields and no required fields
Country, job title, source and status typed by hand end up in dozens of spellings, so filters and reports silently drop records.
Nobody owns data quality
Cleanups are one-off and no rule stops the same mess returning, so it is rebuilt within months.
What can I do about it today?
- Export a full copy firstDownload all contacts, companies and deals to a file before changing anything, and keep it.
- Do not run an automatic merge on everythingA merge is hard or impossible to undo in many tools. Try it on twenty obvious pairs first and read the results.
- Look at where the duplicates came fromSort by source or creation date. If most appeared on one date, a single import or integration is the cause.
- Pause the import or link that creates themSwitch off the source that keeps adding duplicates until you know why.
- Agree what a duplicate isWrite a one-line rule such as same email, or same phone and company, so everyone cleans the same way.
When should I bring someone in?
- There are thousands of records and merging by hand is not realistic.
- Several systems share the same contacts and a merge in one will not reach the others.
- You cannot tell which integration keeps creating the duplicates.
How do I handle it?
- Back up and measureI take a full export and count duplicates by each candidate rule, so you can see how many each rule finds.
- Propose matching rules in plain wordsRules are tested on a sample and the borderline pairs are shown to you, not merged automatically.
- Merge in batches with a logEach batch records which record was kept and what was combined, so a mistake can be traced.
- Standardise the fieldsPhone numbers, countries and statuses are normalised, and bad emails are flagged, not deleted.
- Stop the sourceImports and integrations are changed to look up before creating, and forms use a required, controlled field.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can duplicates be removed automatically?
Exact matches, yes, with care. Near matches should be reviewed, since a wrong merge combines two different people.
Will I lose notes and history?
Not if the merge keeps the activity from both records. That is why a backup and a small test batch come first.
Why do they come back?
Because the sources still create them. Clean-up without fixing the sources lasts only a few months.
Should I delete old contacts?
Be careful. Mark them inactive first. Some data protection rules also apply, so keep what you are legally required to keep.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.
For your developer: the technical fixes
The second identical row with a NULL is accepted instead of failing with a duplicate key errorA UNIQUE constraint in PostgreSQL still lets duplicate rows in when a column is NULLunique: true in the schema, but two documents with the same value are savedMongoose saves duplicate documents although the field is uniqueERROR 1265 (01000): Data truncated for column 'price' at row 1LOAD DATA turns empty CSV fields into 0 or fails with Data truncated