
Pipeline Design
Part of CRM maintenance and replacement
Archiving old opportunities without losing history
Choose which old opportunities leave active work, check the CRM's archive behaviour and verify that useful history remains findable.
Archive an opportunity when it no longer belongs in active sales work and its outcome, customer links and useful history remain retrievable. If the CRM has no suitable deal archive, a closed status and a filtered active view may clear the workspace without changing the record's retention or editing rules.
Decide which deals leave active work
Select a proposed group, such as completed won deals or lost deals with no current follow-up. Review open deals against the team's rule before hiding them.
A customer-requested pause with a credible decision path, owner and review point may still be active. A deal with no current purchase decision needs an agreed outcome or a review decision; age alone does not supply one.
Before changing a deal, check its actual outcome, customer and contact links, any open commitment and how a colleague will find it later. Keep a source ID or other reference that distinguishes it from another opportunity for the same customer. Retain personal information only for an approved purpose under the organisation's rules.
Check what the CRM means by archive
Pipedrive's deal archive removes a deal from most active and pipeline views while retaining its open, won or lost status. Archived deals are accessible throughout Pipedrive, including from the Archive tab, search and linked locations.
Archived Pipedrive deals retain their previous status. Emails and notes are allowed, but new activities cannot be linked to an archived deal. The FAQ says archived leads can be hidden from filters and standard API endpoints. Archiving or unarchiving may trigger configured automations or webhooks.
If an archived Pipedrive deal is unarchived after its former pipeline or stage has been removed, it will not appear in a pipeline until both are assigned. Include retrieval, integration and return-to-work checks in the archive rule.
HubSpot documents filters and saved views for deals. A view limited to current work can reduce clutter while leaving closed records in the CRM. Treat that as a display choice, not as an archive with Pipedrive's restrictions. Check the behaviour of any other CRM before applying the word “archive”.
Pipedrive vs HubSpot: Archive behaviour for closed deals
- Visibility in active pipeline viewsRemoved (Pipedrive), Hidden via filters (HubSpot)
- Access to archived recordsAvailable via Archive tab, search and linked locations (Pipedrive), Accessible via saved views (HubSpot)
- New activities allowedNot allowed (Pipedrive), Depends on view settings (HubSpot)
- Impact on automations/webhooksMay trigger (Pipedrive), Not specified (HubSpot)
Verify a small change before expanding it
Choose a won deal, a lost deal and an awkward open case. Record where each should appear in active views, historical searches and reports.
Apply the proposed method through the organisation's approved route, then have an ordinary user inspect the result. Check the links and history needed to understand the customer outcome. Confirm report populations explicitly if archived deals should still count.
For a bulk action, retain the selected deal IDs, prior states, decision owner and exceptions. Recheck representative records afterwards. A completed bulk action does not establish that every relationship remains useful.
For Australian organisations subject to the Australian Privacy Principles, archiving does not settle retention. APP 11 requires reasonable steps to destroy or de-identify personal information no longer needed for a permitted purpose, subject to its exceptions. Consider old notes, attachments and archived copies as well as the deal status.
Australian Privacy Principle compliance: Archiving and data retention
- APP 11 requirement
- Reasonable steps to destroy or de-identify personal information no longer needed
- Applies to archived records
- Yes – includes notes, attachments and copies
- Retention not automatically satisfied by archiving
- Correct – archiving ≠ deletion or de-identification



