View as Markdown

TL;DR

  • In Lightning Experience, Salesforce merges contacts with different accounts.
  • The exception is a contact associated with a portal user.
  • The merged contact keeps one account, so choose the master with that in mind.
  • If the accounts are duplicates themselves, merge the accounts first.
  • Dedupely merges Salesforce contacts through Salesforce's own merge, with Merge Rules to choose the master.

The same person appears twice in Salesforce: once under "Acme Corp", once under "Acme Holdings". Can you merge them, and where does the merged contact end up? Salesforce allows it in most cases, but the account the contact keeps depends on choices you make before merging.

What Salesforce allows

Situation Can you merge?
Contacts under different accounts, in Lightning Experience Yes
The same, in Salesforce Classic No: contacts must share the same account
One of the contacts is associated with a portal user Not across accounts: move the contacts to one account first

Salesforce's help says you can merge contacts that have different primary accounts unless the contact is associated with a portal user, and that Classic only merges contacts with the same account. For portal contacts, its guidance is to move the contacts into one account, then merge.

Which account the contact keeps

A contact has one primary account, so the merged contact keeps one. Choose the master record, or the account value during the merge, deliberately:

  • Job change: keep the current employer.
  • Duplicate accounts: merge the accounts first, then the contacts end up under one.
  • Parent and subsidiary: keep the account the person works for.
  • Contacts related to several accounts: if your org uses Contacts to Multiple Accounts, the other relationship can stay as an indirect one.

What else changes

  • Contact roles on opportunities: the non-master contacts lose primary status on their contact roles.
  • Related records like activities and cases move to the merged contact.
  • Created By and Created Date come from the oldest record.
  • The non-master contacts go to the Recycle Bin for 15 days.

How Dedupely merges contacts across accounts

Dedupely merges Salesforce contacts through Salesforce's own merge, so Salesforce's rules apply, including the ones for portal users. The master record keeps its ID, and blank fields never overwrite existing data. Merge Rules decide which contact is the master and which value wins in each field, for example a Primary Record rule that prefers the most recently updated record. Duplicate accounts can be merged first in a separate search, and Merge History keeps every original record's values.

Merge Salesforce contacts under the right account

Decide the account first

Salesforce merges contacts across accounts in Lightning Experience, except for contacts with portal users. The merged contact keeps one account, so merge duplicate accounts first, choose the account the person belongs to, and check contact roles on open opportunities.

Frequently asked questions

Can you merge Salesforce contacts that belong to different accounts?

Yes, in Lightning Experience, unless a contact is associated with a portal user. Classic requires the same account.

Which account does the merged contact keep?

One account, from the master record or the value you choose during the merge.

What if the two accounts are duplicates?

Merge the accounts first. The contacts then end up under one account.

What happens to contact roles on opportunities?

Non-master contacts lose primary status on their contact roles, so check open opportunities after the merge.

How do I merge portal contacts under different accounts?

Move the contacts into one account first, then merge them.