# Why Salesforce won't merge contacts linked to portal users

> Contacts with portal or Experience Cloud users follow stricter merge rules in Salesforce. Which merges are blocked, what happens to the user and how to merge.

- URL: https://dedupe.ly/blog/salesforce/salesforce-merge-contacts-portal-users
- Section: blog
- Published: 2026-11-19
- 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)
[Salesforce](https://dedupe.ly/blog/salesforce)

## Why Salesforce won't merge contacts linked to portal users

By
[Gaby Salinas](https://www.linkedin.com/in/gbyslns)
Updated November 19, 2026
#
min read
TL;DR
- A contact linked to a portal user is also a login for a customer, partner or member.
- Salesforce only merges it under stricter rules, because one login has to go.
- The master contact should be the one with the portal user you want to keep.
- The other contact's portal user is deactivated, and contacts under different accounts need moving first.
- Dedupely merges Salesforce contacts through Salesforce's own merge, so these rules still apply.
Most Salesforce contacts are just records. A contact with a portal user is also someone's login: a customer to your help center, a partner to your partner portal, a member to your community. That's why Salesforce is stricter about merging them.

### The rules

| Rule | From Salesforce's help |
| --- | --- |
| The master contact | Should be associated with a portal user, if one of the contacts has one |
| The other contact's portal user | Is deactivated |
| Partner user and customer user on the duplicates | Decide which type of user to keep; the other is disabled |
| Contacts under different accounts | Move them into one account first, then merge |
After the merge, you can enable the contact for the portal it lost access to.

### Why duplicates with portal users happen

- **A person signs up for the portal** with a different email from the one sales has.
- **Several portal accounts** for one person, for example a consultant working with several of your customers.
- **A partner contact and a customer contact** for the same person, each with its own user.
Example
Say a customer's admin has a contact with a portal user for your help center, created when they filed their first ticket with a personal email. Sales has a second contact for them with their work email. The merge keeps the contact with the portal user as master, so their help center login keeps working, and sales' contact merges into it.

### How to merge them safely

- **Find duplicates where either contact has a portal user.**
- **Make the contact with the portal user the master,** or, if both have one, decide which login to keep.
- **Tell the person** if their login will change.
- **Move the contacts into one account** first if they're under different accounts.
- **Re-enable portal access** after the merge if the person needs both portals.
Pro tip
If someone legitimately needs several portal logins, for example a consultant working with several customers, consider linking the contacts instead of merging them. A merge leaves one login.

### How Dedupely handles portal contacts

Dedupely merges Salesforce contacts through Salesforce's own merge, so Salesforce's rules for portal users apply. Merge Rules decide which contact is the master. If portal access is recorded in a contact field, a Custom rule can prefer the contact that has it, and a filter can keep those contacts in a search of their own. Sets that need a decision can go to Manual Review. Merge History keeps every original record's values.
[Merge Salesforce contacts without breaking portal logins](https://v2.app.dedupe.ly/signup)

### One person, one login

Contacts with portal users are logins, not just records, so Salesforce merges them more carefully. Keep the contact with the portal user as master, decide which login stays when both have one, move contacts to one account first and tell the person if their access changes.

### Frequently asked questions

#### Why can't I merge Salesforce contacts with portal users?

Salesforce has stricter rules for them: the master should have the portal user, and contacts under different accounts need moving first.

#### What happens to the other contact's portal user?

It's deactivated. You can enable the merged contact for that portal again afterwards.

#### Which contact should be the master?

The one with the portal user you want to keep.

#### Can I merge contacts with portal users under different accounts?

Move them into one account first, then merge.

#### Should I always merge portal contacts?

Not if the person needs separate logins. Linking the contacts can be better.
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 handle related records that look like duplicates Subsidiaries, branches, shared inboxes and families can look like duplicates. Define why they aren't, then reject the match so it stops coming back. Gaby Salinas October 28, 2026](https://dedupe.ly/blog/duplicates/related-records-not-duplicates)
- [Salesforce Duplicate accounts in Salesforce and how to merge them Salesforce merges up to three accounts at a time. See how duplicate accounts form, what a merged account keeps and how to choose the principal account. Gaby Salinas October 19, 2026](https://dedupe.ly/blog/salesforce/salesforce-duplicate-accounts)
- [Duplicates Edge cases in CRM deduplication a person should decide Shared inboxes, families, subsidiaries, partners who buy and customers who come back need a person to decide. See the question that settles each case. Gaby Salinas October 22, 2026](https://dedupe.ly/blog/duplicates/crm-deduplication-edge-cases)

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