TL;DR
- Deals in different pipelines are often separate deals, not duplicates.
- New business and renewal, or sales and onboarding, are related records.
- A duplicate is the same opportunity entered twice, sometimes in the wrong pipeline.
- When you merge, keep the pipeline and stage from the same record.
- Dedupely filters keep pipelines apart in a search, and Merge Rules decide which deal survives.
A duplicate search on deals finds "Acme renewal 2027" in the Renewals pipeline and "Acme renewal" in the New Business pipeline. Same company, similar names, similar amounts. Merge them? Maybe. Deals in different pipelines need one more question than other duplicates: are they the same opportunity, or two stages of one relationship?
Related or duplicate?
| Two deals for one customer | Usually |
|---|---|
| New business and the renewal a year later | Related: keep both |
| Sales deal and onboarding project | Related: keep both |
| Two products sold separately | Related: keep both |
| The same deal created by two reps in their own pipelines | Duplicate |
| The same deal created by a form and by a rep | Duplicate |
| A deal moved to a new pipeline by copying it instead of moving it | Duplicate |
The test: if both deals closed, would you count the revenue twice? If yes, and it's the same money, they're duplicates.
What a merge keeps
A deal can only be in one pipeline, at one stage. When two deals merge, the surviving deal keeps one pipeline and one stage, usually from the primary record. In HubSpot, the primary record's values are kept, and the other record's value only fills properties the primary leaves blank.
Stages belong to pipelines. If the pipeline comes from one deal and the stage from the other, you can end up with a stage that doesn't exist in that pipeline. Always keep the pipeline and the stage from the same record.
How to merge them safely
- Search deals within one pipeline first, where duplicates are clearest.
- Then search across pipelines, and review every set by hand.
- Pick the primary by where the work is happening: the pipeline the owner uses and the more advanced stage.
- Keep pipeline and stage from the primary.
- Check reports by pipeline after the merge, since one pipeline's count will drop.
How Dedupely handles deals across pipelines
In Dedupely, you can filter a deal search on the pipeline field, so one search covers one pipeline and cross-pipeline pairs only appear when you choose to look for them. Manual Review holds the uncertain sets until someone checks them, and rejected matches stay out of future searches. Merge Rules decide which deal survives: a Custom Primary Record rule can prefer the deal in a given pipeline, and setting the pipeline and stage fields to Primary keeps both from that same deal. Dedupely merges HubSpot deals, Pipedrive deals and Close opportunities.
Same opportunity, or same customer?
Deals in different pipelines are often related, not duplicate. Merge them only when they're the same opportunity entered twice, keep the deal where the work is happening as the primary, and take the pipeline and stage from that same deal.
Frequently asked questions
Should I merge deals that are in different pipelines?
Only if they're the same opportunity entered twice. A renewal and a new-business deal for the same customer are separate deals.
Which pipeline does the merged deal keep?
Usually the primary record's. Choose the primary by where the work is happening.
Can the pipeline and stage come from different deals?
They shouldn't. A stage belongs to a pipeline, so keep both from the same record.
How do I stop related deals from showing up as duplicates?
Filter deal searches by pipeline and reject pairs that are related, so they stay out of future searches.
Will my pipeline reports change after merging?
Yes. The pipeline that held the duplicate will show one fewer deal and less value.




HubSpot Marketplace