# When a customer changes its email format | Dedupely

> A customer switches from anna.smith@ to asmith@, and its contacts come back as new records. How to find these pairs when only the email changed.

- URL: https://dedupe.ly/blog/duplicates/customer-changes-email-format-duplicates
- Section: blog
- Published: 2026-11-17
- 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)
[Duplicates](https://dedupe.ly/blog/duplicates)

## When a customer changes its email format

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated November 17, 2026
#
min read
TL;DR
- Some companies change their email format, like anna.smith@ to asmith@, after a merger or a new email system.
- Every contact at that company can then arrive as a new record with a new email.
- An email match misses these pairs, because the part before the @ changed.
- Match on name plus the email's domain instead, and keep the new address as the main email.
- In Dedupely, Domain Root matches the domain of an email, so name plus email domain finds these pairs.
A customer moves to a new email system, and its addresses change from first.last@company.com to flast@company.com. The domain is the same; every address is different. Over the next few months, as these people fill in forms, reply to sequences and join calls, the CRM creates a new contact for each of them.
Now every contact at that customer exists twice. This post covers how to find these pairs and what to keep.

### Why an email match misses them

An email match compares the whole address. "anna.smith@acme.com" and "asmith@acme.com" are different strings, so they don't match. The same goes for:
| Old format | New format |
| --- | --- |
| anna.smith@acme.com | asmith@acme.com |
| anna.smith@acme.com | anna@acme.com |
| asmith@acme.com | anna.smith@acme.com |
| anna.smith@acme.co.uk | anna.smith@acme.com |
The last one is a domain change, not a format change. It needs a different approach: matching on the root of the domain.

### Match on name plus the email domain

The person's name and the company's domain didn't change. Together, they're a strong match:
- **First and last name,** with tolerance for nicknames if your tool supports it.
- **The domain of the email,** not the whole address.
- **Optionally, the company** the contact is linked to.
Review a sample before merging. Two people with the same name can work at the same company, especially at large customers.
Example
Say a customer of 200 people moves from first.last@ to flast@ addresses. Over a quarter, 80 of them get a second contact record. A search matching first name, last name and the email's domain finds the 80 pairs. Two sets turn out to be different people with the same name, and the team rejects them before merging the rest.

### What to keep when you merge

| Field | Keep |
| --- | --- |
| Main email | The new address, since the old one may stop working |
| Old email | In a secondary email field, if your CRM has one |
| Activities and history | Both, on the merged record |
| Owner and lifecycle stage | From the record your team has worked on |
If the old addresses still work for now, they may stop later. Keeping the new one as the main email avoids a wave of bounces.
Pro tip
When a customer tells you about an email change, ask whether the old addresses will keep working and for how long. If they'll stop, update the main email on each contact before your next campaign, then merge the duplicates.

### When it's not a duplicate

The same name at the same domain usually means the same person, but not always:
- **Common names** at large companies can be two people.
- **Shared inboxes** like info@ aren't a person.
- **Family businesses** may have several people with the same last name.
Check the job title and phone before merging those.

### How Dedupely helps

In Dedupely, the Domain Root match option compares the core domain of an email or URL, ignoring www and country variants, so you can pair contacts on first name, last name and email domain even when the part before the @ changed. The "Match nicknames" setting on first-name fields pairs names like Robert and Bob. Dedupely Intelligence also compares email with a second email field automatically. Merge Rules decide which email stays the main one, and Custom Merge lets you pick it by hand for a single set.
[Find contacts with a new email format](https://v2.app.dedupe.ly/signup)

### Same person, same domain, new address

When a customer changes its email format, match contacts on name plus the email's domain instead of the full address. Review a sample for common names, keep the new address as the main email and the old one as a secondary.

### Frequently asked questions

#### How do I find duplicates when a company changes its email format?

Match on first name, last name and the domain of the email, then review a sample before merging.

#### Why doesn't an email match find these duplicates?

It compares the whole address, and the part before the @ changed, so the two emails don't match.

#### Which email should the merged contact keep?

The new address as the main email, and the old one in a secondary email field.

#### What if the company also changed its country domain?

Match on the root of the domain, so .co.uk and .com versions of the same domain pair up.

#### Can two people at one company have the same name?

Yes, at larger companies. Check job title and phone before merging those sets.
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 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/duplicates/personal-work-email-duplicates)
- [CRM Organization When a contact changes jobs, is it a duplicate? When a contact changes jobs, merging the old and new records keeps the context. Account-based and person-based teams differ in which values win. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/crm-organization/contact-job-change-duplicates)
- [Duplicates Which fields to match on to find CRM duplicates Start with exact matches on email for contacts and domain for companies, then combine fields like name and company. Choose fields per object and source. Gaby Salinas October 30, 2026](https://dedupe.ly/blog/duplicates/which-fields-to-match-on-crm-duplicates)

### 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)
