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.
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.
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.
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.




Salesforce AppExchange