HubSpot Merged Two Different People Into One Contact? How to Separate Them

You can separate them, but first confirm what happened. HubSpot cannot natively unmerge records, and many two-people-in-one-contact cases are cookie overwrites from a shared device rather than true merges. Check the Merged contact IDs property: if a merge occurred, both people can be rebuilt from property history in about 5 minutes.

Last updated: July 2, 2026

Why did HubSpot combine two different people into one contact?

There are two common causes. First, cookie-based form tracking: HubSpot can match a submission to the browser cookie instead of the email address, so two people using one device can end up on one contact record. Second, a person on your team merged the two contacts manually or through the duplicate management tool.

The cookie behavior is documented by HubSpot itself. The visitor tracking documentation explains that cookies are unique to a browser, so if two people share a single computer, HubSpot can associate their form submissions with the same contact record. The forms documentation goes further: when the auto-create option is off and a submission arrives with an unknown email address, HubSpot recognizes and updates contacts based on the cookies in their browsers, and warns that this "may result in contacts being overwritten if the same form is submitted multiple times from the same device."

In practice this shows up with shared front-desk computers, kiosk tablets at events, a family computer, or any browser where a colleague previously submitted or tested one of your forms. The second person's submission lands on the first person's contact record, and their details overwrite the original values.

The teammate-merge cause is more mundane. Someone clicked Merge on the record, or accepted a suggestion in HubSpot's duplicate management tool, which compares contacts on properties like First Name, Last Name, and Email address. Two real people who share a name can look like duplicates and get merged in good faith.

One framing note that matters for the fix: HubSpot describes the shared-device case as contacts being overwritten, not merged. In a HubSpot community thread titled "Automatically merged contact", a long-standing community answer points at the same form setting as the cause and notes that it is not possible to unmerge those contacts natively. Whether your case is an overwrite or a real merge determines which fix applies, so check next.

How do I tell whether it was a real merge or a cookie overwrite?

Open the contact, click Actions in the left panel, then View all properties, and search for Merged. If the Merged contact IDs property contains Record ID values, a real merge happened; hover on the value and click Details to see who merged them and when. If it is empty, you are probably looking at a cookie overwrite.

This check is straight from HubSpot's merge documentation: the Merged contact IDs property contains the Record ID values of all records previously merged into that record, and the Details view shows who performed the merge and the timestamp. That tells you whether you are dealing with a genuine merge and, if so, which teammate or tool did it.

If the merge was performed inside the Data Quality duplicate management tool, you may also be able to export merge history (Data Management > Data Quality > Manage Duplicates > Actions > Export merge history) with data up to 90 days back, including property values prior to the merge. Note the documented limits: the export only covers merges performed in that tool, not manual record-page merges.

How do I stop HubSpot from mixing up form submissions in the future?

Turn on the form setting that creates a new contact for each unique email address. In the current form editor it is called Automatically create new contacts from unknown email addresses, under the Settings icon on the General tab. In the legacy editor it is Always create contact for new email address, on the Options tab.

With the option on, HubSpot's forms documentation says every submission with a unique email address creates a new contact record, and HubSpot "won't use an existing browser cookie to associate the submission with a previously tracked contact." Submissions that match an existing contact's email still update that contact as usual.

There is a documented tradeoff: enabling it automatically turns off "Pre-populate form fields for returning visitors" and "Add link to reset the form." For forms exposed to shared devices, that tradeoff is usually worth it. This setting prevents future mix-ups, but it does not repair a contact that has already been combined.

Can I just recreate the second person as a new contact?

You can, and HubSpot's documentation suggests using the resulting additional email to create a new record, but the new contact starts empty. Every activity, association, and property from both people stays combined on the surviving record, and the secondary email address remains permanently associated with the survivor, so later form submissions can still land there.

The gaps are all documented in the merge documentation. After a merge, all timeline activities of both records appear on the surviving record, all associated records of both are combined onto it, and the secondary contact was removed from all static lists. None of that history follows a manually recreated contact. You would be rebuilding notes, emails, deals, and list memberships by hand, if you can reconstruct them at all.

Email handling makes it worse. The merge keeps the secondary contact's email as an active secondary email on the survivor, and HubSpot states the secondary contact's email address is permanently associated with the primary contact: a post-merge submission from a previously used device is deduplicated by cookie onto the survivor, and even a submission from a new device using that email lands on the survivor. Expect to remove the additional email from the surviving record before recreating the second person, since HubSpot ties an active email to one contact.

And no, the recycle bin does not rescue you here. The merged-away contact has no documented presence in the restore tool, and the restore tool refuses to restore a deleted contact whose email matches an active contact's email, which after a merge it does. We wrote up the full explanation in Does restoring from the recycle bin undo a merge?

How do I separate two merged people with Emergency Unmerge?

Install Emergency Unmerge from the HubSpot Marketplace, open the merged contact, and run the free scan. It confirms the merge and quotes an exact credit cost. Reconstruction rebuilds both people from property history in 1-2 minutes, you review every field with confidence scores, then execute. The whole flow takes about 5 minutes and starts at $4.99.

Simple merges with clear property history typically achieve 90%+ confidence; complex records with overlapping data may be lower. The full step-by-step walkthrough is on the How It Works page.

Honest limitations

  • * Due to HubSpot API limitations, unmerging creates new records with new Record IDs rather than restoring the originals. Original values are preserved in the "Emergency Unmerge" property group.
  • * Results are probabilistic and not guaranteed to be 100% accurate. You review every field before anything is written.
  • * The sooner you act after a merge, the more complete the property history available for reconstruction.

Confirmed it was a real merge?

Scan the contact for free and see the exact cost before you commit.

Install & Scan for Free

No subscription · Free scan · Starting at $4.99

What if the scan shows No Merge Detected?

That usually means the record was never actually merged, which is common in shared-device cases where one contact was overwritten rather than combined with another. Emergency Unmerge recovers merges only. For an overwrite, correct the fields manually using property history, turn on the form setting above, and contact support if you are unsure what happened.

Two notes. In a cookie overwrite there is no merge event and often no second record to separate; the second person's data replaced the first person's values on one record, so the repair is editing the contact back using each property's history and creating the second person fresh. And on genuinely old merges, the scan can also show No Merge Detected if property history was overwritten since. If the situation is ambiguous, contact support and we will help you work out which case you have before you spend anything.

How do you prevent this from happening again?

Turn on the form setting above so unknown email addresses always create new contacts, snapshot records with Pre-Merge Backup before any intentional merge so you can restore for free, and keep automated backups running. CRM Data Backup & Restore by Third Space backs up HubSpot contacts, companies, and deals with one-click restore.

Pre-Merge Backup is built into Emergency Unmerge: it captures every property and association on both records before you merge, and if the merge turns out to be wrong, the restore is free, instant, and 100% accurate, with free re-snapshots anytime. For everything else, CRM Data Backup & Restore by Third Space is free up to 2,000 records.

Frequently Asked Questions

Can HubSpot unmerge two contacts natively?

No. HubSpot's documentation states that it is not possible to unmerge records. The only documented workaround is using the resulting additional email address to create a new record, which starts empty. Emergency Unmerge rebuilds both original records from property history instead, so the second person gets their data back rather than a blank contact.

How much does it cost to separate two merged contacts?

Credits start at $4.99 for 100, with no subscription and no expiration. A simple contact unmerge typically costs 10-30 credits, which is $0.50 to $1.50. Complex contacts with many associations can run 50-200 credits. The scan is free and shows the exact credit cost before you commit to anything.

Will the separated contacts keep their original Record IDs?

No. Due to HubSpot API limitations, unmerging creates new records with new Record IDs rather than restoring the originals. The original Create Date, original Record ID, and other read-only values are preserved in a dedicated Emergency Unmerge property group on the new records, and results are reviewed field by field before execution.

Why do two different people keep landing on the same HubSpot contact?

Tracking cookies are per browser, not per person. HubSpot documents that two people sharing one computer can have their form submissions associated with the same contact record. Turning on the form option Automatically create new contacts from unknown email addresses stops HubSpot from using an existing cookie to attach submissions to the wrong contact.

Does Emergency Unmerge work if the merge happened months ago?

Usually, yes. It works on merges from minutes ago or months ago, on contacts, companies, and deals. Very old merges can show No Merge Detected if the property history HubSpot keeps was overwritten, so the sooner you scan after a merge, the more complete the data available for reconstruction.

Related reading