Short answer: Duplicates creep into every CRM through imports, form fills, integrations and reps creating records by hand. To fix them, define matching rules (email, domain, name plus company, phone), back up your data, review likely duplicates in batches, merge with a clear "winning record" policy, and protect opt-out and ownership fields. Then stop new duplicates at the source with import checks, standardized fields and integration settings. HubSpot and Salesforce both offer native duplicate management features, and many teams add specialist tools for larger cleanups.
Why duplicates matter
Duplicates cause real problems for US and Canadian sales, recruiting and RevOps teams:
- Two reps contacting the same person
- Split activity history and inaccurate reporting
- Opt-outs recorded on one record but not the other
- Wasted enrichment credits on the same person twice
- Confusing account ownership and territory disputes
Step 1: Understand where duplicates come from
Common sources:
- List imports without matching rules
- Web forms where people use different emails
- Integrations that create records instead of updating them
- Contacts who change jobs and get re-added
- Accounts with different name formats, such as "Acme Inc." and "Acme Corporation"
- Subsidiaries and regional offices created as separate accounts
Step 2: Define matching rules
| Object | Strong match | Possible match |
|---|---|---|
| Contacts | Same email address | Same name and company, or same phone |
| Accounts | Same website domain | Similar name and same city or state |
| Leads to contacts (Salesforce) | Same email | Same name and company |
Normalize data before matching: lowercase emails, strip "www" and protocols from domains, standardize company suffixes and format phone numbers consistently.
Step 3: Back up before you merge
Merges are hard to reverse. Export the objects you plan to clean, note record counts and keep the export somewhere safe. Test your process on a small batch first.
Step 4: Use native tools
HubSpot offers duplicate management that suggests possible duplicate contacts and companies for review and merge, and it deduplicates contacts by email and companies by domain in many cases. Check which features are included in your subscription.
Salesforce offers matching rules and duplicate rules that can alert or block users when creating likely duplicates, plus merge functions for accounts, contacts and leads. Admins configure these rules.
Feature details change, so confirm current options in each vendor's documentation.
Step 5: Set a winning record policy
Decide in advance which record wins when merging:
- The record with the most recent activity
- The record owned by the current account owner
- The record with the most complete, verified data
Then decide field by field: keep the newest verified email and phone, keep the earliest create date if you use it for attribution and keep all activity history.
Step 6: Protect critical fields
Before merging, check:
- Opt-out and unsubscribe status: if either record is opted out, the merged record should be opted out
- Owner and territory: avoid surprising reps with ownership changes
- Lifecycle stage and open deals: keep the most advanced stage and all open opportunities
- Source fields: keep original source for attribution
Step 7: Review in batches
Start with strong matches such as exact email or domain, then move to weaker matches with human review. For large cleanups, specialist deduplication tools from each CRM's app marketplace can help with bulk rules and scheduling.
Step 8: Prevent new duplicates
- Run duplicate checks on every import
- Configure integrations to update existing records where possible
- Require domain on accounts and email on contacts
- Standardize company names and fields
- Train reps to search before creating
Step 9: Monitor
Track duplicate counts monthly. If they climb, find which source is creating them and fix it.
Compliance (high level)
Losing opt-out status during a merge can create compliance problems. Make sure merges preserve the most restrictive status so you continue to honor CAN-SPAM opt-outs, CASL consent records and do-not-call preferences under TCPA. Applicable privacy laws may also require you to honor deletion requests across merged records.
Common mistakes
- Merging without a backup
- Losing opt-outs or open deals in a merge
- Matching accounts on name only
- Cleaning once without fixing the sources
- Enriching duplicates and paying twice
Where PeakAI fits
PeakAI is a contact finder with a Chrome extension that finds phone numbers, work emails and personal emails from professional profiles, drawing on global sources, with bulk export and integrations. After you dedupe, use PeakAI or another tested finder to fill missing emails or phones on clean records, so you enrich each person once. Check thepeakai.com for current features, coverage and pricing.
FAQ
What is the best field to dedupe contacts on?
Email address is usually the strongest match for contacts, and website domain is usually the strongest for accounts.
Can I undo a merge in HubSpot or Salesforce?
Merges are generally hard to reverse, so always back up and test on a small batch first.
How often should I dedupe my CRM?
Run checks on every import and review duplicates on a regular schedule, such as monthly.
Do I need a third-party dedupe tool?
Not always. Native tools may be enough for small CRMs, while larger databases often benefit from specialist tools.
What happens to opt-outs when records merge?
It depends on settings, so check carefully. Your policy should keep the most restrictive status.