What Happens When You Merge Contacts in HubSpot (and What You Cannot Get Back)
When you merge contacts in HubSpot, the primary record's property values win, all timeline activities and associations combine onto the survivor, and the secondary record is removed from every static list. HubSpot's documentation states that merges cannot be undone, so review what survives, what changes, and what is lost before you merge.
Last updated: July 2, 2026
Every HubSpot behavior described on this page comes from HubSpot's own knowledge base, primarily the Merge records article (updated June 17, 2026), with links throughout so you can verify each claim at the source. This guide focuses on contacts and notes where companies behave differently.
Which property values survive a HubSpot contact merge?
The primary record's property values survive. HubSpot's merge documentation states that the merged record's values reflect the primary record, and a secondary value is used only where the primary has no value at all. If both records held different values for the same property, the secondary record's value is gone from the merged record's current view.
In HubSpot's own words, from the Merge records article: "in general, the primary record's property values are prioritized ... if the primary record does not have a value for a property (e.g., null, empty) the secondary record's value is used."
Contacts have documented exceptions to primary-wins:
- * Email: the primary contact's email stays primary, and the secondary contact's email is added to the survivor as a secondary email address.
- * Lifecycle stage: the stage furthest down the funnel is kept. HubSpot's example: a Lead merged with a Customer produces a Customer.
- * Form submissions: counts from both contacts are added together.
- * Marketing contact status: the most marketable status is kept.
- * Legal basis properties: the most recent values from both records are kept.
Merging companies instead? The same primary-wins rule applies, with two company-specific twists documented in the same article: the secondary company's domain is kept as a secondary domain name, and analytics properties such as page views and visits are combined from both companies. Lifecycle stage follows the same furthest-down-funnel logic as contacts.
What happens to activities, emails, and other timeline items?
Timeline activities are combined, not lost. HubSpot's documentation confirms that all timeline activities of both records included in the merge will appear on the new record. Emails, calls, notes, meetings, and tasks from both contacts end up on the surviving record, although they are now mixed together on a single timeline.
The exact wording from the Merge records article is that "all timeline activities of both records included in the merge will appear on the new record." The practical cost is attribution: once two histories share one timeline, telling which conversation belonged to which original person requires reading each activity, and nothing on the merged record labels them for you.
What happens to associations when you merge?
All associated records from both contacts combine onto the survivor. HubSpot's documentation states that all associated records of both records included in the merge will appear on the new record. Where both contacts had a company association labeled Primary, the primary company from the primary merge record is kept on the merged contact.
That Primary-label rule is easy to miss and matters for reporting and workflows keyed to a contact's primary company. Per the Merge records article: "For company associations with the Primary label, the primary company from the primary merge record is prioritized." Deals, tickets, and other associated records from both sides simply accumulate on the merged record.
What happens to list memberships and form submissions?
The secondary contact is removed from all static lists, and those memberships are not carried over to the surviving record. Form submission totals from both contacts are added together on the merged contact. This static list loss is one of the least visible casualties of a merge, so export list memberships first if they matter.
HubSpot's documentation puts it in one line: "the secondary record is removed from all static segments." Active lists re-evaluate on their own criteria, but a static list is a fixed roster, and the secondary contact's seat on that roster is simply gone.
Tracking also changes permanently. The same article explains that all cookies (HubSpot usertokens) associated with either contact are merged into the primary, and the secondary contact's email address is permanently associated with the primary contact. A later form submission from a previously used device is deduplicated by usertoken onto the primary, and a submission from a new device using the secondary's email also lands on the primary record. The two identities cannot diverge again on their own.
What do you keep, lose, and see changed after a merge?
You keep combined activities, combined associations, both email addresses, and the primary record's property values. You lose the secondary record's conflicting property values, its static list memberships, and its separate identity, since its cookies and email become permanently attached to the survivor. Lifecycle stage, form submission counts, and marketable status change under special merge rules.
| Data | Outcome | What happens |
|---|---|---|
| Primary record's property values | Kept | Prioritized on the merged record; secondary values fill only empty fields. |
| Timeline activities (both records) | Kept | All activities from both records appear on the merged record, combined into one timeline. |
| Associations (both records) | Kept | All associated records from both sides appear on the survivor. |
| Both email addresses | Kept | Primary email stays primary; the secondary's email becomes a secondary email on the survivor. |
| Lifecycle stage | Changed | The stage furthest down the funnel wins, regardless of which record was primary. |
| Form submission counts | Changed | Added together across both contacts. |
| Marketing contact status | Changed | The most marketable status of the two is kept. |
| Legal basis properties | Changed | The most recent values from both records are kept. |
| Cookies (usertokens) | Changed | All usertokens from both contacts merge into the primary; future submissions attribute to the survivor. |
| Secondary's conflicting property values | Lost | Dropped from current values wherever the primary already had a value. |
| Secondary's static list memberships | Lost | The secondary record is removed from all static segments; memberships do not transfer. |
| The secondary record itself | Lost | Ceases to exist as a separate record; its Record ID survives only inside the Merged contact IDs property. |
| Any native way to unmerge | Lost | HubSpot's documentation states it is not possible to unmerge records. |
All rows sourced from HubSpot's Merge records documentation.
Can you unmerge contacts in HubSpot?
No. HubSpot's documentation answers this directly in a section titled Can I unmerge records: It's not possible to unmerge records. The statement carries no exceptions for contacts, companies, or deals. The only documented workaround is using the resulting additional email address or domain name to create a new, empty record.
"It's not possible to unmerge records. ... For contacts and companies, you can use the resulting additional email or domain name to create a new record."
HubSpot knowledge base, Merge records, section "Can I unmerge records?"
Note what that workaround actually gives you: a brand-new record carrying the freed-up email address or domain, with none of the original properties, activities, associations, or list memberships. It recreates an identity, not the data.
The HubSpot Community has said the same thing for years. A long-standing community answer in the How to UN-Merge Contacts thread reaches the same conclusion: HubSpot has no native way to unmerge contacts once they are combined.
Does the secondary record go to the recycle bin?
HubSpot's documentation does not say. The merge article never describes the secondary record's fate, and the restore deleted records article never mentions merges at all, so there is no documented path to recover a merge loser from the recycle bin. For contacts, a restore would likely be blocked anyway by HubSpot's email conflict rule.
You can check this silence yourself: the Restore deleted records article covers deletions and the 90-day restore window without a single reference to merged records, and the Merge records article never states where the secondary record goes. Treat any claim that you can "restore the merge loser from the bin" as undocumented.
For contacts, two documented rules combine badly here. The merge makes the secondary's email an active secondary email on the survivor, and the restore tool states that "If an active contact email matches the email of the deleted contact, the contact cannot be restored." Even if a merged-away contact appeared in the restore tool, that email conflict would likely block the restore, and restore has no documented ability to reverse the property, activity, and association consolidation a merge performs.
How do you see what a record looked like before the merge?
Open the merged record, click Actions, then View all properties, and search for Merged. The Merged contact IDs property lists the Record ID of every contact previously merged into that record, and hovering the value and clicking Details shows who performed the merge and when it happened, according to HubSpot's documentation.
The property exists per object as Merged contact IDs, Merged company IDs, and Merged deal IDs. Per the Merge records article, it "will contain the Record ID values of all records previously merged into that record," which makes it the fastest way to confirm a merge happened and identify the lost record's ID.
There is also a bulk export, with real limits. From Data Management > Data Quality > Manage Duplicates, the Actions menu offers Export merge history, covering up to 90 days back and containing property values prior to the merge plus merge timestamps. The catch, documented in the same article: the option only appears for merges performed in the Data Quality tool, not for manual record-page merges. And per HubSpot's deduplication documentation, that tool compares duplicates only for contacts and companies and requires a Professional or Enterprise subscription.
So if the merge was done manually on the record page, as most accidental merges are, there is no export of what the records looked like before. Property history and the Merged IDs property become the primary forensic evidence.
Frequently asked questions
Does merging contacts in HubSpot delete the secondary contact's emails and activities?
No. HubSpot's documentation states that all timeline activities of both records included in the merge will appear on the new record. Emails, calls, notes, and tasks are combined onto the surviving contact rather than deleted. What is lost are the secondary contact's conflicting property values and its static list memberships.
Can HubSpot Support unmerge contacts for you?
HubSpot's merge documentation states that it's not possible to unmerge records, and it documents no support-based exception. The only workaround it describes is using the resulting additional email address or domain name to create a new record, which produces an empty record rather than restoring the original data.
How long do you have to export merge history in HubSpot?
Up to 90 days. HubSpot lets you export merged record details from Data Management > Data Quality > Manage Duplicates via Actions > Export merge history. The export only covers merges performed in the Data Quality tool, which handles contacts and companies and requires a Professional or Enterprise subscription.
Does a merge change the secondary contact's email address?
Yes, its role changes. The primary contact's email stays the primary email address, and the secondary contact's email is added to the surviving record as a secondary email address. HubSpot also permanently associates the secondary email with the primary contact, so later form submissions using it land on the merged record.
What are your options if the merge already happened?
You have two realistic paths. If a backup of the records existed before the merge, restore from that backup, since it is the only way to recover exact pre-merge data. If no backup existed, Emergency Unmerge reconstructs the two original records from HubSpot property history, for contacts, companies, and deals only.
Path 1: Restore from a backup, if one existed
A snapshot taken before the merge is the gold standard, because it holds the actual pre-merge data rather than a reconstruction. If you snapshotted the two records with Pre-Merge Backup (a feature of Emergency Unmerge that captures every property and association on both records before a merge), the restore is free, instant, and 100% accurate, with no reconstruction needed.
If you run automated portal backups with CRM Data Backup & Restore by Third Space, you can restore the affected contacts, companies, or deals from a snapshot taken before the merge. The free plan covers up to 2,000 records.
HubSpot also offers a native Backup & Restore tool under Settings > Data Management (Starter and above), but per its documentation those backups exclude associations and activity data, exactly the things a merge reshuffles, and HubSpot's merge documentation still states it is not possible to unmerge records.
Path 2: Reconstruct with Emergency Unmerge, if no backup existed
Emergency Unmerge rebuilds the two original records from the evidence HubSpot keeps: property history, timestamps, association patterns, and email forensics. It works on contacts, companies, and deals, on merges from minutes ago or months ago. The scan is free and shows the exact credit cost before you commit to anything; credits start at $4.99 with no subscription. See how it works and pricing.
Honest limits, stated up front: because of HubSpot API limitations, unmerging creates new records with new Record IDs rather than restoring the originals, and results are probabilistic rather than guaranteed. Simple merges with clear property history typically achieve 90%+ confidence, and you review every field with confidence scores before anything is written to your CRM. Very old merges may show No Merge Detected if the property history was overwritten.
Scope matters too: Emergency Unmerge recovers merged contacts, companies, and deals. It does not recover plain deletions, tickets, or custom objects. If your records were deleted rather than merged, use HubSpot's own restore tool within its 90-day window.
Check the damage for free
Install Emergency Unmerge and scan the merged record. The scan is free, makes no changes to your CRM, and shows the exact cost before you commit. Questions first? Contact support.
Install & Scan for FreeNo subscription · Free scan · Starting at $4.99
Merging on purpose soon? Run the pre-merge checklist first.