CRM duplicates from a sales manager's point of view

Many sales managers don't go looking for duplicates. They find them through the problems duplicates cause: two reps arguing over an account, a commission paid twice, a forecast that doesn't hold.

All of those matter, but one comes first in my experience. Ownership is the problem that pulls a sales manager into the CRM. It's also the one that damages the relationship with whoever runs it.

In this post, I'll go through how duplicates show up for sales managers, starting with ownership, and what I'd do about each one.

Ownership is where duplicates hurt most

When a customer exists twice, each record can have its own owner. One rep has worked the account for months, and another gets the duplicate from a form, an import or a routing rule.

Both reps are right from where they sit. Each one sees a record with their name on it, and the manager has to decide who keeps the customer.

What I see: Of all the ways duplicates affect sales teams, ownership is the biggest. Territory disputes, double commissions and forecast problems all matter, but ownership is where the arguments start.

What to do: Write down how ownership is decided when two records match. For example, the owner of the oldest record keeps the customer, or the rep with the most recent activity does. Agree on it before any merge, since a merge keeps only one owner.

The blame lands on whoever runs the CRM

Ownership problems don't stay inside the sales team. When a rep loses an account to a duplicate, the complaint often goes to the CRM admin or RevOps.

What I see: When ownership is wrong, sales blames whoever is responsible for the CRM. Their own part in it rarely comes up: creating a new record without searching first, or importing a personal list.

The CRM owner does control the routing rules, forms and integrations. But reps create records too, and those records follow whatever habits the team has.

What to do: Treat ownership disputes as a shared problem between sales and the CRM owner. A regular check-in between sales and the CRM admin, built on real examples, is where that starts.

Territories don't hold when one account exists twice

Territory rules assign records by fields like country, region, industry or company size. A duplicate can carry different values in those fields, so it follows a different rule.

One record says the account is in Texas and the other says California, because one holds the headquarters address and the other a branch. Two territories, two reps, one customer.

Not every match is a duplicate, though. A branch office with its own buyer may be a separate account for your team. Merging it would erase a territory you meant to keep.

What to do: Decide which value wins for every field your territory rules read. Then decide whether branches and subsidiaries count as duplicates for your team, since that answer differs from team to team.

Commissions and forecasts follow the duplicates

When a deal exists twice, the pipeline counts it twice. Forecasts look bigger than they are, and if both deals close, two reps can be paid for one sale.

Duplicate deals often start with duplicate contacts or companies. Two reps each create a deal on their own record, and neither sees the other's. We cover the details in how duplicate deals inflate your pipeline.

What to do: Check for duplicate deals before forecast calls and before commissions are paid. Fix the duplicate contacts and companies too, since they're where many duplicate deals begin.

Customers notice before the report does

Two owners also means two reps reaching out. A customer gets a cold email from one rep a week after a call with another. Or a paying customer gets pitched as a prospect.

Leads are a common starting point, because they arrive fast and often have no owner yet. Duplicate leads form faster than contacts, and each one can be routed to a different rep.

What to do: Ask reps to tell you each time they find a customer that another rep is working. Each report points to a duplicate and to the source that created it.

What I'd do next, in order

1. Write down how ownership is decided when two records match.
2. Bring ownership disputes to a regular conversation with the CRM owner.
3. Decide which value wins for every field your territory and routing rules use.
4. Agree on whether branches and subsidiaries count as duplicates for your team.
5. Check for duplicate deals before forecast calls and commission runs.
6. Ask reps to search for a customer before creating a new record.

Protecting the owner field also belongs in your wider data rules. Our data governance guide covers who decides on those rules.

Fix ownership first, and the rest gets easier

Duplicates reach sales managers as disputes between people. Ownership is the biggest of them, and it tends to land on whoever runs the CRM, even when reps' habits play a part.

A written ownership rule, a regular conversation with the CRM owner and clear decisions on territory fields solve much of it. Commissions and forecasts get easier once each customer has one record and one owner.

Frequently asked questions