Duplicate Contact Rate Calculator

The duplicate rate counts the extra copies, not every record in a duplicate set: a set of three records holds one real contact and two duplicates. Divide those extra copies by all contacts.

Also called: Duplicate record rate calculator · CRM duplication rate

  • Last updated
  • Formula tested against reference values

Your numbers

Every record that belongs to a group of matching records, including the one you would keep.

Number of groups of matching records. Your duplicate report or matching tool shows this.

Result

Duplicate rate
—

Calculating…

Extra duplicate copies
—
Records in a duplicate set
—
Contacts after merging
—
Average records per set
—

How to use this calculator

  1. Enter or choose total contact records.
  2. Enter or choose records in duplicate sets.
  3. Enter or choose duplicate sets.
  4. The duplicate rate updates as you type. Use Copy result or Share to keep it.

Method

Extra copies = Records in sets − Sets; Duplicate rate = Extra copies ÷ Total × 100; After merge = Total − Extra copies

Records in sets
all records that match at least one other record
Sets
groups of matching records, each of which merges into one

Worked example

  1. Extra copies = 3,000 − 1,200 = 1,800.
  2. Duplicate rate = 1,800 ÷ 25,000 × 100 = 7.2%.
  3. After merging: 25,000 − 1,800 = 23,200 contacts.

Of 25,000 contacts, 1,800 (7.2%) are extra copies; merging leaves 23,200 unique contacts.

What the result means

Duplicates split activity history, inflate contact-based charges and cause double emails. Fix the source as well as the records: most duplicates come from imports, web forms and integrations without matching rules.

Assumptions and limits

  • Your matching rule correctly identifies which records are the same person.
  • Product names such as Salesforce are trademarks of their owners. This calculator is independent, is not affiliated with or endorsed by any CRM vendor, and uses only the figures you enter.
  • Fuzzy matches can include false positives; review sets before merging.
  • Duplicates across objects (for example a lead and a contact for the same person) need a separate count.

Questions

Why not count every record in a duplicate set?

One record in each set is the one you keep. Counting all of them overstates the problem; the “Records in a duplicate set” output shows that wider figure separately.

What duplicate rate is acceptable?

It depends on how the data is used, but any rate that causes duplicate outreach or split ownership is worth fixing; track it after each import.