How do I find and merge duplicate contacts in a CRM?

The exact menu names vary by CRM, but the general workflow is:

1. Find likely duplicates. Use the CRM’s duplicate-management tool, duplicate reports, or contact search. Compare email addresses and phone numbers first, then names, company, and address. A matching name alone isn’t enough to confirm two records are the same person.
2. Review each pair before merging. Check activity history, linked companies or accounts, deals, notes, consent or unsubscribe status, and other related records.
3. Choose the record to keep. Select the record with the most reliable history and relationships as the primary or master record.
4. Choose which field values to preserve. Keep the most accurate, up-to-date details; confirm that activities and associations will carry over.
5. Merge, then verify. Open the resulting record and check its details, history, and links. Merging is often difficult or impossible to undo, so back up or export records first—especially before bulk merges. Salesforce and HubSpot both warn that merges can be irreversible. (help.salesforce.com)
6. Reduce future duplicates. Set matching rules or duplicate alerts, and encourage staff to search before creating a contact. Salesforce supports matching and duplicate rules to flag likely duplicates. (help.salesforce.com)

For example, HubSpot has a Manage Duplicates tool where you can review a suggested pair, compare properties, choose the record to keep, and merge. In Salesforce, you can use contact search or duplicate record sets, then select a master record and the field values to retain. (knowledge.hubspot.com)

If you tell me which CRM you use, I can give you the exact click-by-click steps.

Most CRMs follow the same pattern: find candidate pairs by matching fields, review them, pick a primary record, and merge. The exact steps depend on the product.

General approach

• Match on reliable fields first. One source suggests matching on email address first, then phone number, then name plus property address. Same-name matches alone produce more false positives.
• Sort the results before merging. Two records with the same email address and the same name are safe to merge. Same name plus same address deserves a look first.
• Keep the full history. Choose the record whose history you want to keep, and make sure useful details from the other record are carried over.
• Back up first. One guide advises backing up your data before performing any merging operations, and exporting the contacts beforehand is a common precaution.

Platform-specific steps

• HubSpot: Go to CRM > Contacts from your dashboard, then click Actions > Manage duplicates. To merge manually, open the contact you want to keep, then use Actions > Merge and search for the duplicate. HubSpot says all activities, notes, and associations merge into the primary record.
• Salesforce (Lightning): Open a contact and click View Duplicates. Then choose up to three contact records to merge. Click Next. Your org needs duplicate rules set up first, and you need to add the "Potential Duplicates" component to your Lightning record page to see them. Merging requires the Delete on contacts permission. Also note that Salesforce requires you to remove the duplicate relationship manually before it can merge certain contacts linked to the same account.
• Zoho CRM: Zoho has a bulk Find and Merge Duplicates option. It works on up to three chosen fields, and it only auto-merges when the records contain identical values in the selected de-duplication field(s) and no conflicts are detected.
• Ontraport: Use Contacts → Settings → Find and Merge Duplicates. In the final step, Combine All fills blank fields in the merged record, while Replace All overwrites them with the other record's values.
• OnePageCRM: You can find and merge duplicates in bulk based on First Name and Last Name or Email Address.

Things to watch for

• Merges are usually permanent. Salesforce's NPSP tool describes merging as an irreversible process, so review each pair before confirming.
• Automatic detection can flag false matches. Duplicate detection isn't perfect, and false duplicates may be identified. If that happens, select "Ignore" to hide the message. (This is from Less Annoying CRM.)
• Deleting duplicates is not the only option. Many teams prevent new duplicates with matching rules that flag or block them at entry. Salesforce's duplicate management searches for existing records upon creation and edit.

If you tell me which CRM you use (and whether you need a bulk cleanup of thousands of records or just occasional merges), I can give you more specific steps.

Finding and merging duplicate contacts is a critical step in maintaining a reliable CRM. Because every CRM platform is slightly different, the exact steps vary, but the process generally follows a consistent set of best practices to ensure you don't lose valuable data.

1. Identify How to Find Duplicates in Your CRM

Most modern CRMs have built-in tools to help you identify duplicates. Depending on your platform, you can usually find these in one of three ways:

• Dedicated Deduplication Tools: Check your CRM’s settings or "Data Management" section. Systems like HubSpot, Salesforce, Zoho CRM, and Dynamics 365 often have native "Duplicate Management" or "Deduplication" features that automatically scan for potential matches based on criteria like email, phone number, or name.
• Manual Search/Lists: You can create custom views or filters to surface records that share the same email address or phone number, which are usually the strongest indicators of a duplicate.
• Third-Party Apps: If your database is large or your CRM's native tools are limited, consider dedicated third-party solutions (e.g., Insycle, Cloudingo, or Dedupely) that offer advanced "fuzzy matching" (catching "Jon Smith" and "Jonathan Smith") and bulk-merging capabilities.

2. How to Safely Merge Records

Merging is more than just deleting rows; it is about unifying context. When you merge:

• Designate a Primary Record: You will typically be asked to choose one record to serve as the "Master" or "Primary" record.
• Preserve History: Ensure that the activities, notes, emails, and deal history from the duplicate record are moved to the primary record before the duplicate is deleted.
• Review Before You Act: If possible, preview the merge results first. If your CRM allows it, merge in small batches initially to ensure your automations and integrations (like email syncing or lead scoring) don't break.

3. Best Practices for Long-Term Maintenance

To prevent duplicates from piling up again, implement these habits:

• Stop the Bleeding: Enable "Do Not Allow Duplicates" settings on unique fields like Email or Phone Number. This prevents users from creating a new record if one already exists.
• Standardize Data Entry: Encourage your team to search the CRM before creating a new contact. Use consistent formatting for entries (e.g., always using standard company name formats).
• Create a Routine: Don't let duplicates become a "next quarter" problem. Set a simple Standard Operating Procedure (SOP)—such as having an admin check the duplicate list once a month—to keep the database clean without it becoming an overwhelming project.
• Map Integrations: Ensure that third-party tools (like web forms, ERP systems, or marketing automation software) are mapped correctly to your CRM's unique identifiers to prevent them from creating redundant records during syncs.

Warning: Before performing a large-scale merge, it is highly recommended to perform a data export (backup) of your contacts. Once records are merged, the process is often irreversible, and you want to ensure you have a fallback if data is inadvertently lost.

A safe approach is to find likely matches, verify they’re the same person, then merge deliberately. Exact menu names vary by CRM, but the workflow is usually:

1. Find possible duplicates. Search contacts by email and phone, and look for variations in names or company. If your CRM offers duplicate detection or a duplicates manager, review its suggested matches. Salesforce can show potential duplicates and supports matching rules; HubSpot’s duplicates manager lets you review suggested pairs. ⁴³

1. Verify each match before merging. Compare identifying details—such as email, phone, organization, and recent activity. Similar names alone aren’t enough; two records may belong to different people.

1. Choose the record to keep. Usually, select the record with the most accurate or complete details, the right account/company association, and useful history. Then choose which field values to retain from each record. Salesforce and HubSpot both let you select the primary record and review values during the merge. ⁴³

1. Check related information first. Review linked activities, campaign memberships, account relationships, and any CRM-specific records or permissions that matter to your team. How related data is handled can vary by CRM; Salesforce documents exceptions for some linked information. ⁹

1. Merge and confirm. Follow your CRM’s merge flow and double-check the final record before confirming. Merging may be irreversible: HubSpot says merged records can’t be reverted, and Salesforce describes the non-primary records as deleted or moved to the Recycle Bin. ³⁹

1. Reduce future duplicates. Ask your CRM admin to configure or tune duplicate-detection rules—for example, matching on email, with additional checks for phone or name—and establish who is authorized to merge records. Salesforce recommends matching rules and duplicate-management workflows. ¹¹¹³

If you tell me which CRM you use, I can give you the exact steps.