# Complex duplicate matches and how to find them | Dedupely

> Some duplicates only show up when several fields line up, and some matches look perfect but aren't. See how to combine fields and when to decide by hand.

- URL: https://dedupe.ly/blog/complex-duplicate-matches
- Section: blog
- Published: 2026-10-21
- 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

## Complex duplicate matches and how to find them

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated October 21, 2026
#
min read
TL;DR
- Complex duplicates only show up when several fields agree at once.
- Records sharing email, phone and address can still belong to different people or companies.
- A field like a tax ID or a person's name can tell close matches apart.
- Uncertain complex matches belong in review before anyone merges them.
- Dedupely lets you combine fields per search, show extra context and review or reject sets.
The easy duplicates share an email. A search on that one field finds them, and nobody argues about the merge.
The harder ones hide. One record has a work email and the other a personal one, or one has a phone number and the other a blank.
They only look like the same person once you line up three or four fields at once. The opposite also happens: records that agree on almost everything and still aren't duplicates.
In this post, you'll see common patterns of complex matches and why overlap alone doesn't prove identity. You'll also see how to combine fields, which field can settle a close call and when a person should decide.

### What makes a match complex

A simple match rests on one field that identifies each record, like email for contacts or domain for companies. A complex match rests on several fields that each prove little alone but agree together.
Name alone pairs strangers. Phone alone pairs family members and colleagues on a main line. Name, phone and company together point to one person far more often.
What counts as a duplicate is still case by case. What one team considers a duplicate, another may not. The fields you combine should follow your own definition of a duplicate.

### Common patterns of complex duplicates

These patterns come up often when teams look past exact email matches.
| Pattern | What lines up | What differs |
| --- | --- | --- |
| Different email addresses | Name and phone, sometimes company | The email address |
| One record with gaps | First and last name, sometimes phone | One record has an email, the other is blank |
| Same phone, different unit | Phone and most of the address | The apartment number, which can mean a typo or a different person |
| Country domains | The core domain, like example.us and example.fr | The country ending and sometimes the name |
| IDs written two ways | Company name and most of a tax ID | One ID ends in a check digit, the other doesn't |
| Duplicate deals | The first words of the deal title, plus email and phone | The end of the title, like the channel the lead came from |
Each one needs a different combination. Our guide on [which fields to match on](https://dedupe.ly/blog/which-fields-to-match-on-crm-duplicates) covers the usual pairs for each object. Our post on [records with no email](https://dedupe.ly/blog/find-duplicates-without-email) covers the blank-field case.
Example
A team searched contacts on exact email and found only a handful of duplicates, because many records had a name but no email. A second search matched first and last name and phone, where one record had an email and the other didn't. It found well over a thousand more.

### When overlap isn't identity

The same logic that finds complex duplicates can also pair records that aren't duplicates. When email, address and phone all agree, a merge looks safe. Sometimes the shared data belongs to a household or to one owner with several businesses.
Example
A small business owner found two company records that shared an email and most of their other details. One person ran both companies, but they were separate legal entities with different names and ID numbers. Told the overlap could justify a merge, she answered: "What you're asking me to do is to merge you and your brother."
Another search grouped two siblings because they shared a last name. The team kept automatic merging for leads and contacts with strong matches, and went through the company sets one by one.
Almost every overlapping field in that case pointed to "same." Only the legal name, the ID number and the person behind each record differed. That's the pattern to watch for: when the shared fields describe a place or an owner, they don't prove the records describe one customer.
Our post on [complex deduplication at scale](https://dedupe.ly/blog/complex-crm-deduplication-at-scale) covers why confidence matters more than volume in projects like this.

### How to combine fields for complex matches

#### Start from where your records overlap

Open a few sets you know are duplicates and note which fields agree. That tells you which fields to combine. Fields that agree on your known duplicates and differ on your known non-duplicates are the ones worth matching on.

#### Give each field its own strictness

Not every field in a combination needs the same comparison. Phone can ignore formatting, name can allow typos and an ID field can stay exact. A loose comparison is safer when a strict field in the same combination confirms it.

#### Add a field that tells records apart

Some fields work as a deciding field. A tax ID, a customer number or a first name set to exact can separate records that share everything else. When one of those fields differs, the records usually aren't duplicates.

#### Run several combinations side by side

One combination rarely catches every pattern. A common approach is to start with a strict combination of three or four fields for the duplicates you'd merge without looking. Then loosen one field at a time and check those results more carefully.
Pro tip
Show fields you don't match on next to each set, like owner, lifecycle stage or a legal ID. They don't change the match, but they give the reviewer the context to decide in seconds.

### Decide the close calls by hand

Complex matches carry more doubt than exact ones, so the review step matters more. A few habits keep it fast.
- **Review looser combinations before any automatic merge.** Only automate a combination once its results stop surprising you.
- **Reject a set when you're certain it isn't a duplicate.** It then stays out of later searches, so nobody decides it twice.
- **Change the search when a false pattern repeats.** If households keep matching, add a person-level field like first name instead of rejecting each set.
- **Ask the person who knows the record.** An account owner can tell you in a minute whether two companies are one customer.
Keep a list of decided patterns, like "same address, different legal ID stays separate." It saves the next reviewer from reopening the same question.

### How Dedupely helps you find complex duplicates

In Dedupely, you combine fields in a duplicate search, choose how strictly each one is matched and hold several combinations in one search. You can show extra fields next to each set for context without changing the match. Uncertain sets can go to review, and sets you're certain about can be rejected so they don't come back.
[Find the duplicates your email search misses](https://v2.app.dedupe.ly/signup)

### More fields, more care

Complex duplicates only appear when you combine fields, and the right combination depends on how your data overlaps. Strict combinations can be trusted, while looser ones need a person to look.
The same overlap can mislead in the other direction. A shared address or phone may describe a household or one owner's businesses. Keep a deciding field in the search and review the close calls yourself.

### Frequently asked questions

#### How do you find duplicates that don't share an email?

Combine fields that agree across the records, like name, phone and company. Let phone ignore formatting and name allow small typos, and keep at least one field strict. Send the results to review first, since combinations without email carry more doubt than exact email matches.

#### Can two records with the same email, phone and address be different people?

Yes. Family members often share a phone, email and home address, and one owner can run several companies from the same office. Look for a field that belongs to one person or entity, like first name or a legal ID, before you merge.

#### How many fields should match to find complex duplicates?

Often three or four. Two fields can pair strangers, while three or four that agree point to one record much more often. Start strict, check the results, then loosen one field at a time and review what the looser search adds.

#### Should complex duplicate matches be merged automatically?

Only after a person has checked enough results to trust the combination. Many teams automate a strict combination and keep looser ones in review. Sets involving households, shared offices or related companies are usually safer reviewed by hand, one at a time.

#### What field can tell two similar companies apart?

A tax or registration ID, a customer number or a legal entity name usually works. Matched exactly, it separates two companies that share an owner, an address or a phone. When that field differs, treat the records as separate unless someone who knows them says otherwise.
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 Complex CRM deduplication at scale Complex deduplication comes from thin overlapping data, mixed criteria and field rules. Automate once three or four strong fields match. Gaby Salinas October 15, 2026](https://dedupe.ly/blog/complex-crm-deduplication-at-scale)
[Duplicates Records with no email and how to find their duplicates Records with no email slip past email matching. Match them on name with company or phone, review near matches, and never let a blank overwrite a value. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/find-duplicates-without-email)
[Duplicates How to match personal and work emails in your CRM One person with a personal email, a work email and an alias becomes several contacts. Match on first and last name plus phone or company instead. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/personal-work-email-duplicates)

### 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/gaby-salinas/talk-to-sales)[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