# Why matching and merging are separate decisions | Dedupely

> Matching decides which records are duplicates. Merging decides what the final record keeps. Treat them as two decisions to avoid wrong merges.

- URL: https://dedupe.ly/blog/matching-vs-merging-duplicates
- Section: blog
- Published: 2026-10-19
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

[Blog](https://dedupe.ly/blog)
Duplicates

## Why matching and merging are separate decisions

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated October 19, 2026
#
min read
TL;DR
- Matching decides which records are duplicates and belong in the same set.
- Merging decides which record survives and which value wins in each field.
- A correct match can still produce a wrong merge if the merge rules are wrong.
- Merge/purge is an older name for matching duplicate records, merging them and removing extras.
- Dedupely lets you decide what matches and which values win separately, then preview each merge.
"Dedupe and merge" sounds like one step. In practice, it's two decisions: which records are the same, and what the final record should look like.
When teams treat them as one, problems are hard to trace. A wrong owner after a merge gets blamed on the match, or a good match gets rejected because the merged record looked wrong.
In this post, you'll see what each decision controls, what "merge/purge" means and what goes wrong when the two blur. You'll also see how to test each one on its own before you merge in bulk.

### Matching finds the set, merging decides the result

Matching compares records and groups the ones you consider duplicates into a set. It answers one question: are these the same customer, company or deal?
Merging takes a set and turns it into one record. It answers a different question: what should that record keep?
| | Matching | Merging |
| --- | --- | --- |
| The question | Are these records the same? | What should the final record keep? |
| What you decide | Which fields to compare and how strictly | Which record survives and which value wins in each field |
| What changes in the CRM | Nothing, until you merge | Records are combined, and the extras are removed |
| When it goes wrong | Separate records are grouped, or real duplicates are missed | The right records combine, but the wrong values survive |
| How you test it | Read a sample of matched sets | Preview the merged result of a sample |

### What "merge/purge" means

Merge/purge is an older term from mailing lists. Teams combined lists, found records that referred to the same person or address and kept one entry.
The idea carries over to CRMs. Matching finds the duplicates, merging combines them into one record, and the purge is the removal of the extra records.
In a CRM, the purge happens as part of the merge. The extra records are deleted or archived, depending on the CRM, and their activity and associations usually move to the surviving record.

### The matching decision

Matching is about evidence. You choose the fields that identify a record, like email for contacts or domain for companies, and decide how strictly each one must match.
What counts as a duplicate is case by case. What one team considers a duplicate, another may not, like two branches that share a domain. That's why the same records can need different criteria in different CRMs.
Our posts on
[how duplicate matching works](https://dedupe.ly/blog/duplicate-records-in-crm-guide)
and
[which fields to match on](https://dedupe.ly/blog/duplicate-records-in-crm-guide)
cover match types and fields in detail.

### The merging decision

Merging is about the result. Once you agree that records belong together, you still have to decide what survives.

#### Which record survives

One record in the set becomes the primary. Common choices are the oldest record, the newest, the last updated or the one with the most data.
The choice matters because the primary record often keeps its record ID and some of its values by default. In some CRMs, a merge creates a new record ID instead.

#### Which value wins in each field

Each field can follow its own rule. The phone number might come from the most recent record, the owner from the oldest and the lifecycle stage from the most advanced.
Fields that hold several values, like tags, can sometimes combine values from every record. Single-value fields need one winner.

#### What happens to related records

Activities, deals and other associations usually move to the surviving record. Check how your CRM handles them, since that's often what people miss most when a merge goes wrong. Our post on
[merging CRM records without losing data](https://dedupe.ly/blog/merge-crm-records-without-losing-data)
goes deeper.

### What goes wrong when the two blur

Many cleanup mistakes come from using one decision to fix the other. Three come up often.

#### Blaming the match for a bad merge

Two records for the same company merge, and the account ends up with the wrong owner. The match was right. The owner rule was wrong.
Tightening the match here would hide real duplicates. Fixing the owner rule solves the problem for every future merge.

#### Rejecting good matches

When a merged record looks wrong, it's tempting to reject that kind of match. But a rejected match stays out of future searches, and the duplicates stay in the CRM.
Reject a match only when you're certain the records aren't duplicates. If the problem was the result, change the merge rules instead.

#### Trusting every match the same way

An exact email match and a match on similar names aren't equally certain. They can share merge rules, but they deserve different handling.
Merge the obvious duplicates, like exact matches on email or domain, in bulk. Send looser matches to review, where someone checks each set before it merges.
Example scenario
A team merges contacts on exact email, and reps complain that lead sources disappeared. The matches were correct, but the rule kept the newest record's lead source. The team changes it to keep the oldest and previews the next round.

### Test each decision on its own

Test the match first. Read a sample of matched sets and ask one question: are these the same record? Adjust the criteria until the answer is yes for the sets you'd merge.
Then test the merge. Preview the result for a sample, including a few edge cases, and check the fields that matter most, like owner, stage and email opt-out.
Once both hold up, you can merge in bulk. When your rules are tested, you can merge new duplicates you're certain of, like exact email matches, automatically on a schedule.
Pro tip
** When a merge looks wrong, ask first whether the records belonged together. If yes, change the merge rule. If no, change the matching criteria.

### How Dedupely keeps matching and merging separate

In Dedupely, build searches to find candidate matches and set merge rules to decide which values survive. Confirm identity, preview the result and send uncertain sets to review. Check your connector's supported activities, associations and exceptions; field rules alone do not establish that all linked data transfers.
[Build your first duplicate search](https://v2.app.dedupe.ly/signup)

### Two decisions, one clean record

Matching and merging answer different questions. Matching decides whether records are the same; merging decides what the final record keeps. Merge/purge is the older name for both, plus removing the extras.
Keeping the decisions apart makes problems easier to fix. A wrong group means changing the criteria, and a wrong value means changing the merge rule. Test each one on a sample, and bulk merges become far less risky.

### Frequently asked questions

#### What is the difference between matching and merging?

Matching decides which records are duplicates by comparing fields like email, domain or name, and groups them into a set. Merging turns that set into one record, deciding which record survives and which value wins in each field. Matching changes nothing in the CRM until you merge.

#### What does merge/purge mean?

Merge/purge is an older term from mailing lists. It means combining lists, finding records that refer to the same person or address, merging them and removing the extras. In a CRM, the same idea is matching duplicates, merging each set into one record and removing the extra records.

#### What does dedupe and merge mean?

It means finding duplicate records and combining each set into one. Deduplication covers the whole process, from matching records that refer to the same customer to merging them. The merge step decides which record survives and which values it keeps, so the result has one record per customer.

#### Can you match duplicates without merging them?

Yes. Matching only groups records into sets, so you can review them, count them or send them for review without changing anything. Matching first is a good way to measure how many duplicates you have, then decide which sets to merge, review or reject.

#### Which record should survive a merge?

It depends on your data, and common choices are the oldest record, the newest, the last updated or the one with the most data. Keeping the oldest record can keep its record ID in place, depending on the CRM. Then choose the winning value field by field.
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/hampus-isaksson/dedupely-zoom-schedule)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
[Duplicates Should you merge duplicates or delete them? Merge duplicates that carry history, associations or attribution. Delete only junk, test and spam records. A simple rule for each case. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/merge-or-delete-duplicates)
[Duplicates Placeholder values that make records look like duplicates Values like test@test.com, John Doe or 1234567890 group unrelated records as duplicates. How to spot them, leave them out and keep them from winning. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/placeholder-values-false-duplicates)
[Duplicates The complete guide to duplicate records in your CRM Duplicate records are CRM records for the same person or company. Clean the ones you have in phases, by certainty, then stop new ones from spreading. Gaby Salinas October 15, 2026](https://dedupe.ly/blog/duplicate-records-in-crm-guide)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Talk to sales](https://meetings.dedupe.ly/meetings/hampus-isaksson/dedupely-zoom-schedule)[Try for free](https://v2.app.dedupe.ly/signup)
[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)
Skip to content