# When one duplicate has a bounced email | Dedupely > When one duplicate has a bounced email and the other a working one, the wrong merge keeps the bad address. How to make the working email win. - URL: https://dedupe.ly/blog/duplicates/duplicate-with-bounced-email - Section: blog - Published: 2026-11-12 - 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 one duplicate has a bounced email By [Gaby Salinas](https://www.linkedin.com/in/gbyslns) Updated November 12, 2026 # min read TL;DR - Duplicates often hold two emails for one person, and one of them may bounce. - A merge that keeps the oldest record's email can keep the dead address. - Use the bounce status, not the record's age, to decide which email wins. - Keep the dead address only where it helps, like an old-emails field for history. - In Dedupely, a Lose Rule can stop an email from winning based on another field, like a bounce flag. A contact changed jobs, or mistyped their email once, and now they have two records: one with an address that bounces and one that works. When you merge them, only one email can be the main address. If the merge keeps whichever record is oldest, it will often keep the dead one, because the older record is the one from before the job change. Every email you send after that bounces, and enough bounces hurt your sender reputation for everyone else. This post covers how to make sure the working email wins, and what to do with the one that doesn't. ### Why the wrong email wins Most merges pick one record as the primary and keep its email. Common defaults pick that record by age: - **Oldest record:** often has the old address from a previous job. - **Newest record:** often has the right address, but not always. A form fill with a typo is new too. - **Last updated record:** may have been touched by an integration that didn't change the email. None of these look at whether the email works. Your email tool knows that: it records hard bounces. That's the field to use. ### Use the bounce status to decide Most CRMs and email tools store bounce information on the contact: a hard bounce flag, a bounce reason or an "email invalid" status. When one duplicate has a bounce and the other doesn't, the email from the record without a bounce should win. | Record A | Record B | Email to keep | | --- | --- | --- | | Bounced | Not bounced | B | | Not bounced | Not bounced | Follow your usual rule, often the most recently engaged | | Bounced | Bounced | Neither works; keep one and mark the contact for re-confirmation | | Not bounced, typo domain | Not bounced | The correct one; check the domain | Pro tip A soft bounce (full inbox, temporary error) isn't the same as a hard bounce. Base the rule on hard bounces only, so a temporarily full inbox doesn't lose a working address. ### Keep the old address where it helps The dead address isn't worthless. Replies to old threads, old list imports and past form fills may still reference it. If your CRM has an additional email or secondary email field, keeping the old address there means future imports with that address still find the right contact, instead of creating another duplicate. Don't keep it as the main address, and don't let it rejoin your sending lists. ### Check the opt-out status too Bounces and unsubscribes are different things. When you merge, make sure that if either record unsubscribed or opted out, the merged record stays opted out. Losing an opt-out in a merge is worse than losing a working email. ### How to make the working email win in Dedupely In Dedupely, Merge Rules let you set which value wins for each field. A Lose Rule blocks a value from winning, and its condition can look at another synced field, so a rule like "the email loses when the bounce field is not blank" keeps a bounced address from becoming the main one. Lose Rules are checked before Win Rules. Best-email options also prefer a work email over a free provider, and Append keeps every unique value in your CRM's multi-value email fields. You can preview the result before merging, so you can check the rule on a few real pairs first. [Keep the email that works](https://v2.app.dedupe.ly/signup) ### Let deliverability decide When duplicates hold two emails and one bounces, the record's age is a poor guide. Use the bounce status to pick the working address, keep the dead one only where it helps future matching and make sure opt-outs survive the merge. That keeps every merged contact reachable, and keeps bounces from coming back through the next import. ### Frequently asked questions #### Which email should I keep when one duplicate's email bounced? The one that doesn't bounce. Use the hard bounce status from your CRM or email tool, not the age of the record. #### Should I delete the bounced address? Not necessarily. Keeping it in a secondary email field helps future imports find the right contact. Just don't use it as the main address. #### What if both emails bounce? Keep one, mark the contact as needing a new email and don't send to it until it's confirmed. #### Do soft bounces count? Base the rule on hard bounces only. A soft bounce, like a full inbox, is often temporary. #### What happens to an unsubscribe when duplicates merge? Make sure it's kept. If either record opted out, the merged record should stay opted out. 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 duplicate contacts hurt email deliverability Duplicate contacts mean the same person emailed twice, bounces from old addresses and quiet inboxes, all of which can hurt deliverability. How to fix it. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/duplicates/duplicate-contacts-email-deliverability) - [Duplicates How data decay and duplicates feed each other in a CRM Data decay leaves outdated records in your CRM while new ones are created next to them. How it differs from duplicates, and which to fix first. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/duplicates/data-decay-and-duplicates) - [Duplicates Merge CRM records without losing data Field-level merge rules let you control how each value is kept or replaced during a CRM merge. More accurate merges, fewer reviews, and logic you can scale. Gaby Salinas February 12, 2026](https://dedupe.ly/blog/duplicates/merge-crm-records-without-losing-data) ### 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)