Duplicate Management
Duplicate Management is the suite of Salesforce features designed to detect and manage duplicate records, including Matching Rules that identify duplicates, Duplicate Rules that define actions (block or alert), and Merge features.
Definition
Duplicate Management is the suite of Salesforce features designed to detect and manage duplicate records, including Matching Rules that identify duplicates, Duplicate Rules that define actions (block or alert), and Merge features. It helps maintain data quality by preventing or consolidating duplicate entries.
In plain English
“Duplicate Management is the set of Salesforce features that prevent and clean up duplicate records. Matching Rules find potential duplicates, Duplicate Rules decide what to do about them (block, warn, or alert), and Merge tools help consolidate duplicates that already exist.”
Worked example
Greenforge Capital's data steward configures Duplicate Management to enforce data quality on Account and Contact records. Matching Rules identify potential duplicates based on fuzzy name + address matching; Duplicate Rules define the action (Block on Contact, Allow with Warning on Account); the platform's Merge feature consolidates existing duplicates the team finds. Without Duplicate Management, the same data hygiene happens manually via periodic reports - slow and reactive. With it, duplicates are caught at creation time and the team can focus on cleanup of historical drift.
Why Duplicate Management matters
Duplicate Management is the suite of Salesforce features designed to detect and manage duplicate records in your org. The main components are Matching Rules (which define what constitutes a duplicate based on field similarity), Duplicate Rules (which define what action to take when a Matching Rule finds a potential duplicate, such as blocking creation, alerting the user, or allowing with a warning), and Merge tools (for consolidating existing duplicates that have already crept in).
Duplicate Management is essential for data quality because duplicates accumulate naturally as users enter data, integrations create records, and lead-to-account matching imperfectly succeeds. Without active management, duplicates undermine reporting accuracy, frustrate users, and create disconnected views of customers across teams. Mature orgs combine Duplicate Management with regular data hygiene routines and integration design that respects existing records, treating duplicate prevention as ongoing operational work rather than a one-time setup.
How to set up Duplicate Management
Duplicate Management is the umbrella feature combining Matching Rules + Duplicate Rules + the Merge UI — together they detect, prevent, and consolidate duplicate records. Each piece configured separately (see matching-rules / duplicate-rule); this page covers the holistic approach to duplicate handling.
- Build Matching Rules first
Setup → Matching Rules → New. Define what counts as a match (exact email, fuzzy name + company). Activate before referencing from Duplicate Rules. See matching-rules.
- Build Duplicate Rules referencing Matching Rules
Setup → Duplicate Rules → New. Configure the policy (Block / Allow with Alert) and which Matching Rule to use. Activate. See duplicate-rule.
- Configure DuplicateRecordSet for ongoing reporting
DuplicateRecordSet is the standard object that tracks detected dupes. Build reports on it to find duplicate clusters that escaped Block-action rules.
- Use the Merge UI to consolidate detected duplicates
On a record's Duplicates related list (or via the View Duplicates button), users see potential matches and can Merge — pick winning values per field, save the consolidated record.
- For bulk dedupe: use Data Loader or third-party tools
Manual one-by-one merge doesn't scale. For large dedupe projects, use Cloudingo, RingLead, or custom Apex with the merge() DML call.
- Monitor data quality via reports
Build reports on DuplicateRecordSet over time. Decreasing dupes = winning. Increasing = rules need tuning.
Define what's a match.
Define policy on match.
Standard object for tracking detected dupes.
Per-record consolidation.
Cloudingo / RingLead / custom Apex.
- Duplicate Management's effectiveness depends on Matching Rule quality. Loose rules produce too many false positives; tight rules miss real dupes. Tune in a sandbox with sample data.
- Block-action Duplicate Rules block API saves too. Integrations creating records hit the rule and fail — confirm impact on inbound data flows before activating Block rules.
- Merging records is irreversible. Once merged, the loser record is gone (data may live in the winner depending on field choice). Salesforce keeps a 15-day Recycle Bin for deletes but not for merges.
How organizations use Duplicate Management
Configured strict Duplicate Rules to block duplicate Account creation entirely. Sales reps see a warning and can either select the existing Account or contact admins for an exception.
Uses Duplicate Management with alert-only mode in some scenarios where blocking would frustrate users, while logging the alerts for periodic data hygiene runs.
Combines Duplicate Management with Lead-to-Account matching during conversion, ensuring converted leads don't create duplicate Accounts when matching ones already exist.
Trust & references
Straight from the source - Salesforce's reference material on Duplicate Management.
- Things to Know About Duplicate RulesSalesforce Help
- Things to Know About Matching RulesSalesforce Help
Test your knowledge
Q1. What does Duplicate Management include?
Q2. What actions can a Duplicate Rule take?
Q3. Why does duplicate management need to be ongoing?
Discussion
Loading discussion…