Salesforce duplicate management and where native tools stop

Salesforce finds duplicates with matching rules and acts on them with duplicate rules, which alert or block users but never merge. Merging is a separate, manual step: you combine up to three records at a time and choose which one survives. Duplicate Jobs, which scan the whole org for existing duplicates, are listed only for Performance and Unlimited Editions. Even there, you merge the results one set at a time. In this post, you'll see what each edition does, how a merge works, where native tools stop and how teams handle the rest.

What Salesforce does on every edition

Salesforce Help lists duplicate management for Essentials, Professional, Enterprise, Performance, Unlimited and Developer Editions. It has two parts that work together.

Matching rules define what counts as a duplicate: which fields to compare, and how. Duplicate rules decide what happens when a user saves a record that matches:

• Alert: the user is warned that the record may be a duplicate.
• Block: the user can't save the record.
• Report: the match is logged in a duplicate record set, which you can review later.

Duplicate rules don't merge anything. Each object can have up to five active duplicate rules, and each duplicate rule can use up to three matching rules. An object can also have up to five active matching rules.

What the standard matching rules compare

Salesforce includes standard rules for business accounts, person accounts, contacts and leads. You can also set up rules across objects, for example contacts that duplicate leads.

• Accounts: Account Name, with exact, acronym or fuzzy matching, combined with phone, billing street, ZIP code, city and state, or website.
• Contacts and leads: first and last name, combined with title and account (or company), email, phone or street address.

In the standard contact and lead rule, email, phone and ZIP code match only when they're exact.

When duplicate rules run, and when they don't

Imports and the API are covered, but differently. For records from data import tools or the APIs, Salesforce overrides the rule settings. No alert is shown, and the record can't be saved.

So a matching record from an import or an integration is blocked rather than let through. That matters for anyone who runs integrations: plan for what each tool does when Salesforce rejects a save.

Duplicate rules don't run at all in a few cases:

• Records created with Quick Create or Community Self-Registration.
• Leads converted to accounts or contacts when Use Apex Lead Convert isn't enabled.
• Records restored with Undelete.
• Records added through Lightning Sync or Einstein Activity Capture.
• Records merged by hand.

What each Salesforce edition includes for duplicates

Salesforce Help still describes availability with the legacy edition names, so the table uses them. In September 2026, Salesforce announced Core, Advanced and Max editions, which it compares to legacy Enterprise, legacy Unlimited and Agentforce 1.

As of October 2026, from Salesforce Help: Managing duplicates, Duplicate rules, Merge contacts, Merge leads, Account merge considerations, Duplicate jobs; and the merge API reference.

As of October 2026, Salesforce lists Starter Suite from $25 and Pro Suite from $100 per user per month. The new Core, Advanced and Max editions are $195, $395 and $550 per user per month, billed annually. Salesforce hasn't said which of the new editions include Duplicate Jobs, so confirm with Salesforce before you budget. Prices change often, so check Salesforce's pricing pages first.

How a Salesforce merge works

Salesforce merges records of the same type, up to three at a time, including the record that survives. Accounts (business or person), contacts and leads can be merged, and support reps can merge cases. These rules apply whatever your edition:

• You choose the principal record, then pick which field values to keep from the others.
• Related records move to the surviving record. For accounts, Salesforce Help says they're re-linked "with some exceptions".
• For accounts, Created By and Created Date come from the oldest record. Hidden and read-only fields, such as sharing, come from the principal.
• The Chatter feed is kept from the principal record only.
• The other records go to the Recycle Bin, where they stay for 15 days.
• Merging needs Delete permission on the object. Some account merges also need Modify All Data or Manage External Users.

Person accounts and business accounts

You can't merge a person account with a business account, in either direction. Person accounts enabled for portal or Experience Cloud users can't be merged at all.

Leads and contacts

Because Salesforce only merges records of the same type, a lead can't be merged into a contact. When a lead and a contact are the same person, the native route is converting the lead.

Duplicate rules don't run on that conversion unless Use Apex Lead Convert is enabled. Check for a matching contact and account before you convert.

In Classic, two converted leads can't be merged; Lightning Experience can.

Cases

Support reps can merge up to three cases into one, and child records go to the master case. Depending on an admin setting, the other cases go to the Recycle Bin or stay with "Merged" added to the subject.

Undoing a merge

I haven't found a Salesforce page that documents undoing a merge. You can restore a merged-away record from the Recycle Bin within 15 days. Salesforce Help doesn't say that re-parented related records move back with it.

Where native tools stop, even on Performance and Unlimited

The top editions add Duplicate Jobs. The other limits apply on every edition:

• Matching: each object gets up to five active matching rules, built from a fixed set of match methods. Most Salesforce orgs I see need more specific matching than that.
• Three records per merge: a company with five account records takes at least two merges. Through the API, anything above three records means running merges one after another.
• Jobs find, they don't merge: Duplicate Jobs group matches into duplicate record sets. Each set is compared and merged on its own, up to three records.
• Objects: Duplicate Jobs cover business and person accounts, contacts and leads. The merge API supports leads, contacts, accounts and individuals, so opportunities and custom object records aren't among the merge types.
• No merge in Data 360: identity resolution builds unified profiles from match rules, but it doesn't change the source records. It doesn't merge or delete records in your CRM.

Matching is the limit I hear about most. Many orgs hold branches and regional offices that share a name or a domain. Telling them apart takes rules written for that org.

For a few hundred simple duplicates, the native tools are often enough. The limits show once the backlog reaches thousands of records.

How teams handle what native tools leave behind

Most Salesforce cleanups I've worked on come down to the same few decisions, on any edition.

Start with Accounts and Contacts

Most Salesforce teams I talk to come to clean Accounts and Contacts first. Opportunities, cases and activities hang off those records, so their duplicates spread into reports and ownership.

Write down what makes a duplicate in your org

Before matching anything, agree on what a duplicate is for each object. Two accounts with the same name in different countries may be separate customers. Two contacts with the same email are almost always one person.

Leave placeholder values out of your matches, such as a shared office phone or an email like test@test.com. Merge the matches you're most certain of first, and review the near matches before merging them.

Decide which record survives and which value wins

The principal record decides more than its visible fields. Its sharing settings, read-only fields and Chatter feed are the ones that stay.

For key fields, such as account owner, record type and address, agree on whether the newest, the most complete or the oldest value wins.

Keep the original values

The Recycle Bin gives you 15 days, and there's no documented unmerge. Export the records you plan to merge, with their Salesforce IDs and owners, before you start.

Map what creates records

List every import, integration and form that writes to Salesforce, and check which paths skip your rules. For imports and integrations, find out what each one does when a matching record is blocked. Then set a regular rhythm for merging the duplicates that still get in.

Check your edition before you plan the cleanup

Every Salesforce edition with duplicate management can flag duplicates as records are saved and merge them up to three at a time. Whether you can also scan the whole org for existing duplicates depends on your edition, so that's the first thing to confirm.

The groundwork is the same on every edition. It starts with a shared definition of a duplicate for each object and an agreed choice of which record and values survive. An export of the originals completes it, since the Recycle Bin keeps merged records for only 15 days.

Frequently asked questions