Keep these considerations in mind when you merge duplicate lead records.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Starter, Essentials, Group, Professional, Enterprise, Performance, Unlimited, Pro Suite, and Developer Editions with Sales |
Campaigns
When duplicate leads that are members of different campaigns are merged, Salesforce retains the campaign Member Status Updated date for each campaign the merged lead is a member of.
Sharing Rules
In Professional, Enterprise, Unlimited, Performance, or Developer edition orgs, any sharing rules are applied to the merged lead. Also, any manual sharing from the principal record is applied to the merged lead.
Related Items, Chatter Feeds, and Attachments
When duplicate records are related to items such as campaigns or activities, Salesforce relates the items to the merged record, with some exceptions. Chatter feeds are retained from the principal record only. Salesforce Files attached in the Chatter feed or Files related list will be retained in the merged record.
Hidden and Read-Only Fields
Salesforce retains any data in hidden or read-only fields, such as sharing settings, from the principal record. Hidden fields aren’t shown while you merge. A merged record retains the Created By user and Created Date from the oldest record merged, regardless of which record is the principal. The record shows the merge date as the Last Modified By date.
Non-Principal Leads
The non-principal leads are moved to the Recycle Bin.
Converted Leads
In Salesforce Classic, you can’t merge a converted lead with other converted leads. You can merge a converted lead with a non-converted lead, as long as the non-converted lead is selected as the principal record. To merge converted leads, use Lightning Experience instead.