# Merging two deals in Pipedrive: pick the primary one before you click Merge

https://salesbond.app/blog/pipedrive-merge-two-deals-primary-deal/
Published: 2026-10-04 · Updated: 2026-10-26

To merge deals in Pipedrive, open one of the two deals, click More (…) > Merge, find the other deal by name, choose which deal’s data to keep, click Preview, then Merge ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates), [Pipedrive: how can I clean up my account](https://support.pipedrive.com/en/article/how-can-i-free-up-space)). Deals merge only from the detail view, not with the Merge Duplicates tool. The help promises no undo, so pick the primary deal before you click.

## A merge that stopped at “keep this data”

An invented scene, but you will have seen the shape of it. Lena Arkwright runs a sales team of six. Piotr Bell joined in spring and took over the accounts of a rep who left, including a logistics company the old rep had been talking to for most of a year. Piotr called, got a meeting, and created a fresh deal in his own pipeline. Nine months of emails, notes and a half-finished proposal sat on the old deal, two stages back, still open, with an expected close date that had passed in February.

Lena found the pair in a forecast review. Two open deals, one buyer, two values, two close dates. “Merge them,” she said. Piotr opened the first one, clicked Merge, found the second one, and then stopped at the “keep this data” choice.

He was right to stop. Why a second deal skews the numbers is covered in [duplicate records in Pipedrive](https://salesbond.app/blog/duplicate-records-in-pipedrive/). This article is about the click itself, which is quick and, as far as anyone can tell, final. When the two deals come from [a Zap that ran twice](https://salesbond.app/blog/pipedrive-zapier-duplicate-records/), merge them as below, then fix the source.

## Which deal to keep as primary when you merge

Pipedrive has two labels for this decision. The Merge Duplicates tool for people and organizations calls the winner the “primary” item: its information takes priority wherever the two records conflict, as in the help’s example with two Tom Smith contacts ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates)). In a manual deal merge, the same choice is the “keep this data” bubble, which decides “which item will continue to exist in your account” ( [Pipedrive: how can I clean up my account](https://support.pipedrive.com/en/article/how-can-i-free-up-space)). We call the survivor the primary deal.

Our rule is three questions, in order. Stop at the first one that gives a clear answer.

1. Which deal has the history you couldn’t retype? Emails, notes, call outcomes, the files the buyer sent. Whatever does or doesn’t carry over from the other deal, the primary deal’s own record is the the one that continues. Irreplaceable history makes a deal primary, nearly always.
2. Which deal has fields you’d defend today? Stage, value, expected close date, owner. If the answer points the other way from question one, question one still wins: fields take a minute to fix after the merge, while history can’t be recreated by hand.
3. What already points at it? An automation that created it, a report filter, a spreadsheet row with its deal ID. The primary deal’s ID is the one that keeps working outside Pipedrive ( [updating Pipedrive records from a spreadsheet by system ID](https://salesbond.app/blog/pipedrive-update-records-spreadsheet-system-id/) ).

If all three tie, keep the older deal. It has been in reports longest.

For Lena, that means the old rep’s deal, stale fields and all. Piotr’s deal has the right stage, the right close date and three weeks of history. The old one has nine months. Keep it, then spend two minutes bringing it’s fields up to date.

## Four fields to compare before you open Preview

By the time Preview shows you the merged deal, the choice is already made. So the comparison happens earlier, on the two open deal cards, and we write it down somewhere that survives the click: a note, a chat message to the rep.

![Two schematic deal cards compared field by field; Deal A is marked primary, Deal B's stage and close date need copying by hand.](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-merge-two-deals-primary-deal-2.png)

Owner first. Different owners make the merge a handover too, because one of those two people is about to lose a deal from their pipeline. Agree on it out loud beforehand. A rep who finds a deal gone and has to ask what happened won’t trust the pipeline for a while.

Stage next. Two stages means at least one of them is wrong about where the buyer is. Decide the true stage now, if you keep the deal with the earlier stage, you’ll need to move it right after the merge, and that’s easy to forget once the card looks clean.

Value. Two values usually mean two offers, or one offer and one guess. Find out which number the buyer actually saw. Don’t split the difference.

Expected close date. The one in the past is nearly always the stale one. The primary deal needs a date someone believes in, or it goes back into the forecast as a deal that should have closed months ago.

One more, not a field but a link: the person and organization on each deal. If they’re different companies, pause. You may be looking at two buying processes, and the last section is for you. A similar mix-up happens when one company has bought the other: with [a prospect acquired mid-deal](https://salesbond.app/blog/prospect-acquired-mid-deal-pipedrive/), the answer is to link the organizations, not to merge them.

A merge is a bulk edit of two records, so the usual habit applies: write down what you expect to see afterwards, then check ( [bulk editing in Pipedrive without breaking the pipeline](https://salesbond.app/blog/pipedrive-bulk-edit-safety/)).

## What the help article says, and what it doesn’t

Pipedrive’s help describes five steps and shows one example of data carried over: an activity. Both pages we read today were last updated on September 3, 2026.

1. On the deal’s detail view, click More (…) and select Merge ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates) ).
2. Type the other deal’s name in the search bar; the first few letters bring up autofill options. Once you select it, both deals are displayed ( [Pipedrive: how can I clean up my account](https://support.pipedrive.com/en/article/how-can-i-free-up-space) ).
3. Choose which data to keep with the “keep this data” bubble.
4. Click Preview to see the merged deal, “including the data that’s been merged into it”. The help’s example: a deal with no linked activities now has one from the other deal.
5. Click Merge.

That one activity is all either page says about what travels from the second deal. Notes, files, email threads, products, custom fields, stage history: not listed. We won’t list them on Pipedrive’s behalf. If you need to know what your account does with a particular kind of data, merge two throwaway test deals first and look.

Neither page says a deal merge can be undone. The warning that merged items “can’t be un-merged” is written about the Merge Duplicates feature ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates)); about manual deal merges there is no sentence either way. We treat it as permanent, because planning around an undo the vendor hasn’t promised is how you end up explaining a missing deal to a rep.

So, two minutes of insurance. Pipedrive’s cleanup article recommends exporting data you plan to remove before deleting it ( [Pipedrive: how can I clean up my account](https://support.pipedrive.com/en/article/how-can-i-free-up-space)), and we borrow the habit for merges. Export the deal you’re about to give up, or at least paste a note into the primary deal: which deal it was merged from, the date, and the old stage, value and close date. If something doesn’t come across, you’ll know what it was. Merging during an import is a separate story: [what the import revert can and can’t bring back](https://salesbond.app/blog/pipedrive-import-revert-48-hours-merge/).

## Who is allowed to merge

Admin users can merge, and so can regular users whose permission set allows it; a regular user only sees the duplicates their visibility settings allow ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates)). The visibility point carries over to deals: a rep can only merge what they can open.

Our practice is narrower than the permission. One person merges deals, usually the manager or whoever administers the account, and reps request a merge with two links and their answers to the three questions. A merge changes a record someone else may rely on, and one pair of hands means one place to ask what happened.

## When closing the second deal beats merging

Sometimes the four-field comparison comes back ugly. Different contact, different product line, unrelated values, and the only thing the two deals share is the organization name. At that point we stop calling it a duplicate. It may be two buying processes at one company, and then both deals stay open with honest fields. Or it may be one live process and one that died quietly months ago. The dead one doesn’t need to be folded into the live one.

It needs to be closed.

Mark the second deal lost with “duplicate” as the reason ( [Pipedrive: lost reasons](https://support.pipedrive.com/en/article/lost-reasons)). The reason is saved on the deal, so the record stays in your history where you can find it. Pipedrive uses freeform reasons by default; if your account has switched to predefined ones, someone with the Deals admin permission has to add “duplicate” to the list first. Even a deleted deal can be recovered for 30 days after deletion ( [Pipedrive: how can I clean up my account](https://support.pipedrive.com/en/article/how-can-i-free-up-space)). A merged one, as far as the help says, can’t. So when the fields disagree enough that you can’t say with a straight face which record is true, close the second deal, write down why, and move on.

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal in the connected CRM and gives each one its own health score, so a duplicate is just one more deal in the list. Picking the primary deal stays with you: three questions, a note, and someone who knows the account. [Check your CRM with SalesBond](https://salesbond.app/).