TL;DR
- Clients sometimes ask you to merge records that aren't the same person, company or deal.
- Before you push back, find out what problem they're trying to solve.
- Often a link, a parent company or a cleaner report solves it without a merge.
- If they still want the merge, put the risk in writing and merge one set first.
- In Dedupely, rejected sets stay out of future searches, and Merge History keeps every merge's original values.
Sooner or later, a client points at two records and says "merge these". You look, and they're not duplicates. Two branches of one company. A parent and its subsidiary. Two people who share an inbox. Two deals that happen to have the same name.
You're the one who knows how merges work, so it's your job to say so. This post covers how to push back without turning it into an argument, and what to do if the client still wants the merge.
Why clients ask for the wrong merge
| What they ask | What's usually behind it |
|---|---|
| "Merge all the Acme companies" | They want one view of the account, or one number in a report |
| "Merge these two contacts" | Two people share an email or a phone, and reps keep calling the wrong one |
| "Merge these deals" | A deal was split in two, or a renewal was logged as a new deal |
| "Merge everyone at this domain" | They want fewer records, not fewer duplicates |
In almost every case, the request is a symptom. The real problem is a report, a routing rule or a view in the CRM.
Step 1: Ask what they're trying to fix
Don't start with "that's wrong". Start with "what happens today that you want to stop?" The answer tells you whether a merge is the right tool.
- A reporting problem can often be solved with a parent company link or a grouped report.
- A rep confusion problem can be solved with clearer names, owners or a note on the record.
- A real duplicate you missed? Then they're right, and you merge it.
Step 2: Show what the merge would do
Clients rarely see what a merge changes. Show them, with their own data:
- Which record survives and which one disappears.
- Which values are kept in the fields that disagree.
- What moves: activities, deals and linked records all end up on one record.
- What can't be split again without manual work.
Step 3: Offer the alternative
Bring a fix that solves their problem without the merge:
- A parent and child link between related companies.
- A report or view that groups records the way they want to see them.
- A field that marks the relationship, like "same household" or "shared inbox".
- Clearer record names so reps stop picking the wrong one.
Step 4: If they still want it
It's their CRM. If the client still wants the merge after seeing what it does:
- Put it in writing: what will merge, what changes and that you advised against it.
- Merge one set first and let them check the result in the CRM.
- Keep a record of the original values before you merge the rest.
- Don't add it to an automatic rule unless they want every similar set merged the same way.
How Dedupely helps with disputed merges
In Dedupely, you can reject a set you and the client agree isn't a duplicate, and it stays out of every future search for that object, including automatic merges. Before merging, a preview shows which record survives and which values win. For a set the client insists on, you can merge just that set, and Custom Merge lets you edit values by hand first. Merge History records every merge with each original record's values, and its CSV export keeps the original values and IDs. Most merges can be undone for 30 days from Merge History, but treat every merge as permanent.
Find the need behind the request
A wrong merge request is usually a real problem with the wrong fix attached. Ask what they want to change, show what the merge would do, offer a fix that keeps the records apart and, if they still want it, merge one set with their sign-off in writing.
Frequently asked questions
What do I do when a client wants to merge records that aren't duplicates?
Ask what problem they're trying to solve, show them what the merge would change and offer a fix that keeps the records apart, like a parent company link or a grouped report.
Should I refuse to do the merge?
Advise against it plainly, but it's the client's CRM. If they still want it, get their approval in writing and merge one set first.
How do I show a client what a merge will change?
Walk through one set: which record survives, which values win and what moves to the surviving record.
Can I stop the same records from being suggested again?
In Dedupely, yes. Rejected sets stay out of future searches for that object, including automatic merges.
What if the merge turns out to be wrong?
Most merges in Dedupely can be undone for 30 days from Merge History. Merge History also keeps the original values, so you can rebuild records if needed.




Pipedrive user