TL;DR
- A Pipedrive merge keeps the primary item's values when two items disagree.
- Every unique email and phone number stays on the merged Pipedrive record.
- Activities, notes, deals and linked organizations move to the surviving Pipedrive record.
- Archived Pipedrive deals and leads can't be merged.
- Dedupely merges Pipedrive People, Organizations, Deals, Leads and Products with rules you preview.
In Pipedrive, the same person or company can end up in your pipeline several times. Reps open the wrong record, log a call on it, and the history splits in two.
Merging fixes that, as long as you know what the merged record will hold. Which email stays, where do the deals go, and what happens to the notes on the losing record?
In this post, you'll see what happens to each part of a record when you merge in Dedupely for Pipedrive. For how Pipedrive's own duplicate tool finds and merges items, see Pipedrive duplicates and where native merging stops.
Which Pipedrive records Dedupely merges
Dedupely syncs and merges Pipedrive People, Organizations, Deals, Leads and Products. Pipedrive's own merge pages describe people, organizations and deals, so Leads and Products are where Dedupely covers the most new ground.
As of October 2026, from Pipedrive's support center: Merge duplicates and Updating items in the detail view.
A merge always combines items of the same type. A lead won't merge with a person, and a deal won't merge with an organization. Connecting Pipedrive to Dedupely needs Admin permissions, and syncing only reads your data until you start a merge.
Which values the merged record keeps
Every merge keeps one item and decides which value survives in each field. In Pipedrive, the primary item's information wins when the items disagree. If two people have different phone numbers in the same field, the primary person's number is the one that stays.
As of October 2026, from Pipedrive's support center: Merge duplicates.
If you haven't set Merge Rules, Dedupely follows Pipedrive's own merge logic. With Merge Rules, you choose the record that survives: the oldest, newest, last updated, most complete or a custom choice.
Then you set rules field by field, like keeping the most recent phone or the owner of the record with the open deal.
Blank fields never overwrite existing data, so an empty value on one record won't erase a filled one on the other.
Emails and phone numbers are combined
People in Pipedrive can hold several emails and phone numbers. When Dedupely merges them, multi-value fields are combined, so every unique email and phone number stays on the surviving record.
That matters for people who use a work and a personal address, or who changed numbers. Nobody loses the address a customer replies from.
For other multi-value fields, Merge Rules can append values from every record instead of picking one. Append only works on fields that hold several values.
What moves to the surviving record
A merge in Dedupely for Pipedrive keeps the history of every record in the set.
| Part of the record | What happens |
|---|---|
| Activities | Move to the surviving record |
| Notes | Move to the surviving record |
| Deals | Linked deals move, so the person or organization keeps its full pipeline |
| Linked organizations | Move with the person |
| Emails and phones | Every unique value is kept |
| Other fields | The primary record's value, or your Merge Rules |
After the merge, a rep looking for that customer finds one record with every call, note and deal on it.
What can't be merged
Archived deals and archived leads can't be merged. Plan for them before a cleanup, since old lost deals and leads are often where duplicates sit.
Records of different types never merge, as covered above. Neither do records in two different Pipedrive accounts, since Dedupely matches within each connected account.
Pipedrive's help page says merged duplicates can't be un-merged in Pipedrive. Most Dedupely merges can be undone for 30 days from Merge History, except Products.
As of October 2026, from Pipedrive's support center: Merge duplicates.
When overlap doesn't mean duplicate
What counts as a duplicate is case by case. Two Pipedrive organizations can share an email, an address and a phone and still be two companies.
Relatives raise the same question for people. Two siblings can share a last name, an address and a household and still be two people. A field that tells them apart keeps them out of the same set, like a legal ID or an exact match on first name.
Merging many records at once
Pipedrive's native merge combines one pair at a time. Dedupely lets you bulk merge a whole page of sets, or every set in a search, with the same rules applied to each one. Bulk merging a few thousand matches takes minutes.
Once a search has proven itself, you can merge new duplicates you're certain of, like exact email matches, automatically on a schedule. Automatic merging never touches sets you've rejected, held back or sent to review.
What you can see before and after a merge
Before a set merges, Dedupely shows the winning values in bold and a Preview Merge panel with the full record. Check a few previews from each search, including your edge cases.
After the merge, Merge History records the original records, the winning values and a link to the merged record in Pipedrive. You can export it as a CSV with the original data and record IDs.
If the wrong records merge, restore the values from that CSV and reject the false match. Our playbook on what to do if you merged the wrong records walks through it.
How Dedupely helps you merge Pipedrive duplicates safely
In Dedupely, you build duplicate searches for each Pipedrive item type and set rules for which value wins. You preview each merge, reject false matches and send unclear sets, like related companies, to review. Then you bulk merge the sets you're sure of.
One record with the whole history
A merge in Dedupely for Pipedrive brings a customer's activities, notes, deals and contact details onto one record. Emails and phones are combined, blanks never overwrite filled fields, and you decide which values win elsewhere.
The decisions that matter come before the merge. Know which sets are true duplicates, keep archived items and look-alike companies out, and check the preview. After that, reps open one record and see everything.
Frequently asked questions
What happens to activities when you merge in Pipedrive?
They move to the surviving record. In Dedupely, activities, notes, deals and linked organizations from every record in the set move to the record that survives. A rep who opens the merged person or organization sees the calls, meetings and notes that were split across the duplicates before.
Does a Pipedrive merge keep both email addresses?
Yes, when you merge in Dedupely. Multi-value fields are combined, so every unique email and phone number stays on the surviving person. In Pipedrive's own merge, the primary item's values win when two items conflict, so check which item you choose as primary.
Can you merge archived deals in Pipedrive?
No, archived deals and archived leads can't be merged in Dedupely. Decide how to handle archived items before a large cleanup, since old lost deals and leads are often where duplicates sit. Agree with your team on whether archived items still matter for reporting and history.
Can you undo a merge in Pipedrive?
No, Pipedrive's help page says merged duplicates can't be un-merged, and merges made through other tools happen in Pipedrive too. Not in Pipedrive itself: its help page says merged duplicates can't be un-merged. Most Dedupely merges can be undone for 30 days from Merge History, except Products. Undo is for records that weren't duplicates, so treat every merge as permanent and keep the original values before a large merge. Merge History also exports the original records as a CSV. See how to undo a merge.
Can you merge more than two Pipedrive records at once?
Not with Pipedrive's native merge, which combines one pair at a time. Larger backlogs take a deduplication tool that bulk merges. With Dedupely, you can bulk merge a page of sets or every set in a search, and the same rules decide each merge.










