# When a client asks for a merge you think is wrong | Dedupely

> A client wants two records merged and you think they're different. How consultants push back, find the real need and protect the CRM without losing the client.

- URL: https://dedupe.ly/blog/partners/client-asks-for-wrong-merge
- Section: blog
- Published: 2026-11-18
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

Skip to content
[New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication)
[Blog](https://dedupe.ly/blog)
[Partners](https://dedupe.ly/blog/partners)

## When a client asks for a merge you think is wrong

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated November 18, 2026
#
min read
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.
Example
Say a client asks you to merge "Acme UK" and "Acme US" because their account report shows two rows. Merged, both offices' contacts, deals and owners sit on one company, and the regional teams can no longer report on their own pipeline. A parent company link gives the client one row in the report and keeps both offices.

### 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.
Pro tip
Add a line to your kickoff agreement saying the client approves the definition of a duplicate and any merges outside it. When this comes up later, you point to the agreement instead of debating it.

### 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.
[Run your next client cleanup](https://v2.app.dedupe.ly/signup)

### 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.
Behind the article

### Gaby Salinas

Marketing Assistant at Dedupely
Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.
As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.
[Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns)

### Contact us

We’d be happy to help you get this set up.

#### Write us a message

We probably know the answer to your question already
help@dedupe.ly
Email copied to your clipboard!
[Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
- [Duplicates When to review high-stakes CRM merges yourself Key, big and VIP accounts deserve a person on every merge. Keep them out of bulk merges, check what's attached, pick values field by field and preview. Gaby Salinas October 28, 2026](https://dedupe.ly/blog/duplicates/merge-high-stakes-crm-duplicates-with-outcome-control)
- [Team Collaboration Getting sales, marketing and support to agree on duplicates Sales, marketing and support use the same records in different ways. Agree on what a duplicate is, write it down and decide which values win per field. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/team-collaboration/agree-on-what-counts-as-duplicate)
- [Duplicates Can you undo a merge in a CRM? Can you undo a merge in a CRM? In most, no. See what each CRM allows after a merge, and how to recover from a wrong merge. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/duplicates/can-you-undo-a-crm-merge)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Try for free](https://v2.app.dedupe.ly/signup) [Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)
[Or sign up with Google](https://v2.app.dedupe.ly/signup/google)
Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)
