# Convert a deal back to a lead in Pipedrive: the middle option between stuck and Lost

https://salesbond.app/blog/pipedrive-convert-deal-to-lead/
Published: 2026-10-04 · Updated: 2026-10-25

Convert a deal to a lead when the buyer has given you a concrete “not now” with a date, and you want the contact out of your pipeline numbers but not out of your sight. Pipedrive moves the fields, contacts, activities, emails, notes and files to the new lead. It does not move the deal history, the deal labels or the invoices, and the person who clicks Convert becomes the lead’s owner ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)). That last pair of facts is what this post is about, because the help page tells you how to click and says nothing about when, or about what the click does to your reports.

## Three exits for a stuck deal: keep, lose, send back

A deal that has not moved in two months has three ways out of the open pipeline. You keep it open and accept that it inflates the weighted forecast. You mark it Lost with a reason. Or you send it back to the Leads Inbox.

Most teams only use the first two, and “Lost: no decision” ends up holding every buyer who said “call me in Q2”; what that does to win rate is in [deals that end in “no decision”](https://salesbond.app/blog/no-decision-deals-pipedrive/). The two pieces of advice fit together like this: a “no decision” with no date is Lost, as that post says, and a “not now” with a date comes here.

Convert to lead is the right exit when the opportunity is real but the deal is not. The buyer has a budget cycle, a hiring freeze, a reorganization, and they told you so. There is a date. There is no reason to count that contact in stage conversion or weighted pipeline for the next five months, and there is every reason to keep the notes, the emails and the next activity.

It is the wrong exit for a deal where the buyer simply stopped answering. Silence is not “not now”. A silent deal is Lost with an honest reason; sending it to the Leads Inbox moves the fiction from one list to another, and leads have thier own expiry problem, which the [leads vs deals](https://salesbond.app/blog/pipedrive-leads-vs-deals/) post covers.

If the buyer did give a date, here is [where a not-now lead lives until it comes back](https://salesbond.app/blog/lead-recycling-pipedrive/).

Pipedrive’s guide to freeing up space also lists converting stagnant deals to leads, up to 100 at a time, as one way to get under the open deals limit ( [Pipedrive: how can I free up space](https://support.pipedrive.com/en/article/how-can-i-free-up-space)). Under the leads and deals limit, which replaces the open deals limit for all accounts by October 2026, leads count too, so converting a deal frees no space; more on [the usage limit and the deals waitlist](https://salesbond.app/blog/pipedrive-deals-waitlist-open-deal-limit/). If you never plan to work those deals again, [archiving](https://salesbond.app/blog/pipedrive-archive-old-deals-leads/) is the better tool: it keeps the history and does not change the owner.

## What Pipedrive carries over when you convert a deal to a lead

The converted lead gets the deal’s fields, including value and the contact information, the linked person and organization, the activities (done and scheduled), the linked emails, the notes and the files. It does not get the invoices, the deal labels or the deal history ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)).

![Two cards: fields, contacts, activities, emails, notes and files travel to the lead; history, labels and invoices stay behind](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-convert-deal-to-lead-2.png)

Invoices are bookkeeping, and they stay with your invoicing. Deal labels are a workflow matter. If your team runs on labels like “Champion identified” or “Procurement stage”, those markers are gone on the lead, and you will relabel in the Leads Inbox with lead labels, a separate system.

Deal history is the one that bites later. The changelog of a deal records every stage move, every close-date push, every owner change with a timestamp. That is the the raw material for cycle length, for stage conversion and for the kind of close-date audit we described in [auditing pushed close dates through the deal changelog](https://salesbond.app/blog/pipedrive-deal-changelog-close-date-audit/). The lead does not inherit it.

Then there are the gaps. Pipedrive shows a warning when the deal carries formula field data and does not spell out what happens to those values, and the help page is silent on the deal’s stage and time in stage, participants, products and any automations that were watching the deal. We treat all of these as gone.

## The owner changes to whoever clicks: a trap for bulk conversion

Pipedrive is explicit here. The user who converts becomes the owner of the resulting lead ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)).

For one deal that is a footnote. Maria converts her own stalled deal, Maria owns the lead, nothing changed.

For a bulk conversion it is the whole story. Picture a rep handing over a territory before he leaves the company; the account is made up, the shape is common. His manager filters his open deals with no activity in 90 days, selects 80 of them and clicks Convert to leads from the list view. Pipedrive shows a confirmation window and emails her when the batch finishes. The next morning there are 80 leads in the Leads Inbox, and every one of them belongs to her, not to the rep who inherits the territory. He never sees them in “my leads”. And because the deal history did not travel, there is no changelog on the lead that says who owned the deal before.

Who can do this? Global admins and anyone with the “Convert deals to leads” permission, and Pipedrive enables that permission for regular users by default ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)). So this is not a manager’s trap only. A rep who tidies up a shared filter that happens to include a colleague’s deals walks into it just as easily. Because it is a permission, an admin can switch it off for the people who should not be doing bulk conversions.

Our rule is short. Whoever will follow up on the leads runs the conversion, from a filter scoped to one owner. In the handover case that means reassigning the deals to the new rep first and letting him convert. Before anyone converts, export or screenshot the deal list with the Owner column visible, because that export is the only place the pre-conversion ownership will exist afterwards. Same discipline as in [bulk edit safety](https://salesbond.app/blog/pipedrive-bulk-edit-safety/).

## A three-question test before you convert

The click takes a second. The decision deserves three questions, in this order, and a “no” on the first one ends the conversation.

1. **Is there a named reason and a date?** “Budget reopens in January”, “new VP of Ops starts in March”. The lead needs a scheduled activity on or near that date, and it should be on the deal already so that Pipedrive carries it over. If the only reason is “they went quiet”, this is a Lost deal that has not been admitted yet.
2. **Who will own the lead after the click?** Whoever converts. If that is not the person who should follow up, hand the deal to that person first so they convert it, or plan the reassignment as part of the same sitting. A lead owned by the wrong person is a lead nobody calls.
3. **What are we losing from the reports, and have we written it down?** The deal history goes. If the deal spent four months in Proposal and that matters to your stage-conversion numbers, note it before converting: the stage, the days in stage, the close date it was carrying. A one-line note on the deal travels to the lead; the changelog does not.

Three yeses and you convert. We would still convert one deal before converting ninety, because the owner change and the missing labels become visible on one record while the filter and the export are still open and the batch is still a plan.

![Three-question checklist before converting a deal to a lead, each with a "no" exit, ending in "Three yeses: convert"](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-convert-deal-to-lead-3.png)

## What it does to your reports (cycle length, stage conversion)

The pipeline report gets better. That is the point. A deal that will not close for five months is noise in weighted pipeline and in every “deals by stage” chart, and taking it out makes the numbers your team argues about closer to reality.

Two other numbers get quietly worse, and both come from the same missing changelog.

Cycle length first. Say the deal was created in February, sat in Proposal from April, and the buyer said “January” in June. You convert. In January the lead comes back as a deal. Since the lead never received the old deal’s history there is nothing for it to pass on, and from the report’s point of view that deal is born in January. The months of real sales effort never happened. Convert ten such deals a year and your average cycle length is flattering and wrong, and the error points in the direction people like, which is why it goes unnoticed.

Stage conversion second. The old deal’s trip through Qualified and Proposal is in it’s changelog, and the changelog stays with the deleted deal, not with the lead. Pipedrive keeps deleted deals restorable for 30 days; after that they are permanently deleted and can’t be accessed or restored ( [Pipedrive: how can I restore deleted deals](https://support.pipedrive.com/en/article/how-can-i-restore-deleted-deals)). Whatever that deal told you about your stages has a 30-day shelf life.

The practical answer is a lead field. Add a custom field on leads, something like “Prior deal: stage and days”, and fill it in at question three before converting. It is a crude substitute for a changelog, but it survives the trip, and when the lead becomes a deal again the field is still there to read. For the volume, Pipedrive’s help suggests a report on the “Lead source” field to see how many deals you have converted ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)). The report gives you the count; the field gives you what each lead used to be.

A disclosure belongs here. 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 against more than 20 rules, gives it a score from 0 to 100, shows the specific violations behind that score and explains what to do. It flags the deal. It does not decide the exit, and it should not; the three questions above are a human’s. If you want the candidates surfaced before a handover instead of during it, [Check your CRM with SalesBond](https://salesbond.app/).

## Undo: how to restore, and why the lead stays

Conversion is reversible in one sense: the deal is not gone. Pipedrive moves the original deal to deleted deals. To undo, filter the deals list for deleted deals, find the one you converted, and restore it. The converted lead stays in the Leads Inbox ( [Pipedrive: converting deals to leads](https://support.pipedrive.com/en/article/converting-deals-to-leads)).

Read that last sentence twice. Undo does not reverse the conversion. It gives you back the deal and leaves you with a duplicate lead. If you restore and walk away, the rep has a deal in the pipeline and a lead in the inbox for the same buyer, and whichever one gets the next call, the other one rots. Restoring is a two-step job: restore the deal, then archive or delete the lead, in the same sitting.

The restore guide adds two limits. Only admin users can restore a deleted deal, so a rep who converted by mistake needs an admin, even though converting was in their own hands. And the window is 30 days; inside it, a restored deal reopens in the same stage it was in when it was deleted ( [Pipedrive: how can I restore deleted deals](https://support.pipedrive.com/en/article/how-can-i-restore-deleted-deals)).

Going the other way is the ordinary direction: a lead converts into a deal as usual, which [leads vs deals](https://salesbond.app/blog/pipedrive-leads-vs-deals/) covers. And if what you wanted was the deal out of sight with its history intact, that was archiving, not converting.

So if someone on your team ran a bulk conversion in the last few weeks, the clock is already running. List the converted deals, restore the ones that should not have moved in one pass, clean the duplicate leads in a second, and fill in the prior-stage field for the ones that stay as leads. The [import revert](https://salesbond.app/blog/pipedrive-import-revert-48-hours-merge/) post walks through the same pattern for imports, and it transfers.