Short answer
Marking a deal lost records a sales outcome; archiving removes it from active management while keeping its previous status; deleting removes it from the CRM, and Pipedrive only lets an admin restore it within 30 days. Before bulk changes, check reports, filters, exports and integrations: archiving does not mean every consumer continues counting the record identically.
Key verification: The sample preserves its sales outcome and views or integrations include or exclude archived records as intended.
Sources and limitationsA pipeline is full of old deals and someone suggests marking them all as lost to clear it. That changes the meaning of the history if some were won or simply needed to stop appearing in day-to-day work. Separate outcome, operational visibility and retention policy before choosing an action: marking lost records a sales outcome, archiving removes the deal from working views without changing its outcome, and deleting removes it from the CRM with a limited window to recover it.
What each action changes
| Action | What changes | What is kept | Going back |
|---|---|---|---|
| Mark as lost | Sales status and lost reason | The whole record, visible in the lost deals view | Reopen the deal |
| Archive | Hidden from most list and pipeline views; can no longer be edited | Previous status (open, won or lost), search and export | Unarchive, one by one or in bulk |
| Delete | Leaves the CRM and its reports | Nothing after the recovery window | Restore within 30 days, admins only |
The table summarises Pipedrive documentation consulted on 27 October 2026, cited in the sections below. Check permissions and plan in your own account, because some features depend on them.
Choose the action with three questions
Three fictitious situations
| Situation | Reasonable decision to evaluate | Prior evidence |
|---|---|---|
| Customer rejects the proposal | Lost outcome with a reason | Confirmed rejection |
| Won work already delivered | Archive while keeping it won | Delivery and obligations reviewed |
| Unnecessary test record | Delete under an authorised policy | Test identity and dependencies |
An open deal with no reply from the customer for months has no confirmed outcome. Marking it lost is legitimate if your closing rule allows it, but the reason must then reflect that; the guide to lost opportunity reasons proposes an "Unconfirmed" value for these cases.
Effects documented by Pipedrive
The help article on archiving deals and leads states that archiving keeps the previous status (open, won or lost), that title, value, stage, owner and custom fields cannot be changed, and that new activities cannot be linked and the deal cannot be merged. Archived deals are hidden from most list and pipeline views, appear in search and can be exported from list views.
It also warns that the standard API list endpoints do not return archived deals, that archiving can trigger automations and that, when unarchived, a deal whose pipeline or stage no longer exists will not appear in any pipeline until one is assigned. Archiving another user's deals requires the permission to edit deals owned by others. Do not read "keeps history" as a guarantee that every report, filter or export includes them.
Deleting: a short window and a written policy
According to Pipedrive's help on restoring deleted deals, they can be recovered for 30 days after deletion, only an admin can do so, and the deal returns to the stage it was in. After that window, they are permanently deleted.
That is why deletion is no way to "clean up" losses: they disappear from the analysis and from any later export. Keep it for erroneous records, duplicates already consolidated or tests, and document who authorises it. If it responds to a request to erase personal data, follow your company's data protection procedure; CallsIQ does not set out legal retention periods here.
Archive and recovery pilot
Using authorised fictitious records, note the IDs and previous outcomes. Archive a sample, find it in the archive view and compare a report with its documented filter. Also check the process that consumes the API, if there is one. Then rehearse unarchiving and verify that the pipeline and stage still exist. Do not run the test on active customer deals.
Record the differences and approve a policy before automating it. A small team can keep a periodic manual review; Pipedrive fits when this needs to be applied to a shared history. CallsIQ has not archived records in an account for this guide and does not set out legal retention obligations here.
Controlling the effect on a sales rate
A fictitious report contains 12 won and 8 lost deals: 12 / (12 + 8) = 60%. You archive 5 won deals already delivered. If the report excludes them, it shows 7 won and 8 lost: 7 / 15 = 46.67%. The sales outcome has not changed; the visible population has.
| Fictitious scenario | Visible won | Visible lost | Rate shown |
|---|---|---|---|
| Nothing archived | 12 | 8 | 60% |
| 5 won archived and excluded | 7 | 8 | 46.67% |
| 5 lost archived and excluded | 12 | 3 | 80% |
| 5 lost deleted | 12 | 3 | 80% |
The last two rows show the edge case: archiving or deleting losses "improves" the rate without selling anything more. The difference is that archived deals can be brought back with an archive-status filter, and deleted ones cannot. Before archiving, keep the filter, period and sample IDs. Afterwards, compare a view that includes both archive states. Recovering a record and recovering the meaning of a report are different checks. The rate itself is defined in the close rate guide.
Common mistakes and how to spot them
- Marking lost in bulk what only needed archiving. Symptom: the quarter's most frequent reason is "clean-up" or blank. Check: compare the lost date with the last activity.
- Exporting without archived deals. Symptom: the lost deals export has fewer rows than the known count. Check: repeat the filter in the archive tab, as explained in the guide to exporting lost deals from Pipedrive.
- An integration that stops seeing records. Symptom: an external dashboard loses deals after a bulk archive. Check: find out which endpoint it uses and whether it includes archived deals.
- Unarchiving into a deleted pipeline. Symptom: the recovered deal appears in no pipeline. Check: assign a pipeline and stage before treating it as restored.
- Deleting with no admin available. Symptom: nobody can restore an accidental deletion. Check: confirm who has restore permission before any bulk deletion.
From the author's experience
Joaquín Orozco, the author of CallsIQ, spent eleven years as a developer and implementer of contact-center software at Vocalcom, and he points out that the outcome of archiving or deleting a deal depends on how the CRM links activities to the deal and on which action is reversible: before archiving or deleting he would check whether the call history is still queryable and whether the integration keeps a valid identifier.
For a closing-by-inactivity rule, he would use an alert before any automatic close rather than closing automatically — reviewing, say, after one or two weeks of no reply depending on the sales cycle — because archiving should never replace an explicit commercial decision. He has no specific accidental bulk deletion he can describe as his own incident, but to prevent one he would require an export beforehand, tests on a subset, and permission controls around irreversible operations.
Before a bulk archive, he would first check the syncs that only query active records and the dashboards that filter by status, because an archive can make records disappear from a view without their data actually being deleted. On a report whose rate shifts after a pipeline clean-up, he won't attribute a real case without his own data; the effect, he says, can be detected by comparing the denominator's deal count before and after the clean-up, using the same cohort and reference date. And when "deals are missing," his diagnosis always starts by checking filters, permissions, archive status and date range, and only afterward investigates deletions and the audit history.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Linked sources describe the terms and capabilities each provider publishes. Examples that use fictional data are labelled in the text.
Scope: Documentation reviewed on 16 October 2026. Examples are fictional and tests are proposed; CallsIQ has not performed product tests.
- help article on archiving deals and leadssupport.pipedrive.com
- restoring deleted dealssupport.pipedrive.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
PipedriveAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.