Guides

Can you merge leads in Pipedrive? Yes, but one gets deleted

By Tomi · Last updated

Yes. You can merge two leads from the three-dot menu in Pipedrive's Leads Inbox, but the lead you don't keep is deleted completely, and you can't undo it. Pipedrive says the other lead "will no longer exist in your account". Merged people, organizations and deals stay inactive for 30 days; in our sandbox test, the merged lead was already gone when we looked it up. If you might need it back, archive or delete the extra lead instead.

Lead merge tested through Pipedrive's API in a sandbox, October 2026. Steps from Pipedrive's help center. Last checked: October 30, 2026. What we couldn't verify.

What happens when you merge leads in Pipedrive

Part of the lead After the merge
The lead you keep Stays, with the same link
The other lead Deleted. It doesn't wait 30 days as inactive like a merged person or deal
Fields that disagree (value, owner, labels, source) You pick which lead's data to keep. Pipedrive says the other lead's "unique data will be added" to it, without saying which fields count
Notes and activities Not documented by Pipedrive, and we haven't tested it. Count them on both leads before you merge
The linked person and organization The merge joins leads, not contacts. If each lead had its own copy of the same person, check for a duplicate contact afterwards
Zaps and spreadsheets that used the other lead Broken. Its old ID points to nothing
A way back None. No undo button and no way to reactivate it through the API. You'd have to create it again, with a new ID

People, organizations and deals work differently: see what a merge does to each record type.

How to merge two leads in Pipedrive

You need the Merge duplicate leads permission, under the Deals app in Manage users > Permission sets (permission sets, updated September 3, 2026). Admins have it.

  1. Write down both leads' value, owner, labels and source channel, and how many notes and activities each one has.

  2. Open one of the leads from the Leads Inbox.

  3. Click the three-dot menu (...) at the bottom left of the lead and choose Merge.

  4. Type the name of the other lead and select it.

  5. Choose which lead's data to keep. That lead is the one that stays, so pick the one with the right value and owner.

  6. Click Preview, compare it with your notes from step 1, then Merge.

Steps from Pipedrive's Leads Inbox article (updated September 23, 2026). Tools and apps > Merge duplicates doesn't list leads, only people and organizations.

Archived leads: unarchive both first. Pipedrive asks you to unarchive a lead before editing it, and Dedupely says Pipedrive won't let it merge archived leads either.

Safer options than merging a lead

Option What happens Can you take it back?
Archive the extra lead Leaves the inbox but stays in your account, files included Yes, unarchive it any time
Delete the extra lead Gone from the inbox Yes, for 30 days from Tools and apps > Restore data (how it works)
Convert both to deals, then merge them Each lead becomes a deal with its person, organization, notes and activities. Then you merge the two deals Only through the API, within 30 days
Merge the leads One lead absorbs the other No

If the extra lead has nothing worth keeping (no notes, activities or emails), delete it. Unlike a merge, Restore data can bring it back for 30 days.

Don't convert duplicate leads without checking first. Two leads for the same person become two deals, and your pipeline counts the sale twice.

How to merge a lead into an existing deal

This is the most common duplicate: a lead comes in from a form for someone who already has an open deal. Pipedrive has no way to merge a lead into a deal, and its leads vs deals article (updated September 23, 2026) only describes converting a lead to a new deal.

Two ways to handle it:

  1. Keep the deal, drop the lead. Copy anything new from the lead onto the deal (a note, the source, a phone), then archive or delete the lead.
  2. Convert, then merge deals. Convert the lead to a deal (notes, activities, person and organization go with it), then merge the two deals, keeping the old deal. Its value wins.

Why Pipedrive creates duplicate leads

  • Web forms and LeadBooster. Forms, the chatbot, live chat and Prospector create leads, and Pipedrive doesn't document how they match someone who's already a contact. Check the Leads Inbox for repeat names once a week (more ways to prevent duplicates).
  • Imports. Every imported lead needs a person or an organization, and Pipedrive names the lead after it when your file has no title column. The import asks how to handle duplicates, but the help article doesn't say whether that covers leads. If an import created a batch of duplicate leads, a global admin can revert the whole import within 48 hours (import article, updated October 19, 2026), which is cleaner than merging them one by one.

Merging leads with AI today

  • Pipedrive's official MCP can't merge leads. Its 51 tools (list, updated October 22, 2026) read, create, update and convert leads to deals, but don't merge or delete. Claude or ChatGPT can find likely duplicate leads; you merge in Pipedrive (setup for Claude, what the MCP can't do).
  • The community servers and Pipedream actions we looked at merge people, organizations and deals, not leads. If a tool does merge leads, the lead it absorbs is deleted with no undo.
  • Dedupely merges leads in bulk and says "No merge can be undone".

A prompt that's safe to run: "List leads in Pipedrive that share a person, an organization or an email, with both lead IDs, value, owner and how many notes and activities each has. Also list leads whose person already has an open deal. Don't change anything."

What we couldn't verify

  • Which fields, notes, activities and labels move to the kept lead. Pipedrive only says "unique data" is added, and our test checked that the other lead was gone, not what moved.
  • Whether a merged lead appears in Restore data. The API couldn't find it after the merge, but we didn't check that page.
  • What happens to a duplicate person linked to the other lead, and to that lead's files and emails. Dedupely says file links on leads don't change in a merge.
  • Whether the app's merge window warns that the other lead is deleted right away, as it warns about 30 days for contacts.

Where Pipehand fits

Pipehand is planned to launch in April 2027, with early access for founding members from January 2027. It's designed to find duplicate leads, leads whose person is already a contact, and leads that are already an open deal, with the reason for each match. Your AI will be able to merge them after a field-by-field preview. Before every lead merge, Pipehand is designed to keep a copy of both leads, so an undo can recreate the deleted one (with a new ID, and it will tell you so). At launch, leads won't merge on their own: they'll always wait for your review.

If you want your AI to clean up duplicate leads with a preview and an undo, join the waitlist on pipehand.com.

FAQ

Can you merge leads in Pipedrive?

Yes. Open the lead in the Leads Inbox, click the three-dot menu at the bottom left, choose Merge, pick the other lead and which one to keep, preview and confirm. You need the Merge duplicate leads permission.

What happens to the other lead when you merge leads in Pipedrive?

It's deleted right away. Unlike people and deals, it doesn't wait 30 days as inactive, and in our test the API could neither find it nor reactivate it.

Can you undo a lead merge in Pipedrive?

No. There's no unmerge, so you'd have to create the lead again by hand, with a new ID. If you might need it back, archive or delete the extra lead instead.

Does Pipedrive's Merge duplicates tool find duplicate leads?

No. Merge duplicates only lists people and organizations. Look for leads with the same person or organization in the Leads Inbox (how to find duplicates).

Can you merge a lead into an existing deal in Pipedrive?

Not directly. Copy what you need from the lead onto the deal and archive the lead, or convert the lead to a deal and merge the two deals, keeping the older one.

For developers

Lead merge endpoint and webhooks
  • PUT /v1/leads/{id}/merge with merge_with_id returned 200 in our sandbox, but it isn't in the public spec. POST /v2/leads/{id}/merge returned 405. The absorbed lead returned 404 afterwards.
  • PATCH /api/v2/persons/{id} or /api/v2/deals/{id} with is_deleted: false reactivates a merged person or deal within 30 days. There's no equivalent for leads.
  • Archived leads can't be edited through PATCH /v1/leads/{id} except to unarchive them, since July 15, 2025 (changelog).
  • Webhooks v2 send lead delete for the absorbed lead with meta.merged_to_id and its fields in previous. Save them (or GET the lead before merging), because the API returns 404 afterwards. The event was marked change_source: app even though we merged through the API.