TL;DR
- When duplicates disagree on an opt-out, the merged record must keep the opt-out.
- Field-by-field merges can let the "yes" from the other record win instead.
- Some opt-outs live outside the contact's fields, in email or calling tools.
- Find every opt-out field and test a sample before a large merge.
- Dedupely Merge Rules can stop an unsubscribed email winning, and Merge History keeps every original value.
Merging duplicates usually improves data. With opt-outs, it can do the opposite: a contact who unsubscribed on one record and stayed subscribed on the other can come out of the merge subscribed. Nobody decided that; a merge rule did.
Where opt-outs live
| Opt-out | Where it's usually stored |
|---|---|
| Email unsubscribe | A status field, or the email tool's own subscription records |
| Do not call | A checkbox on the contact or lead |
| Do not text | A checkbox, or the texting tool, by phone number |
| Marketing consent | A consent field with a date and source |
| Objection to processing | A field or a note from a privacy request |
Some of these follow the contact's fields in a merge. Others, like subscription records in an email tool, follow their own rules, often by email address.
How a merge can lose an opt-out
- The primary record's value wins, and the primary record hadn't opted out.
- A "newest value" rule picks the record that was updated last, not the one that opted out.
- The opted-out email isn't kept as the main email, so the email tool sees a new address.
- The do-not-call flag is on the record that's merged away.
Before a merge: protect every no
- List every opt-out field in your CRM and in connected tools.
- Find sets where the records disagree on any of them.
- Decide the rule: an opt-out on any record survives.
- Check how your CRM merges subscription statuses, since some keep the most restrictive status and some don't.
- Test on a small batch and check the opt-outs on the merged records.
- Keep a record of the original values, so you can restore an opt-out if a merge gets it wrong.
How Dedupely helps keep opt-outs
In Dedupely, Merge Rules decide which value wins in each field, and a Lose Rule can stop a bounced or unsubscribed email from becoming the main email on the merged record. Lose Rules are checked first, so the unwanted value can't win unless there's no other data. The merge preview shows the result with the winning values in bold before you merge, and Merge History keeps every original record's values, so you can check opt-out fields after a merge and restore any that changed.
The no always wins
Opt-outs have to survive a merge, whichever record they're on. List every opt-out field, find the sets that disagree, test a small batch and keep the original values, so a cleanup never puts someone back on a list they left.
Frequently asked questions
What happens to opt-outs when you merge duplicate contacts?
It depends on the CRM and your merge rules. Make sure an opt-out on either record survives.
Can a merge resubscribe someone?
Yes, if the merged record keeps the subscribed record's status or email.
How do I find duplicates that disagree on an opt-out?
Compare the opt-out fields across each duplicate set before merging, and review the ones that differ.
Are opt-outs in my email tool affected by a CRM merge?
They may follow their own rules, often by email address. Check how your tool links opt-outs to contacts.
What should I do if a merge lost an opt-out?
Restore it right away from the original values, and check other merges made with the same rules.



