Finding hidden duplicates in Salesforce with Dedupely using domain root

If your Dedupely scan shows fewer duplicates than Salesforce’s list, it means they aren’t being matched with your current search settings. Differences in names, domain extensions, or missing data can keep duplicates from showing up in a basic scan.

This guide walks through the exact steps to adjust match types, use targeted filters, and split work between bulk merges and manual review so you can find the duplicates your first scan missed.

Why duplicates hide in the first place

When Salesforce’s duplicate list shows a higher number than Dedupely, the gap usually comes from:

• Name variations: Extra words, abbreviations, or typos (e.g., “Colen Build” vs “Colen”)
• Domain differences: .com vs .net
• Missing fields: Blank domain or company name fields make matching harder
• Different detection methods: Salesforce’s list is based on its own rules; Dedupely’s results depend on the match options and filters you set

Match types: Exact vs. Domain Root

If you’re using Exact match for the Company field:

• Exact match: Both domain and extension must match exactly (company.com matches company.com, but not company.net)
• Domain root match: Ignores the extension and matches on the root domain (company.com matches company.net, company.org)

Tip: Switch to Domain Root match if duplicates share the same root domain but have different extensions, or if you suspect domain-based duplicates are being missed.

Note: Domain Root also ignores anything that comes after "www" or "http://"

Filters for finding what the algorithm misses

Name or domain variations can prevent matches from showing in a standard scan. To find them them:

• Change the Email filter from equals to contains
• Search for just part of the domain (e.g., colen) to catch both .com and .net versions
• Combine this with Domain Root match type for broader coverage without introducing irrelevant duplicates

Use this approach to focus on one company or pattern at a time for faster review.

Here's a tip to avoid merging contacts from different branches within the same company:

Use Domain Root match along other fields:

• Contacts: First Name + Last Name
• Companies: City + Zip codes

Bulk merge your duplicates

When you uncover hidden duplicates, don’t merge everything at once, start with matches that have the most complete, reliable fields - usually where both records have a filled-in domain and consistent company name.

• Merging incomplete or inconsistent records can overwrite good data with blanks.
• A careful start builds trust in the process and lets you automate safely later.

Auto merge on a schedule

Once you’ve confirmed a search matches duplicates accurately, you can set it to run automatically.

When to automate:

• The match type and filters consistently return true duplicates
• You’ve merged a batch manually and had zero bad merges

How to use it:

• Schedule the search to run ASAP or at a set frequency so new duplicates with the same pattern are handled before they pile up
• Keep at least one manual Search Pad for edge cases, for example, when names vary a lot, even if the domain root matches

Future-proof your Salesforce from duplicates

Finding hidden duplicates isn’t a one-time job. Similar variations can creep back in through imports, integrations, or manual entry.

Ongoing plan:

• Re-run your hidden-duplicate searches periodically (monthly or quarterly)
• Keep automation active for any safe searches you’ve set up
• Review manual Search Pads on a regular schedule so exceptions don’t accumulate into large batches again

If your Dedupely scan shows fewer matches than the Salesforce list, adjust your match type, refine your filters, and split merges between automated high-confidence searches and manual review. This approach finds the duplicates that hide from default scans and keeps your Salesforce data cleaner long-term.