How to Merge Accounts in Salesforce: What You Need to Know

Duplicate accounts are one of the most common data quality problems in Salesforce. When the same company exists twice under slightly different names — "Acme Corp" and "Acme Corporation," for instance — your team ends up with split history, confused relationships, and unreliable reporting. Merging accounts solves this by consolidating duplicate records into a single, clean entry.

Here's how the process works, what it affects, and what to think through before you start.

What Merging Accounts Actually Does in Salesforce

When you merge accounts in Salesforce, you're combining two or three duplicate account records into one master record. The platform lets you choose which record becomes the master and which field values carry over from each duplicate.

After the merge:

• The master account retains the field data you selected
• Related records — contacts, opportunities, cases, activities, notes, and attachments — are moved to the master
• The duplicate records are permanently deleted
• Merged record IDs are retired (the old IDs redirect to the master in most contexts)

This is a destructive action. Deleted duplicates cannot be recovered through the standard Recycle Bin once a merge is complete.

How to Merge Accounts: Step-by-Step

Salesforce offers a built-in merge tool accessible directly from the account record. Here's the general flow:

Finding Duplicates

1. Navigate to the Accounts tab
2. Open one of the duplicate account records
3. In the Details tab or sidebar, look for the Merge Accounts button (this may appear under a related list or action menu depending on your Salesforce edition and layout configuration)
4. Alternatively, use Duplicate Rules and Matching Rules — if configured, Salesforce will surface potential duplicates automatically through a "Potential Duplicates" component

If your org uses Salesforce Classic, the merge path runs through Tools > Merge Accounts from within an account record. In Lightning Experience, the flow is similar but accessed through the action menu or the Duplicates component.

Running the Merge

1. Search for and select up to three records to merge at once
2. Review the side-by-side comparison of field values
3. Select the master record — this is the record whose ID survives
4. For each field, choose which record's value to keep (you're not locked into one record's data across every field)
5. Click Merge and confirm

The process typically completes in seconds for standard account records.

What Gets Merged — and What Doesn't 🔍

Understanding what data moves and what stays behind matters more than most users expect.

One important nuance: if your org uses Account Hierarchies, merging a parent account with a child account (or vice versa) can alter your entire hierarchy structure. Review the parent-child relationships before merging any account that sits within a hierarchy chain.

Permissions Required to Merge Accounts

Not every Salesforce user can run merges. The following permissions are typically required:

• Delete permission on accounts (since the duplicates are deleted)
• Edit permission on accounts
• For some orgs, Merge Topics or admin-level access depending on customization

Standard users without delete access will either see the merge option grayed out or won't see it at all. System administrators can perform merges across all records. If your role doesn't include delete access, a Salesforce admin will need to run the merge or adjust your permissions.

Bulk Merging: When the Standard Tool Isn't Enough

The native Salesforce merge tool handles up to three records at a time. For organizations dealing with hundreds or thousands of duplicates, that's not a workable solution.

Common approaches for bulk deduplication include:

• Salesforce's Duplicate Management tools — built into the platform, these can flag and prevent duplicates through rules but don't batch-merge automatically
• Third-party AppExchange tools — apps like Dedupely, DupeCatcher, or Cloudingo are built specifically for bulk merging and offer more control over merge logic and field mapping
• Data Loader + manual prep — some admins export, clean, and re-import data, though this approach carries higher risk and requires careful field mapping
• Apex or Flow automation — custom code or declarative tools can automate merge logic for specific use cases, though this requires developer-level expertise

The right approach depends heavily on the volume of duplicates, the complexity of your data model, and your team's technical resources.

Variables That Affect Your Merge Process 🛠️

Several factors change what merging looks like in practice:

• Salesforce Edition — available features and UI differ between Essentials, Professional, Enterprise, and Unlimited editions
• Lightning vs. Classic — the interface and some steps vary between experiences
• Customizations — heavily customized orgs may have custom objects, validation rules, or triggers that behave unexpectedly during merges
• Account Hierarchy depth — deeper hierarchies require more planning before merging parent or child accounts
• Data volume — accounts with hundreds of related records may behave differently than simple records with minimal history
• Integration dependencies — if external systems reference Salesforce Account IDs, a merge can break those connections unless the external system handles ID redirects

Before You Merge: A Few Practical Checks

• Export a backup of both records before merging — Salesforce doesn't give you a clean undo
• Check whether either account is referenced by active integrations, CPQ configurations, or billing systems
• Review open opportunities and cases to confirm they'll land in the right place on the master
• Confirm which account record has the longer, more complete history — that's often a strong candidate for master

The merge process itself is straightforward. The complexity lives in what's connected to the accounts you're merging — and that picture looks different for every Salesforce org.