Salesforce Merge Contacts | Accounts | SalesforceTutorial

Salesforce merge contacts combines duplicate Contact records into one surviving record in Lightning Experience. You select up to three contacts, choose the principal record, decide which visible field values to retain, and confirm the merge. Use the same controlled process for duplicate Account records, but review permissions, automation, related records, and rollback options before changing production data.

What must be configured before Salesforce merge contacts works?

The merge interface depends on duplicate detection and record-page configuration. A matching rule defines how Salesforce compares records. A duplicate rule decides whether Salesforce blocks, allows, or reports a possible duplicate during create or edit operations. The Potential Duplicates component then exposes matching records on a Lightning record page.

Salesforce documents the relationship between matching rules and duplicate rules in the Duplicate Management Trailhead unit. For a broader data-quality setup, see the SalesforceTutorial guide to Salesforce duplicate management.

How to add the Potential Duplicates component

1. Open a Contact record in Lightning Experience.
2. Select Setup > Edit Page to open Lightning App Builder.
3. Drag Potential Duplicates onto the record page.
4. Save the page and activate it for the required app, record type, and profile assignments.
5. Repeat the process for the Account record page when users also need account merging.

How does Salesforce merge contacts in Lightning?

The standard Lightning flow starts from an existing Contact record. Salesforce Help states that users can choose up to three Contact records in one merge operation. One becomes the principal Contact; the others are removed after their data and relationships are processed.

How to merge contacts Salesforce step by step

1. Open the Contact that should be reviewed.
2. In the duplicate alert or Potential Duplicates component, select View Duplicates.
3. Select the Contact records to compare. Keep the total at three or fewer.
4. Select Next.
5. Choose the principal Contact. This record keeps its Salesforce record ID.
6. For each field shown in the comparison table, select the value that should survive.
7. Review the selected values and confirm the merge.
8. Open the surviving Contact and validate Account, email, phone, owner, campaign membership, activities, and custom relationships.

What survives a Contact merge?

The principal record keeps its ID. Values chosen in the wizard update that record. Fields that are not available for selection require extra care: Salesforce retains hidden or read-only values according to the principal-record behavior documented for the merge process. Layout assignment can also affect which fields appear in comparison screens.

Before merging, inspect these areas:

• AccountId: confirm which Account should remain on the surviving Contact.
• OwnerId: make sure ownership supports the intended sharing and queue process.
• Email and phone: check normalized values, not only formatting differences.
• External IDs: do not discard an identifier used by middleware, ERP, marketing, or billing systems.
• Consent fields: confirm the surviving values satisfy your privacy and communication rules.
• Custom lookups: test whether related custom records are reparented, blocked, or left unchanged.

Can contacts from different Accounts be merged?

Yes. The Lightning Contact merge process can compare contacts associated with different Accounts. This helps when the same person was created under an old employer, subsidiary, or duplicate customer account. The selected Account value on the principal Contact determines the direct account association after the merge.

Contacts to Multiple Accounts adds another edge case. Salesforce documents that duplicate indirect Account-Contact relationships can block a merge. Remove or correct the conflicting AccountContactRelation records, then retry. Review Salesforce considerations for Contacts to Multiple Accounts before cleaning up relationship records.

How do you merge Accounts in Salesforce Lightning?

The Account merge flow resembles the Contact process: open an Account, view possible duplicates, select up to three records, choose a principal Account, select retained values, and confirm. Related Contacts and other supported child records are processed according to Salesforce merge behavior and your org configuration.

Merge accounts in Salesforce Lightning

1. Open the Account that should be the starting point.
2. Select View Duplicates from the duplicate alert.
3. Select up to three Account records.
4. Choose the principal Account.
5. Select the field values to keep.
6. Review related records and confirm the merge.
7. Validate account hierarchy, ownership, Contacts, Opportunities, Cases, activities, sharing, and integration identifiers.

Merge Salesforce accounts: business and person account rules

Salesforce allows business accounts to merge with business accounts and Person Accounts to merge with Person Accounts. A business Account cannot be merged with a Person Account. For Person Accounts, test Contact-related automation as well because a Person Account combines Account and Contact behavior.

The official procedure is documented in Merge Duplicate Accounts in Lightning Experience. Teams that are redesigning account access should also review the SalesforceTutorial explanation of Salesforce sharing rules.

Account merge checks for enterprise orgs

How does merge duplicates Salesforce logic find records?

To merge duplicates Salesforce must first identify or receive a group of records. Native duplicate management uses matching rules for comparison and duplicate rules for action. Standard rules cover common Account, Contact, Lead, and Person Account scenarios, while custom rules let admins choose fields and matching methods supported by the platform.

Matching rule versus duplicate rule

A rule that blocks record creation can prevent new duplicates but does not clean existing data. For an existing org, use reporting, duplicate record sets, controlled jobs where licensed and available, or a reviewed data-migration process. See Manage Duplicates Using Duplicate Record Sets.

How can Apex merge Contacts or Accounts?

Apex supports merge DML for Accounts, Contacts, and Leads. The operation can combine a principal record with one or two duplicate records. Use Apex only when the business rule is deterministic and the process includes logging, permissions, duplicate validation, and tests. An automated merge based only on a fuzzy name match can destroy valid records.

public with sharing class ContactMergeService {
    public class MergeRequest {
        @AuraEnabled public Id masterContactId { get; set; }
        @AuraEnabled public Id duplicateContactId { get; set; }
    }

    @AuraEnabled
    public static Id mergeContacts(MergeRequest request) {
        if (request == null ||
            request.masterContactId == null ||
            request.duplicateContactId == null ||
            request.masterContactId == request.duplicateContactId) {
            throw new AuraHandledException('Provide two different Contact IDs.');
        }

        if (!Schema.sObjectType.Contact.isUpdateable() ||
            !Schema.sObjectType.Contact.isDeletable()) {
            throw new AuraHandledException('You do not have permission to merge Contacts.');
        }

        List<Contact> contacts = [
            SELECT Id, FirstName, LastName, Email, AccountId, OwnerId
            FROM Contact
            WHERE Id IN :new Set<Id>{
                request.masterContactId,
                request.duplicateContactId
            }
            WITH USER_MODE
        ];

        if (contacts.size() != 2) {
            throw new AuraHandledException('Both Contact records must be accessible.');
        }

        Map<Id, Contact> contactsById = new Map<Id, Contact>(contacts);
        Contact masterContact = contactsById.get(request.masterContactId);
        Contact duplicateContact = contactsById.get(request.duplicateContactId);

        Database.MergeResult result =
            Database.merge(masterContact, duplicateContact, false);

        if (!result.isSuccess()) {
            Database.Error firstError = result.getErrors()[0];
            throw new AuraHandledException(firstError.getMessage());
        }

        return result.getId();
    }
}

Governor-limit note: do not call this method once per row from a loop. A merge is DML and participates in transaction limits. For a cleanup queue, group reviewed work into bounded asynchronous transactions and persist success or failure for each pair.

Security note: with sharing enforces record sharing, not object permissions or field-level security by itself. The example checks update and delete access and uses WITH USER_MODE for the query. Add field-specific checks when your code writes values before the merge. See the SalesforceTutorial guide to Apex CRUD and field-level security.

What trigger events run during a merge?

Salesforce does not fire a separate “merge trigger.” The principal record is updated and losing records are deleted, so object triggers run through update and delete contexts. Salesforce documents merge trigger behavior in the Apex Developer Guide. Build handlers that are bulk-safe and do not assume every delete is a user-initiated standalone deletion.

trigger ContactTrigger on Contact (
    before update,
    after update,
    before delete,
    after delete
) {
    if (Trigger.isAfter && Trigger.isUpdate) {
        ContactAutomation.handleAfterUpdate(Trigger.new, Trigger.oldMap);
    }

    if (Trigger.isBefore && Trigger.isDelete) {
        ContactAutomation.handleBeforeDelete(Trigger.old);
    }
}

Test classes must cover the merge path and all side effects. Salesforce requires at least 75% Apex code coverage for deployment, but merge tests should assert record survival, deleted duplicate IDs, field values, and related-record behavior rather than targeting coverage alone.

What should you verify before and after a merge?

Pre-merge checklist

• Export the candidate records and key related objects.
• Confirm that the records represent the same person or organization.
• Identify the principal record by business ownership, external ID, and integration history.
• Review duplicate Account-Contact relationships.
• Pause or account for automation that sends email, creates tasks, or publishes platform events.
• Test with the same permission set used by production users.

Post-merge checklist

• Confirm the surviving record ID and selected field values.
• Validate child records, campaign members, activities, files, and custom junction objects.
• Check integration logs for references to losing record IDs.
• Re-run duplicate reports to confirm the group is resolved.
• Document the merge in a cleanup log with approver, date, principal ID, and losing IDs.

Common Salesforce contact and account merge errors

Can you undo a merge?

A merge is not a single-click reversible transaction in the user interface. Losing Contact records are placed in the Recycle Bin, but restoring them does not guarantee that every field, relationship, sharing entry, or external-system reference returns to its prior state. Treat recovery as a controlled data-repair task. Salesforce provides a specific support article on recovering merged Salesforce Contacts.

Best practices for merging duplicate Salesforce records

1. Prevent before cleaning: tune duplicate and matching rules around stable identifiers such as normalized email, phone, domain, or an external customer key.
2. Separate detection from approval: let automation identify candidates, but require a user or steward to approve ambiguous merges.
3. Protect integration keys: select the record recognized by external systems as principal or update those systems in the same change window.
4. Test automation: include Flow, Apex, assignment, territory, sharing, and integration behavior in sandbox validation.
5. Use small batches: merge reviewed groups and audit results instead of running an unbounded cleanup.
6. Measure recurrence: report on new duplicate record sets to identify the source process that continues creating duplicates.

Frequently Asked Questions

Official Salesforce references

• Merge Duplicate Contacts in Lightning Experience
• Merge Duplicate Accounts in Lightning Experience
• Duplicate Management Trailhead module
• Database.MergeResult Apex Reference