Salesforce Deduplication Guide

Supported Objects

Dedupely supports deduplication for the following Salesforce objects:

• Accounts
• Contacts
• Leads
• Custom Objects

Permissions Required

To connect to Salesforce and merge duplicates, you must have a Salesforce Administrator profile, or your user role must specifically have "Modify All Data" or explicit "Delete" and "Edit" permissions for the specific objects you intend to deduplicate.

Common Salesforce Duplicate Issues

Salesforce orgs are highly customized and act as the central hub for multiple departments. Because Admins cannot afford to break cross-functional processes or downstream reporting, they face unique, high-stakes deduplication challenges:

• API Integrations and Form Bypasses: External APIs, Web-to-Lead forms, and third-party integrations frequently bypass native Salesforce Duplicate Rules, pushing unverified duplicate records directly into the org.
• The HubSpot-Salesforce Integration: In multi-tool tech stacks, merging a record in one CRM without coordinating with the active integration sync can trigger bi-directional update loops, re-creating deleted contacts or constantly overwriting field values.
• Inherited Tech Debt and Hidden Triggers: Most Admins manage inherited orgs with years of legacy Apex triggers, Process Builders, and Flows. Blindly merging records carries the risk of executing unintended triggers or severing connections tied to external legacy IDs.
• Native 3-Record Merge Limit and Rep Bypasses: Salesforce natively limits manual merges to a maximum of 3 records at a time. Additionally, to avoid blocking sales reps from logging real prospects, native Duplicate Rules are often set to "alert" rather than "block", and reps routinely ignore those warnings.

Salesforce Native Merge Functionality

Dedupely merges using Salesforce's native API. While you can use Dedupely's Merge Rules to control which specific field values or record win during a merge, you cannot override Salesforce's core structural merge behaviors. Every merge performed will automatically adhere to the following native Salesforce rules:

• Master Record IDs and the Recycle Bin: During a merge, Salesforce retains the ID of the designated Primary (Master) Record. The secondary, non-primary records involved in the merge are safely moved to the Salesforce Recycle Bin, where they stay for 15 days before being permanently deleted.
• Reparented History and Related Lists: Blank fields on the primary record will never overwrite existing data. All child records (Opportunities, Tasks, Cases, Notes, and Custom Object related lists) attached to secondary records are automatically reparented to the winning primary record.
• System Event Executions: Native merges fire standard Salesforce system events. Any active Apex triggers or Record-Triggered Flows configured to listen for these events will execute normally during a merge.

Recommended Salesforce Deduplication Process

To dedupe without breaking integrations, active flows, or connected downstream systems:

1. Test via Sandbox or Merge Preview: For enterprise orgs with extensive custom code, Flows, or cross-system syncs, connect Dedupely to a Salesforce Sandbox first to observe downstream system impacts. For standard orgs, use Dedupely's Merge Preview to inspect field-level merge outcomes and verify winning data rules before executing live merges or enabling automation.
2. Clean up legacy data: Merge accumulated historical duplicates first to establish a clean baseline. Removing legacy data reduces the risk of old, dead records accidentally overwriting active data during future automated merges.
3. Define your match logic: Trace duplicate origins (e.g., Web-to-Lead, API integrations, HubSpot syncs). Build strict match rules for automated cleanup and isolate edge cases requiring manual review.
4. Build dedicated Duplicate Searches: Create one separate Duplicate Search in Dedupely for each specific duplicate scenario rather than combining all rules into a single broad search.
5. Protect downstream workflows with Auto Match: Use Dedupely's Auto Match feature for edge cases before fully automating. Set a match threshold for a search so you are notified to review matches, reject them, merge them, or flag them for Manual Review with team leads before committing permanent changes.
6. Automate ongoing deduplication: Once your rules are proven and verified against downstream systems, enable Auto Merge on a continuous schedule to match and merge recurring API and form duplicates automatically.

FAQs about Salesforce deduplication

• Why aren't my Salesforce Duplicate Rules catching all my duplicates? Salesforce's standard matching rules often miss fuzzy matches (like typos, nicknames, or address variations) and are completely bypassed by third-party API integrations and web-to-lead forms.
• Is there a way to bulk-merge duplicates natively in Salesforce? Natively, Salesforce requires you to manually review and merge records, and limits you to merging a maximum of 3 records at a time. Dedupely allows you to bulk merge thousands of records in one single action.
• Where do the losing records go after a merge? Salesforce natively moves the secondary (losing) records to your Salesforce Recycle Bin. They remain there for 15 days, allowing you to restore them if a mistake was made, before they are permanently deleted by Salesforce.
• Can I use Dedupely to merge records while the HubSpot-Salesforce Integration is active? Yes.
• How do merges impact the HubSpot-Salesforce Integration? Merging records in Salesforce will trigger HubSpot to merge the corresponding records on its next sync cycle. We highly recommend reviewing our dedicated guide on merging duplicates with an active HubSpot-Salesforce Integration to avoid sync loops.
• Can I control which record or field information wins during a merge? Yes. Dedupely allows you to configure custom Merge Rules to define both the Primary (master) Record criteria (such as oldest, newest, or most complete record) and field-by-field logic. You can set rules for standard or custom fields to ensure critical data is preserved.
• Can I match Accounts based on their company domain? Yes. Dedupely allows you to use the "Domain Root" match option to match website URLs by their root (ignoring www, .com, etc.). You can also use the "Ignored terms" feature in your Match Settings to automatically skip common legal suffixes like "Inc." or "LLC" when comparing Account names.
• Can I deduplicate Custom Objects? Yes, Dedupely fully supports searching and merging Custom Objects in Salesforce.

Mentioned in this article: Duplicate Searches, Merge Rules, Finding Duplicates, Merging duplicates, Auto Match, and Merging duplicates with an active HubSpot-Salesforce Integration.