Short answer
Before merging HubSpot contacts, verify that they represent the same person and decide which values to retain. Save identifiers and review associations and integrations: a shared phone number does not establish identity, and a merge must not be treated as reversible.
Key verification: Check the resulting contact and correct the process that created the duplicates.
Sources and limitationsBefore merging contacts in HubSpot, confirm that they are the same person, choose what data to keep, and review integration references. A matching phone is not enough: it can belong to a company, family or phone system that is used by several people.
HubSpot indicates that a merge cannot be undone. Therefore, the main job is to check the identity and effects before confirming. Read the official merge documentation along with the steps that follow.
Separate candidates from confirmed duplicates
| Coincidence | What to investigate | Provisional decision |
|---|---|---|
| Same phone, different people | Shared line and associated company | Keep separate |
| Same email and compatible names | History, identity and possible name changes | Candidate for review |
| Similar name, different emails | If they are people with the same name or channels of the same person | Do not merge without evidence |
| Two records created for the same query | Origin of creation and matching activities | Review identity and associations |
The table proposes an editorial review criterion; it doesn't replicate a HubSpot algorithm. A tool that suggests duplicates offers candidates, not an authorization to consolidate them all.
Prepare a review sheet
- Current identifiers of both records.
- Name, email, telephone number and company verified.
- Activities and opportunities that belong to each one.
- Fields with incompatible values and evidence to choose from.
- Responsible for the decision and reason for the merger.
- External integrations or lists that use those identifiers.
Save the data required before the change using an authorized export or internal registry. That copy helps you review and reconstruct information, but it is not equivalent to an undo function.
Do not decide only by the oldest record or the one with the most fields. An abundant value may be outdated; A recent record may contain a confirmed email. Treats communication preferences and permissions as information that requires your own review.
Review the effect on identifiers and integrations
The documentation distinguishes regular behavior, which generates a resulting identifier, from beta behavior that preserves the parent ID. It also allows you to consult merged IDs. Don't assume which one uses your account: keep the previous ones and check the resulting one.
If an integration associates calls with a CRM ID, it updates their correspondence when necessary. A successful merge on the screen can leave an old reference in a sheet, automation, or external system. Before touching those rules, check how the integration processes a merge.
Avoid doing it during an active conversation: HubSpot warns of disconnection if merged during a call. Coordinate the review with the person assisting so as not to interrupt an ongoing process.
The manual procedure in HubSpot
- Open the record that you have chosen as the main one in CRM → Contacts.
- Under Actions, select the merge option.
- Look for the second record and check that it is exactly the approved candidate.
- Compare the displayed properties and chooses the values to keep.
- Confirm only when the review sheet is complete.
You need merge or Super Admin permission. Menus may change; Please use the linked official document as a reference for your account interface. Work through peer reviews before considering a batch operation.
Check the result, not just that a record disappears
Open the resulting contact and review identity, telephone numbers, emails, activities, companies and opportunities. Check which owner remains and whether a duplicate tracking task exists. Combined history may take time to sync; do not repeat the operation because you do not immediately see all the activities.
Then look for the references of both IDs in your work systems. Save a “previous → resulting” correspondence and the time of review. That notation helps explain why a historical report had two records and the current one had one.
Also correct the cause of duplicate creation
Fictional example: an import creates a record by email and a telephony integration creates another by number. Merge the pair once their identity is confirmed; If the creation criteria remain the same, the next contact may repeat the problem.
Review which system has the authority to create people, what fields it uses to search for an existing record, and what it does on a shared phone. If your problem is event traversal between tools, continue with the call, GA4 and CRM integration guide .
For pending queries, assign a single recovery task even if there are multiple phone events. The callback guide resolves that coordination without requiring merging uncertain identities.
Sources and limitations
Documentary review: . Content type: Documentation-based procedure.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- merge documentationknowledge.hubspot.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
HubSpotOfficial plan catalogueThese links lead to official pages without affiliate identifiers. We do not yet have an active affiliate link for these options. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.