How do you find duplicate contacts in a CRM?

Search on the field that is unique, not on the name. Email first, then phone, then company plus surname. Merge in one direction and fix the intake.

Syncek Team · CRM reference library

/ 3 min read / Art. #36

Find duplicates by sorting on the field that is supposed to be unique, not on the name. Email address first, because it is the only field most people fill in consistently. Then phone number with the formatting stripped. Then company plus surname, which catches the cases where one record has a work address and the other a personal one. Names alone are the worst place to start, because the same person appears as Bob, Robert and R. Smith and none of those sort together.

Work in that order, and know what each pass catches

Email catches the bulk and produces almost no false positives. Two records with one address are one person.

Phone catches the records created from a call or a business card, where nobody typed an email. Strip spaces, dashes and country codes before comparing, or the same number in two formats will not match itself.

Company plus surname catches the rest, and it is the pass that needs human eyes. Two people can share a surname at one company.

Decide which record survives before you merge

Pick the surviving record by which one carries the history, not by which one looks tidier. A sparse record with three years of activity is worth more than a complete one created last week.

Then merge in one direction only. Merging A into B and later B into A produces a record whose field values came from whichever run happened last, and nobody can tell which.

Merging is not reversible in most tools

Check before you start whether your CRM can undo a merge. Many cannot, and the ones that can often restore the record without its relationships.

Export the affected rows first. It is a two-minute step that turns an irreversible operation into a recoverable one, and it is the same reason a CSV gets checked before an import rather than after.

Then fix the intake, or they come back

Deduplication is maintenance until you change what creates duplicates. The usual sources are an import without a matching key, a form that does not check existing records, and two people entering the same lead from different places.

Give the CRM a unique field it can match on and the problem shrinks to the cases that genuinely need judgement. Otherwise you will run the same four passes next quarter, which is why a cleanup belongs on a calendar and why what you keep and for how long is worth deciding once.

Frequently asked questions

How do you find duplicate contacts in a CRM?

Sort on the field meant to be unique rather than on the name. Email address catches most of them with almost no false positives. Phone number, with spaces and country codes stripped, catches records created from calls. Company plus surname catches the remainder and needs review, because two people at one company can share a surname legitimately.

Why is searching by name a bad way to find duplicates?

Because the same person is entered as Bob, Robert and R. Smith, and those do not sort next to each other. Names also vary by accents, married names and transliteration. Sorting by name finds the duplicates that were already obvious and misses the ones costing you, which are the records created months apart by different people.

Which duplicate record should you keep?

The one carrying the history, not the one that looks more complete. Activity, deals and notes are expensive to recreate; empty fields are cheap to fill. A sparse record with three years of correspondence is worth more than a tidy one created last week. Merge in one direction only, so the result does not depend on which run happened last.

Can you undo a merge in a CRM?

Often not, and where you can the restored record frequently comes back without its relationships. Check your tool before you start rather than after. Exporting the affected rows first takes a couple of minutes and turns an irreversible operation into a recoverable one, which is worth doing even when the tool claims an undo exists.

How do you stop duplicates coming back?

Change what creates them. The usual sources are imports without a matching key, web forms that do not check existing records, and two people entering the same lead from different places. Give the CRM one field it can match on reliably, usually email, and the remaining duplicates shrink to the few that genuinely need a human decision.