View as Markdown

TL;DR

  • When a report shows the same customer twice, it's tempting to remove the duplicate in the report and move on.
  • That fixes one number in one report, while the CRM, and every other report and tool, stays wrong.
  • Each report then needs its own fix, and the fixes start to disagree with each other.
  • Reps, automations and integrations still work from the duplicate records.
  • Dedupely fixes duplicates in the CRM itself, so every report built on it starts from one record per customer.

A dashboard shows more customers than finance has. Someone finds the reason: the same company is in the CRM three times. The fastest fix is in the report: group by domain, remove repeated rows, or add a "distinct" step to the query. The number looks right by the end of the day.

It's a reasonable short-term fix. The problem is that it fixes the report, not the data. This post covers why report-level fixes don't hold up, and when they're still useful.

What a report-level fix does

A report-level fix hides duplicates from one view. It doesn't change the records underneath. Common versions:

  • A "distinct" or "remove duplicates" step in a spreadsheet or query.
  • Grouping by email or domain so several records show as one row.
  • A manual exclusion list of records the analyst knows are duplicates.
  • A lookup table that maps several record IDs to one "real" customer.

All of these work for the report they're built in. None of them reach the CRM.

Why it doesn't fix the CRM

What the report fix does What stays broken
Shows one row per customer The CRM still has two or three records
Adds up revenue correctly Deals and activities are still split across records
Removes repeats from one list Emails, sequences and calls still use both records
Works in one dashboard Every other report needs the same fix, built again

Reps still see the duplicates. They call the wrong record, miss history and create more duplicates while looking for the right one.

Automations still run on both records. Workflows, lead scoring and routing treat each record as a different person or company.

Other tools still sync both. Your marketing tool, support desk and any data export get the duplicates as they are.

Report fixes drift apart

The bigger problem shows up a few months later. Sales has a dashboard that groups by domain. Marketing has a spreadsheet that groups by email. Finance has its own exclusion list. Each fix is built differently, so each report gives a slightly different number for the same thing.

Now the conversation is about which report is right, not about the business.

When a report-level fix is fine

Report fixes aren't wrong. They're useful as a stopgap:

  • For a report due today, while the CRM cleanup is planned.
  • For historical data you can't or don't want to change.
  • As a check: comparing the grouped count with the raw count shows how big the duplicate problem is.

Treat it as a measurement, not a solution.

Fix it where the data lives

The lasting fix is in the CRM:

  1. Find the duplicates for the objects your reports rely on, usually companies, contacts and deals.
  2. Merge them, with rules for which values win, so history and deals end up on one record.
  3. Catch new ones on a schedule, so the reports stay right without extra steps.
  4. Remove the report workarounds once the data is clean, so every report counts the same way.

How Dedupely fixes duplicates at the source

Dedupely finds and merges duplicates in the CRM itself, in HubSpot, Salesforce, Pipedrive, Close, Nimble and Google Contacts. When records merge, activities and associations, like linked companies, deals and contacts, move to the merged record, so reports built on the CRM count each customer once. Merge Rules decide which values win in each field, and Auto Merge can merge new duplicates on a schedule so the reports don't drift again.

Fix duplicates in your CRM

One fix, every report

Removing duplicates in a report fixes one number. Merging them in the CRM fixes every report, every rep's view and every tool that syncs with it. Use report fixes as a stopgap and a measurement, then fix the data where it lives.

Frequently asked questions

Can I just remove duplicates in my reports instead of the CRM?

For one report, as a stopgap. The CRM, your reps and your other tools still work with the duplicates, and every other report needs its own fix.

Why do my reports show different numbers for the same thing?

Often because each report handles duplicates differently, grouping by email in one and by name or domain in another.

Is a report-level fix ever the right choice?

Yes, for a report due today or for historical data you don't want to change. Use it while you plan the CRM cleanup.

How do I know how many duplicates my reports are hiding?

Compare the raw row count with the count after grouping by email or domain. The difference is a rough estimate.

What should I do with report workarounds after a cleanup?

Remove them, so every report counts records the same way.