SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Confirm that the pair represents one real entity
HubSpot can surface potential duplicate contacts and companies, but similarity is a review signal rather than proof that two records should become one. Compare stable identifiers, authorized contact details, company domains and relationship context. Two people with similar names or two divisions sharing a domain may need separate records.
Record the primary decision before merging
HubSpot describes the record selected first as the primary record and generally prioritizes its property values, with documented exceptions. A merge creates a resulting record identity, combines activities and associations, and cannot be undone through an unmerge operation. Export or record the relevant state before proceeding.
| Control | Primary candidate | Secondary candidate |
|---|---|---|
| Business identity | Verified customer record | Duplicate import record |
| Required values | Approved owner and status | New phone requiring review |
| Relationships | Active deal and company | Recent form activity |
This is a fictional review example, not a real customer merge.
Reconcile more than the visible name
- Save the original Record IDs and URLs.
- Confirm both records represent the same entity.
- Choose the primary record and values to retain.
- Inventory important activities, associations and dependent processes.
- Perform the authorized merge.
- Verify the resulting ID, selected values, associations and recent activity.
- Search for the original IDs and document the decision.
Review downstream effects
The official documentation describes object-specific merge behavior and notes that workflow or integration effects can depend on the connected feature and subscription. Inspect the processes actually used by the account. Do not infer that combining two CRM rows also reconciles every external application.
For a controlled sample, compare a normal duplicate, a false positive and a pair with conflicting values. Reject the false positive and retain the reason. Accept the merge only when the surviving record preserves the approved meaning and the necessary relationships. This guide is an editorial checklist, not evidence that a live HubSpot merge was performed.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.