TL;DR
- HubSpot has no automatic deduplication for deals, unlike contacts and companies.
- Workflows, imports, cloning and integrations can each create a second HubSpot deal for one sale.
- A HubSpot deal merge keeps the primary deal's values and both deals' associations.
- A new deal ID is the default; the preservation beta keeps it. HubSpot merges cannot be undone.
- Dedupely finds duplicate HubSpot deals and merges them with rules for which value wins.
Duplicate deals in HubSpot show up in the pipeline first. The same sale appears twice, the forecast looks better than it is, and two reps may each think the deal is theirs.
Contacts and companies have some protection in HubSpot, through email and domain. Deals have none, so a second deal for the same sale is created without a warning.
In this post, you'll see where duplicate deals come from in HubSpot and how to tell a duplicate from a separate sale. You'll also see what a HubSpot deal merge keeps and how to choose the deal that survives. For duplicate deals in any CRM, see our post on how duplicate deals inflate your pipeline.
Why HubSpot deals duplicate without a warning
HubSpot deduplicates contacts by email and companies by domain. Its deduplication page lists no automatic property for deals. Deals can only be matched on their Record ID, or on a custom property you set to require unique values.
So when a rep, a workflow or an integration creates a deal, HubSpot doesn't compare it with existing ones. Our guide to HubSpot deduplication on free and paid plans covers what each plan adds for contacts and companies.
Source, as of October 2026: HubSpot's knowledge base, Deduplicate records in HubSpot.
Where duplicate deals come from in HubSpot
Causes differ from one portal to the next. These are the HubSpot features that can create a second deal.
Workflows that create deals
A workflow's "Create record" action can create a deal for each enrolled record. By default, the new deal is associated with the enrolled record and assigned to its owner.
Records enroll only the first time they meet the triggers, unless re-enrollment is turned on. With re-enrollment, a contact who fills in a second form can get a second deal. Two workflows that create deals for the same trigger have the same effect.
Imports
Deal rows without a Record ID or a unique value property are imported as new records. Importing the same file twice, or a corrected version of it, can double every deal in it.
Cloning
Cloning a deal creates a new record with the same configured properties and associations. That's useful for a renewal or a second order, and it can leave a near-identical deal when someone clones by mistake. HubSpot's Record source property lets you filter cloned records.
Integrations and reps
Billing, ecommerce and other CRMs can create deals through the API, each with its own logic for finding an existing one. Reps also create deals by hand, and nothing stops two of them from logging the same opportunity.
Sources, as of October 2026: HubSpot's knowledge base, Create records with workflows, Workflows FAQ and Clone a record.
Is it a duplicate or a separate sale?
What counts as a duplicate deal is case by case: what one team considers a duplicate, another may not. Two deals at the same company can be a renewal, an upsell or a second product line. Check these signals before merging.
| Signal | Points to a duplicate | Points to a separate sale |
|---|---|---|
| Create date | Created minutes or hours apart | Created months apart |
| Associated contact and company | Same people on both | Different buyers or departments |
| Amount and line items | Same amount and products | Different products or terms |
| Pipeline | Same pipeline | Different pipelines, like new business and renewals |
| Record source | A workflow, an import or a clone | Created by a rep for a new request |
Start with the obvious duplicates: same company, same amount, same pipeline, created close together. Send the rest to the deal owners before you decide.
What a HubSpot deal merge keeps
HubSpot merges two records of the same object at a time, deals included. Its merge article lists special rules for some contact, company and ticket properties, but none for deals. So deals follow the general rules, as of October 2026.
| What | What happens in a merge |
|---|---|
| Property values | The primary deal's values are kept. The other deal fills only properties that are empty on the primary. |
| Create date and history | The oldest create date is kept, and property history from both deals is combined. |
| Activities | All timeline activities from both deals appear on the merged deal. |
| Associations | All associated records from both deals appear on the merged deal. The secondary deal's Primary company label is removed. |
| Record ID | By default, the merged deal gets a new Record ID. Accounts enrolled in Primary ID Preservation keep the primary ID instead. The Merged record IDs property records merged IDs. |
| Workflows | By default both deals leave active workflows. In Primary ID Preservation, the primary stays enrolled and the secondary is unenrolled. Check your account and merge method before changing workflow enrollments. |
| Undo | Not possible. HubSpot doesn't let you unmerge records. |
| Limits | No merges for a record that's been through 250 or more merges, and association limits still apply. |
Source, as of October 2026: HubSpot's knowledge base, Merge records.
What that means for amount and stage
Because the primary deal's values win, its amount, stage, close date and owner become the merged deal's. If the secondary deal held the right amount, that value is lost unless you edit it first.
HubSpot's merge article doesn't mention line items or quotes. Check both on a test merge before merging deals that carry them.
What that means outside HubSpot
Check anything that stores deal IDs, such as billing systems, warehouses and spreadsheets. The default merge changes the primary ID; the preservation beta retains it. References to the secondary deal still need review, and a working CRM link does not prove an integration has updated its mapping.
How to choose the deal that survives
Since merges are permanent and the primary deal's values win, the choice of primary matters more than any other step.
- The deal with the correct stage and amount. Or edit the primary first, so the right values survive.
- The deal other systems reference. Check how the merge handles its ID and how each connected tool follows merged or removed records.
- The deal with the quote. Keep the deal your customer has seen as the one that stays.
- The right owner. Agree on ownership first, so the merge doesn't move a deal between reps by accident.
Keep an export of both deals before merging. Our post on backing up your CRM before a large merge covers what to save.
How to keep new duplicate deals out
Once the backlog is merged, the sources above decide how fast new duplicates form.
- Review every workflow that creates deals, and check its re-enrollment triggers.
- Import deal updates with the Record ID or a unique value property.
- Ask each integration how it finds an existing deal before it creates one.
- Filter by Record source now and then to spot clones nobody followed up on.
How Dedupely cleans up duplicate deals in HubSpot
Dedupely connects to your HubSpot deals, where you build duplicate searches on the deal fields you choose, like deal name, amount or close date. You set rules for which value wins, preview each merge and merge the sets you're sure of in bulk. Unclear sets can go to review for the deal owners to check.
One deal for every sale
HubSpot gives contacts and companies a key to match on, and deals none. Workflows, imports, clones and integrations can each add a second deal, and nothing warns you when they do.
A merge fixes the pipeline, but it keeps the primary deal's values and can't be reversed. Deciding what counts as a duplicate, and which deal should survive, is what makes the cleanup safe.
Frequently asked questions
Why does HubSpot create duplicate deals?
HubSpot has no automatic deduplication for deals, so it doesn't compare a new deal with existing ones. Duplicates often come from workflows that create deals, imports without a Record ID, cloned deals, integrations and reps logging the same opportunity. A property that requires unique values, like an order number, helps prevent them.
Can you merge deals in HubSpot?
Yes. Users with merge permission can merge two deals at a time. The primary deal's values generally win, and the secondary fills empty properties. Check associated line items and quotes on a sample. HubSpot creates a new ID by default; accounts in Primary ID Preservation keep the primary ID.
What happens to associations when you merge deals in HubSpot?
All associated records from both deals, like contacts and companies, appear on the merged deal. The primary deal's Primary company label is kept, and the secondary deal's label is removed. Timeline activities from both deals carry over too. HubSpot's merge article doesn't mention line items or quotes, so check them on a test merge.
Can you undo a deal merge in HubSpot?
No. HubSpot does not support unmerging deals. A new ID is created by default, while Primary ID Preservation retains the primary ID. Export both deals and check linked data before merging; retained IDs do not make a merge reversible.
How do I stop workflows from creating duplicate deals?
Check each workflow that creates deals and its re-enrollment settings. By default, records enroll only the first time they meet the triggers, so re-enrollment is a common cause of repeat deals. Also make sure two workflows don't create deals for the same trigger, and add a unique value property where you can.
Or sign up with Google
HubSpot Marketplace 
