Merged the Wrong HubSpot Tickets? Here Are Your Real Options (2026)
You cannot unmerge HubSpot tickets. HubSpot's documentation is blunt: "It's not possible to unmerge records." That applies to every object, tickets included. Emergency Unmerge reconstructs merged contacts, companies, and deals only, so for tickets the realistic path is manual: property history, a recreated ticket, and re-linked associations.
Last updated: July 2, 2026
What does a ticket merge actually combine?
Tickets are on HubSpot's mergeable list alongside contacts, companies, deals, appointments, courses, listings, services, and custom objects (per the merge documentation, last updated June 17, 2026). When two tickets merge, HubSpot's documented behavior is:
- • Properties: the primary ticket's property values win; the secondary's value is only used where the primary has no value.
- • Activities: "all timeline activities of both records included in the merge will appear on the new record." Every note, email, and call from both tickets lands on the survivor.
- • Associations: all associated records of both tickets are combined onto the survivor.
- • Lists: the secondary record is removed from all static segments; those memberships are not carried over.
- • Paper trail: the survivor's Merged ticket IDs property records the Record ID values of every ticket previously merged into it.
In other words, one ticket keeps living with a blended identity, and the other stops existing as a separate record. Everything below follows from that.
Can you unmerge a ticket in HubSpot?
No. HubSpot's Knowledge Base asks the question for you, under a section titled "Can I unmerge records?", and answers it in six words: "It's not possible to unmerge records." There is no per-object qualification, no ticket exception, and no setting that changes it.
The only workaround HubSpot documents does not apply to tickets: "For contacts and companies, you can use the resulting additional email or domain name to create a new record." Tickets have no email or domain to free up, so even that narrow escape hatch is closed.
The recycle bin does not save you either. HubSpot's restore documentation never mentions merged records at all, so there is no documented path to pull the merged-away ticket out of the recycle bin, and no documented statement that restoring anything undoes a merge. More on that trade-off in Recycle Bin vs Unmerge.
The manual recovery path
Since no tool reconstructs tickets (ours included), the honest play is a careful manual rebuild. It will not resurrect the original record, but it can give your team a working ticket again with the right values and the right associations.
Establish exactly what was merged, and when
On the surviving ticket, open the left panel and click Actions > View all properties, then search for Merged. The Merged ticket IDs property lists the Record ID of every ticket merged into this one. Hover on the value and click Details to see who performed the merge and the timestamp. Write these down; they anchor everything else.
Pull the lost values from property history
Review the property history on the surviving ticket, property by property, around the merge timestamp from step 1. Values that changed at merge time tell you which side won each field. Capture the pre-merge values that belonged to the other ticket: subject, pipeline, status, priority, owner, and any custom properties your team relies on.
Recreate the ticket
Create a new ticket and enter the recovered values by hand. Note the old Record ID somewhere on the new ticket (a note or a custom property) so reporting and audits can trace the lineage. Then correct any field on the survivor where the wrong side's value won during the merge.
Re-link the associations
The merge piled both tickets' associations onto the survivor. Associate the recreated ticket with its rightful contacts, companies, and deals, and remove from the survivor any associations that only ever belonged to the other ticket. Do this from the association cards on each record, checking each one against what you know about the two original tickets.
The limits, stated plainly
- * The recreated ticket is a new record: new Record ID, new create date, empty timeline. Reports keyed to the original ID or date will not see it as the same ticket.
- * The conversation history stays blended. All timeline activities from both tickets landed on the survivor, and HubSpot's merge documentation describes no way to split them back out.
- * Merge history export will not help. Per HubSpot's documentation it only covers merges performed in the Data Quality tool, and that tool compares duplicates for contacts and companies, not tickets.
- * Property history has depth limits in practice. If a property was edited repeatedly after the merge, the pre-merge value you need may be harder to find or gone from view. The sooner you do this, the better it goes.
Can HubSpot Support help?
Not with an undo. HubSpot's own documentation leaves Support nothing to work with: the merge article's answer is "It's not possible to unmerge records.", full stop, and the restore documentation never mentions merged records, so there is no documented mechanism for Support to separate merged tickets or fish the merged-away ticket out of the recycle bin.
By all means open a ticket with Support, but go in with accurate expectations: they can point you at the same documented facilities described above (the Merged ticket IDs property and its merge details), not reverse the operation. Nothing in HubSpot's published documentation describes Support undoing a merge for tickets or for any other object. Any vendor or forum post promising otherwise is promising something HubSpot itself does not document.
If contacts or companies were merged in the same cleanup
Ticket merges rarely travel alone. If the same dedup pass or manual cleanup also merged people or companies, that part of the damage is recoverable: Emergency Unmerge reconstructs merged HubSpot contacts, companies, and deals, the three objects it supports, using property history analysis with per-field confidence scores you review before anything executes.
The scan is free and shows the exact credit cost before you commit to anything. For a wider sweep, the Free Bulk Scan checks up to 10,000 contact or company records per job and returns a downloadable report of every merge it detects, read-only, with no changes to your CRM. Fair warning on the fine print, because this page is for honesty: unmerging creates new records with new Record IDs (a HubSpot API limitation), and results are probabilistic, with simple merges typically achieving 90%+ confidence.
There is no subscription; credits start at $4.99 and never expire. See How It Works and pricing for the details, or start with the free scan and decide from the numbers.
Contacts, companies & deals only · Free scan · No CRM changes
Prevent the next ticket merge from needing this page
Since ticket merges cannot be undone and cannot be reconstructed, prevention is the whole game: tighten who can merge, and keep an export trail of ticket data on your side. For the objects where recovery does exist, CRM Data Backup & Restore by Third Space backs up HubSpot contacts, companies, and deals with one-click restore. Free up to 2,000 records.
Frequently Asked Questions
Can you unmerge a ticket in HubSpot?
No. HubSpot's documentation answers this directly: "It's not possible to unmerge records." The statement carries no per-object exception, so it applies to tickets the same as everything else. The only documented workaround, creating a new record from a freed-up email or domain, exists for contacts and companies, not tickets.
Does Emergency Unmerge work on merged tickets?
No. Emergency Unmerge reconstructs merged HubSpot contacts, companies, and deals only. It does not support tickets, and a scan cannot change that, so we would rather say so plainly. For a merged ticket, the realistic path is manual: pull the old values from property history, recreate the ticket, and re-link its associations.
Can HubSpot Support restore a merged ticket?
There is no documented path for that. The Knowledge Base states "It's not possible to unmerge records." and the restore documentation never mentions merged records at all, so there is no documented way for anyone, including Support, to separate merged tickets or restore the merged-away ticket from the recycle bin.
Related reading
Duplicate Cleanup Gone Wrong
What to do in the first hour after a bulk dedup merges the wrong records.
Recycle Bin vs Unmerge
Why the restore tool and merge recovery are two different problems.
Associations Lost After a Merge
Why records seem to lose their relationships after a merge, and how to repair it.