Two people can share a name, a phone line, or a role inbox. One person can also have two email addresses. A CRM’s duplicate suggestion is therefore a lead for investigation, not permission to merge. A bad merge can distort sales history, active tasks, communication permissions, and reporting.
Short answer
Separate detection, identity review, and merge. Use strong identifiers and source context to form a hypothesis. Check conflicting fields, consent, associations, and live workflows before choosing a survivor. If identity or downstream behavior is uncertain, leave the records separate and assign a reviewer.
HubSpot documents automatic deduplication by contact email in particular creation flows and a manager for potential pairs. Microsoft documents match-code rules and notes that simultaneous creation can still produce duplicates. Neither product’s rule is a universal identity test.
A merge decision matrix
| Signal | Tentative state | Human check |
|---|---|---|
| Same trusted external ID and confirmed person | Strong candidate | ID provenance, history, permissions |
| Same individual email, no identity conflict | Review candidate | Verification, owner, active workflows |
| Same shared business or household number | Do not auto-merge | Actual users and context |
| Same name and company, different emails | Investigate only | Role, office, name changes, namesakes |
| Role inbox such as info@ | Shared mailbox, not a person key | Multiple people and purposes |
| Conflicting opt-out or consent state | Stop | Provenance and current restriction |
This is a Pulse editorial model, not a legal basis for processing personal data or a vendor-specific matching rule.
Inventory what the merge may change
Compare record IDs, creation source, owner, company association, deals, tickets, tasks, email sequences, communication preferences, and update timestamps. Do not copy unnecessary personal details into an unmanaged sheet. Preserve an authorized snapshot of material fields and associations, with restricted access and an appropriate retention period, before an irreversible operation in the chosen CRM.
A simple “newest wins” rule can replace a reliable value with a later but weaker one. HubSpot documents winner criteria and warns that certain bulk merges cannot be undone. Verify the behavior available to your subscription and integrations before any batch action.
A five-state review queue
potential duplicate
→ identity confirmed?
no → keep separate and record why
uncertain → assign human reviewer
yes → inspect consent, history, tasks, and workflows
→ conflict or downstream effect unknown?
yes → pause; do not merge
no → approve surviving record and field choices
→ merge in the authorized CRM; verify resulting associations
Record the decision owner, old and new IDs, fields chosen, reason, and date. Approval must include workflow review: one contact may be in a sales sequence while the other is opted out or has an open service ticket. A merge must not trigger another message or turn an unknown preference into permission.
Test before any bulk cleanup
Use fictional records: two namesakes, one changed phone number, a shared inbox, conflicting consent states, an open deal on only one record, and simultaneous form submissions. Fail the dry run if namesakes merge, a ticket disappears, a message resends, or an unknown preference becomes opt-in.
Prevent new duplicates at intake. Look up existing IDs before importing, use unique properties where supported, and route conflicts for review. HubSpot explains that rows without a Record ID can create new records on import; a pre-import check reduces risk but cannot guarantee perfect detection.
For the earlier system choice, see spreadsheet versus CRM. For new enquiries, the lead qualification flow shows where duplicate review belongs before routing; it is not a lead score.
Limits and sources
This guide has not been run on a real CRM and does not recommend automatic merging or provide legal advice on consent. Feature availability and merge behavior vary by platform and plan. See HubSpot’s duplicate review and Record ID import guidance, plus Microsoft’s duplicate detection limitations. The matrix, queue, and fictional test cases are original Pulse decision aids that need validation in the team’s system.