[{"data":1,"prerenderedAt":59},["ShallowReactive",2],{"/en/answer-library/in-pipedrive-whats-a-practical-data-retention-and-cleanup-policy-merge-vs-delete":3,"answer-categories":36},{"id":4,"locale":5,"translationGroupId":6,"availableLocales":7,"alternates":8,"_path":9,"path":9,"question":10,"answer":11,"category":12,"tags":13,"date":15,"modified":15,"featured":16,"seo":17,"body":22,"_raw":27,"meta":29},"ae713059-15e0-4183-8507-340e87911459","en","04d81372-995a-4a35-a760-11f7db16fecd",[5],{"en":9},"/en/answer-library/in-pipedrive-whats-a-practical-data-retention-and-cleanup-policy-merge-vs-delete","In Pipedrive, what’s a practical data retention and cleanup policy (merge vs delete vs archive, and when to mark deals lost) that keeps the CRM clean without “k","## Answer\n\nA practical Pipedrive retention policy keeps real revenue history intact and removes only what creates noise. Default to marking deals Closed Lost or Closed Won rather than deleting, and use archiving for older closed work so pipelines stay usable without breaking reporting. Reserve deletion for true junk such as spam, test records, or accidental duplicates with no meaningful activity. Then run cleanup on a predictable cadence so the CRM stays clean without heroic one off projects.\n\n## Policy goals and scope (what this policy optimizes for)\nThe biggest CRM leak is not bad data, it is indecision. Open deals that should be closed, duplicates that split activity, and “cleanup” that deletes history all quietly distort forecasting and attribution.\n\nThis policy optimizes for four things.\n\nFirst, pipeline truth. Every open deal should represent a real next step and a real chance to close.\n\nSecond, reporting integrity. Conversion rates, stage performance, and source attribution should not change just because someone wanted a cleaner list view.\n\nThird, rep usability. The CRM should feel like a working board, not a storage unit.\n\nFourth, defensible retention. You should be able to explain why you kept data, why you removed data, and who approved it.\n\nScope covers Deals, Leads (if you use them), People, Organizations, and the minimum supporting data tied to those records such as activities and emails. The “source of truth” for commercial history is the deal record and its close status, close date, owner, and lost reason. If you protect those fields, you can be aggressive about reducing clutter without ruining your dashboards.\n\nPipedrive supports archiving for deals and leads, which is your best friend for keeping history while removing day to day noise. Pipedrive also provides guidance on cleaning up your account and freeing space, which is useful when you are carrying years of old items that no longer need to live in active views. See Pipedrive’s documentation on archiving and cleanup for the official mechanics and constraints: https://support.pipedrive.com/en/article/archive-deals-leads and https://support.pipedrive.com/en/article/how-can-i-free-up-space.\n\n## Classify CRM records by lifecycle state (Active, Dormant, Closed, Invalid)\nIf you only adopt one habit, make it this: every record should have a lifecycle state that tells a manager what to do next. You can implement this through conventions, views, and a small set of required fields.\n\nUse these four states.\n\nActive: A deal or contact with a next step scheduled or recent engagement. It belongs in the pipeline or active outreach lists.\n\nDormant: Real, but currently not moving. No upcoming activity and no meaningful engagement for a defined window.\n\nClosed: Won or lost. It should not remain open. It can remain visible for reporting or be archived once it is no longer operationally useful.\n\nInvalid: Spam, test data, wrong region, wrong company, or garbage created by an integration. Invalid records should be deleted quickly to avoid infecting reporting.\n\nDormant thresholds should match your sales cycle.\n\nIf you sell SMB with a 15 to 45 day cycle, dormancy often starts at 14 to 30 days of no activity.\n\nIf you sell mid market with a 60 to 120 day cycle, dormancy often starts at 30 to 60 days.\n\nIf you sell enterprise with long procurement, dormancy might start at 60 to 120 days, but you should still require a next step. “Waiting on legal” without a calendar commitment is just procrastination with better vocabulary.\n\nPractical tip: create one saved filter view per pipeline that surfaces “Open deals with no activity scheduled” and “Open deals with last activity older than X days.” This turns hygiene into a weekly routine rather than a quarterly panic.\n\n## Deal retention rules: keep, mark lost, or delete (rare)\nFor deals, the clean policy is simple: keep almost everything, close aggressively, delete almost nothing.\n\nKeep deals when they represent legitimate commercial work, even if they ended badly. Closed Lost deals are not clutter, they are your pricing intelligence, positioning feedback, and pipeline math.\n\nMark deals Closed Lost when the opportunity is no longer active, even if the door is not permanently closed. Use a lost reason like “Timing” or “Nurture” to signal you may re engage later. Leaving it open is how pipelines become museum exhibits.\n\nArchive deals when they are closed and no longer needed for daily operations, but you want to retain them for historical reporting and reference. Archiving is the healthiest way to reduce noise while keeping the data accessible when needed. Pipedrive’s archiving feature is designed for exactly this problem: https://support.pipedrive.com/en/article/archive-deals-leads.\n\nDelete deals only in rare cases.\n\n1. Test deals created during training.\n2. Spam deals created by bots or junk forms.\n3. Accidental duplicate deals where one has no meaningful activity, no notes, no emails, and no reporting value.\n\nCommon mistake: teams delete old Closed Lost deals to make conversion rates “look better” or to clean the pipeline. What to do instead is close them properly with a lost reason, then archive them once they are operationally irrelevant. Deletion makes your funnel look healthier than it is, which is like weighing yourself after taking off your shoes and calling it a fitness plan.\n\n## When to mark deals lost (timing, triggers, and stage rules)\nYour best hygiene lever is not a delete button. It is a clear definition of “this deal is no longer active.”\n\nUse three categories of triggers.\n\nFirst, explicit outcomes.\n\nIf they say no, choose a lost reason that reflects the truth: competitor, no budget, no decision, not a fit, internal priority shift.\n\nSecond, disqualification.\n\nIf you confirm they are the wrong segment, wrong geography, wrong use case, or do not meet your minimum deal criteria, mark it lost immediately with a reason like “Not a fit.” Do not let reps “keep it open just in case.” That is how you end up forecasting imaginary money.\n\nThird, inactivity with defined effort.\n\nNon response is not a stage. It is a signal that you need an outreach standard.\n\nA practical rule is “close it when you have done a reasonable, documented attempt pattern and time window for that stage.” Here is a stage based SLA that works for many teams. Adjust the days to match your cycle.\n\nNew or Qualified: mark lost after 14 to 30 days with no response after at least 5 to 7 attempts across at least two channels.\n\nDiscovery or Needs analysis: mark lost after 21 to 45 days of no response after a clear next step was proposed.\n\nProposal sent: mark lost after 21 to 45 days of no movement unless a decision date is agreed.\n\nNegotiation or Legal: mark lost after 30 to 60 days without mutual progress milestones.\n\nThe policy should require two fields before a deal can be marked lost.\n\n1. Lost reason. Make it a controlled list so reporting stays clean.\n2. Lost date. This should be the day the deal became inactive, not the day someone finally cleaned their pipeline.\n\nPractical tip: treat “Nurture” as a lost reason, not a stage. Close it as lost with “Timing” and create a follow up activity for a future date, or move the contact to a nurture status. This keeps pipeline velocity honest while preserving future upside.\n\nA note on recycling: if the same account comes back six months later, prefer creating a new deal rather than reopening an old one, unless your team explicitly tracks reopens. A new deal preserves cycle time analysis and makes attribution less confusing. If you care about linking the history, add a custom field like “Previous deal link” or “Lifecycle round” and reference the prior deal.\n\n## People/Organizations retention: delete vs keep vs archive strategy\n\n| Option | Best for | What you gain | What you risk | Choose if |\n| --- | --- | --- | --- | --- |\n| Mark Contact/Org as 'Archived' (Custom Field) | Retaining historical data without cluttering active views | Clean pipeline views. historical reporting preserved. easy to reactivate | Requires manual filtering. not a true Pipedrive archive function | You need to keep records for reporting but remove them from daily use |\n| Keep all Contacts/Orgs indefinitely | Comprehensive historical data, long sales cycles | Full historical context. no data loss | Cluttered CRM. slower performance. higher storage costs. irrelevant data | Your reporting requires every single record ever created, regardless of relevance |\n| Define a retention period for inactive Contacts/Orgs | Balancing data retention with CRM cleanliness | Manageable database size. relevant data for reps. improved performance | Requires clear policy and automation. risk of deleting useful data if not well-defined | You want to maintain a lean CRM while preserving essential historical data for a set period |\n| Set Contact/Org Status to 'Do Not Contact' | Opt-outs, legal compliance, or accounts not to be engaged | Compliance with communication preferences. prevents accidental outreach | Record remains in active views unless filtered. can be accidentally overridden | The contact is real but should not be contacted for any reason |\n| Delete Contact/Org | Spam, test data, or GDPR deletion requests | Permanently removes unwanted records. frees up space | Loss of historical data. breaks deal attribution. irreversible | The record is definitively not a real prospect/customer and has no associated deals |\n\nContacts and organizations are where teams either become hoarders or become reckless. The clean middle ground is to keep what supports revenue history and delete what is clearly invalid.\n\nUse this decision logic.\n\nKeep by default if the person or organization is tied to any legitimate deal, activity, note, or email that you want to preserve for reporting or customer context.\n\nDelete when the record is definitively invalid. That includes spam submissions, fake emails, and records created by a broken integration. Also delete when you have a legal deletion request where retention is not required.\n\nArchive strategy for contacts: Pipedrive has archiving for deals and leads, but contacts are typically managed through status, visibility, and filters rather than a true archive function. The most practical pattern is a custom field such as “Contact status” or “Lifecycle status” with values like Active, Nurture, Do Not Contact, Archived. Then build default filters so reps do not see Archived contacts in day to day lists.\n\nHere is the retention options table you can literally copy into your internal policy.\n\nMark Contact/Org as 'Archived' (Custom Field): your default for keeping history but removing clutter.\n\nDefine a retention period for inactive Contacts/Orgs: your default for staying lean without becoming reckless.\n\nSet Contact/Org Status to 'Do Not Contact': your compliance safety net for opt outs and sensitive accounts.\n\nDelete Contact/Org: your last resort for spam, test data, or legal deletion requests.\n\nIf you need a practical retention period, many teams do well with 24 to 36 months since last activity for inactive contacts, with exceptions for strategic accounts and customers. If you are space constrained, follow Pipedrive’s guidance on cleaning up to free space, but keep your reporting needs in mind before bulk deletes: https://support.pipedrive.com/en/article/how-can-i-free-up-space.\n\n## Merge vs delete decision tree (duplicates and near duplicates)\nDuplicates are expensive because they split context and create double outreach. But sloppy merging is worse because it can fuse two different humans into one Frankenstein record.\n\nUse this simple decision tree.\n\n1. Are you confident these represent the same real person or organization?\n\nIf yes, merge.\n\nIf no, do not merge. Instead, add a note, add a label like “Possible duplicate,” and let an owner verify.\n\n2. Is one record clearly junk?\n\nIf yes and it has no meaningful activity, delete the junk record.\n\nIf it has any meaningful activity, prefer merging so you retain the history.\n\n3. Choose the master record intentionally.\n\nPick the record with the most complete fields, the correct email and domain, the most recent activity, and the cleanest company name.\n\n4. Preserve attribution fields.\n\nIf you track source, UTMs, or partner referrals, decide which fields represent “original source” versus “latest source.” Do not overwrite the original source during a merge just because the newer record has a different campaign tag.\n\nPractical tip: keep a simple merge log note convention, such as “Merged duplicate on 2026 07 08 by Ops, kept email X and phone Y.” When someone asks why attribution changed, you will be glad you did.\n\n## Prevent duplicates at the source (forms, imports, integrations, naming standards)\nThe cheapest duplicate is the one you never create.\n\nMost duplicates come from three places: web forms, CSV imports, and integrations that create new contacts instead of updating existing ones.\n\nSet standards that make matching easier.\n\nRequire email for creating a person whenever possible. Email is your best unique identifier.\n\nNormalize organization naming. Use “Acme” instead of “Acme Inc.” in the name field and store legal suffixes elsewhere if you care. Consistency is what makes search and matching work.\n\nMatch organizations by domain when you can. Domains are not perfect, but they reduce “Acme” versus “Acme Corporation” drift.\n\nDuring imports, map fields consistently and dedupe before importing. If you import a list twice with slightly different columns, you will get two versions of the same reality.\n\nFor integrations, review the settings for “create new record” behavior. Your goal is to update an existing person when the email already exists, not create a new person with the same email spelled the same way but living in a parallel universe.\n\n## Reporting and attribution guardrails (so cleanup doesn’t break dashboards)\nCleanup should improve accuracy, not rewrite history.\n\nDefine a small set of fields that should be treated as immutable once the deal is created.\n\nCreated date.\n\nOwner at creation, or at least a separate “Created by” marker.\n\nPipeline and initial stage.\n\nSource fields such as lead source and UTMs, ideally split into Original source and Latest source.\n\nWon or lost date and lost reason.\n\nThe biggest reporting risk is deletion. When you delete closed deals, you reduce denominator counts and inflate conversion rates. When you delete contacts linked to deals, you can break attribution chains and make it harder to explain what drove revenue.\n\nA safer approach is to archive closed deals and leads once they age out of operational relevance, because archiving preserves data while decluttering views. Again, see Pipedrive’s archiving documentation for how it behaves in the product: https://support.pipedrive.com/en/article/archive-deals-leads.\n\n## Cadence, roles, and permissions (who does what, how often)\nHygiene works when it is boring and routine.\n\nWeekly, each rep should close or advance stale deals, schedule a next activity for every active deal, and mark dead deals as lost with a reason. Managers should review a “stale deals” view in one pipeline meeting and ask for decisions, not excuses.\n\nMonthly, Sales Ops should run three checks: percentage of open deals with no activity scheduled, completeness of lost reasons, and duplicate trends by source such as a specific form or integration.\n\nQuarterly, run a dedupe sweep and an archive sweep for old closed deals. If storage is a concern, include a review aligned with Pipedrive’s space cleanup recommendations: https://support.pipedrive.com/en/article/how-can-i-free-up-space.\n\nAnnually, review retention rules with legal and finance. Many teams keep closed deal history for 24 to 36 months in the CRM for operational use, and rely on exports or a warehouse for deeper history.\n\nPermissions matter. Limit bulk deletion rights to admins. Require manager approval for any bulk delete of contacts or deals. Give reps the power to mark lost and to merge only when they are trained, otherwise route merges through Ops.\n\n## Concrete playbooks (templates for common scenarios)\nThese are intentionally short. The goal is judgment, not bureaucracy.\n\nZombie deal closure playbook\n\nTrigger: Deal is open, no activity scheduled, and last activity is older than your dormancy threshold.\n\nSteps: Rep attempts one final outreach that references a clear decision, updates the expected close date only if a next step is agreed, otherwise marks Closed Lost.\n\nRequired fields: Lost reason “No response” or “Timing” plus a short note about attempts.\n\nOutcome: Deal is closed, and optionally a future follow up activity is created for nurture.\n\nCompetitor loss playbook\n\nTrigger: Prospect confirms they chose another vendor.\n\nSteps: Mark Closed Lost immediately, set lost reason “Competitor,” record competitor name in a note or custom field, and tag any objection theme you track.\n\nOutcome: Clean pipeline and usable win loss insights.\n\nNo response disqualification playbook\n\nTrigger: You have completed your attempt pattern and exceeded the stage SLA with no response.\n\nSteps: Mark Closed Lost with reason “No response,” add a note with the date of last attempt, and set the person status to Nurture if you plan to retry later.\n\nOutcome: Honest pipeline and a clean nurture pool.\n\nDuplicate person merge playbook\n\nTrigger: Two people share the same email, or clearly the same person with small naming differences.\n\nSteps: Choose the record with the most complete fields as master, merge, then verify that deals and activities are attached as expected.\n\nOutcome: One timeline, less confusion, less double outreach.\n\nSpam lead handling playbook\n\nTrigger: Obvious bot data, nonsense names, disposable emails, or irrelevant region.\n\nSteps: Delete if it has no legitimate activity and no reporting value. If you are uncertain, mark as Invalid via a status field first, then delete in a monthly sweep.\n\nOutcome: Cleaner database and more reliable lead metrics.\n\nRecycled lead playbook (same account returns later)\n\nTrigger: A previously lost account re engages after a meaningful gap.\n\nSteps: Create a new deal with current source, keep original deal closed, and reference the old deal in a link field or note.\n\nOutcome: Accurate cycle time and clean attribution across “rounds.”\n\nIf you change only one system choice next, make it this: enforce a rule that every open deal must have a next activity scheduled, and everything else should be closed lost or won and then archived when it ages out. That one habit keeps your pipeline real, your reporting defensible, and your CRM from turning into a digital junk drawer.\n\n### Sources\n\n- [Archive deals and leads - Knowledge Base | Pipedrive](https://support.pipedrive.com/en/article/archive-deals-leads)\n- [How can I clean up my account and free up space? - Knowledge Base | Pipedrive](https://support.pipedrive.com/en/article/how-can-i-free-up-space)\n\n---\n\n*Last updated: 2026-07-08* | *Calypso*","decision_systems_researcher",[14],"crm-data-hygiene-in-pipedrive-best-practices-for-clean-pipelines","2026-07-08T10:06:36.872Z",false,{"title":18,"description":19,"ogDescription":19,"twitterDescription":19,"canonicalPath":9,"robots":20,"schemaType":21},"In Pipedrive, what’s a practical data retention and cleanup","Policy goals and scope (what this policy optimizes for) The biggest CRM leak is not bad data, it is indecision.","index,follow","QAPage",{"toc":23,"children":25,"html":26},{"links":24},[],[],"\u003Ch2>Answer\u003C/h2>\n\u003Cp>A practical Pipedrive retention policy keeps real revenue history intact and removes only what creates noise. Default to marking deals Closed Lost or Closed Won rather than deleting, and use archiving for older closed work so pipelines stay usable without breaking reporting. Reserve deletion for true junk such as spam, test records, or accidental duplicates with no meaningful activity. Then run cleanup on a predictable cadence so the CRM stays clean without heroic one off projects.\u003C/p>\n\u003Ch2>Policy goals and scope (what this policy optimizes for)\u003C/h2>\n\u003Cp>The biggest CRM leak is not bad data, it is indecision. Open deals that should be closed, duplicates that split activity, and “cleanup” that deletes history all quietly distort forecasting and attribution.\u003C/p>\n\u003Cp>This policy optimizes for four things.\u003C/p>\n\u003Cp>First, pipeline truth. Every open deal should represent a real next step and a real chance to close.\u003C/p>\n\u003Cp>Second, reporting integrity. Conversion rates, stage performance, and source attribution should not change just because someone wanted a cleaner list view.\u003C/p>\n\u003Cp>Third, rep usability. The CRM should feel like a working board, not a storage unit.\u003C/p>\n\u003Cp>Fourth, defensible retention. You should be able to explain why you kept data, why you removed data, and who approved it.\u003C/p>\n\u003Cp>Scope covers Deals, Leads (if you use them), People, Organizations, and the minimum supporting data tied to those records such as activities and emails. The “source of truth” for commercial history is the deal record and its close status, close date, owner, and lost reason. If you protect those fields, you can be aggressive about reducing clutter without ruining your dashboards.\u003C/p>\n\u003Cp>Pipedrive supports archiving for deals and leads, which is your best friend for keeping history while removing day to day noise. Pipedrive also provides guidance on cleaning up your account and freeing space, which is useful when you are carrying years of old items that no longer need to live in active views. See Pipedrive’s documentation on archiving and cleanup for the official mechanics and constraints: \u003Ca href=\"#ref-1\" title=\"support.pipedrive.com — support.pipedrive.com\">[1]\u003C/a> and \u003Ca href=\"#ref-2\" title=\"support.pipedrive.com — support.pipedrive.com\">[2]\u003C/a>.\u003C/p>\n\u003Ch2>Classify CRM records by lifecycle state (Active, Dormant, Closed, Invalid)\u003C/h2>\n\u003Cp>If you only adopt one habit, make it this: every record should have a lifecycle state that tells a manager what to do next. You can implement this through conventions, views, and a small set of required fields.\u003C/p>\n\u003Cp>Use these four states.\u003C/p>\n\u003Cp>Active: A deal or contact with a next step scheduled or recent engagement. It belongs in the pipeline or active outreach lists.\u003C/p>\n\u003Cp>Dormant: Real, but currently not moving. No upcoming activity and no meaningful engagement for a defined window.\u003C/p>\n\u003Cp>Closed: Won or lost. It should not remain open. It can remain visible for reporting or be archived once it is no longer operationally useful.\u003C/p>\n\u003Cp>Invalid: Spam, test data, wrong region, wrong company, or garbage created by an integration. Invalid records should be deleted quickly to avoid infecting reporting.\u003C/p>\n\u003Cp>Dormant thresholds should match your sales cycle.\u003C/p>\n\u003Cp>If you sell SMB with a 15 to 45 day cycle, dormancy often starts at 14 to 30 days of no activity.\u003C/p>\n\u003Cp>If you sell mid market with a 60 to 120 day cycle, dormancy often starts at 30 to 60 days.\u003C/p>\n\u003Cp>If you sell enterprise with long procurement, dormancy might start at 60 to 120 days, but you should still require a next step. “Waiting on legal” without a calendar commitment is just procrastination with better vocabulary.\u003C/p>\n\u003Cp>Practical tip: create one saved filter view per pipeline that surfaces “Open deals with no activity scheduled” and “Open deals with last activity older than X days.” This turns hygiene into a weekly routine rather than a quarterly panic.\u003C/p>\n\u003Ch2>Deal retention rules: keep, mark lost, or delete (rare)\u003C/h2>\n\u003Cp>For deals, the clean policy is simple: keep almost everything, close aggressively, delete almost nothing.\u003C/p>\n\u003Cp>Keep deals when they represent legitimate commercial work, even if they ended badly. Closed Lost deals are not clutter, they are your pricing intelligence, positioning feedback, and pipeline math.\u003C/p>\n\u003Cp>Mark deals Closed Lost when the opportunity is no longer active, even if the door is not permanently closed. Use a lost reason like “Timing” or “Nurture” to signal you may re engage later. Leaving it open is how pipelines become museum exhibits.\u003C/p>\n\u003Cp>Archive deals when they are closed and no longer needed for daily operations, but you want to retain them for historical reporting and reference. Archiving is the healthiest way to reduce noise while keeping the data accessible when needed. Pipedrive’s archiving feature is designed for exactly this problem: \u003Ca href=\"#ref-1\" title=\"support.pipedrive.com — support.pipedrive.com\">[1]\u003C/a>.\u003C/p>\n\u003Cp>Delete deals only in rare cases.\u003C/p>\n\u003Col>\n\u003Cli>Test deals created during training.\u003C/li>\n\u003Cli>Spam deals created by bots or junk forms.\u003C/li>\n\u003Cli>Accidental duplicate deals where one has no meaningful activity, no notes, no emails, and no reporting value.\u003C/li>\n\u003C/ol>\n\u003Cp>Common mistake: teams delete old Closed Lost deals to make conversion rates “look better” or to clean the pipeline. What to do instead is close them properly with a lost reason, then archive them once they are operationally irrelevant. Deletion makes your funnel look healthier than it is, which is like weighing yourself after taking off your shoes and calling it a fitness plan.\u003C/p>\n\u003Ch2>When to mark deals lost (timing, triggers, and stage rules)\u003C/h2>\n\u003Cp>Your best hygiene lever is not a delete button. It is a clear definition of “this deal is no longer active.”\u003C/p>\n\u003Cp>Use three categories of triggers.\u003C/p>\n\u003Cp>First, explicit outcomes.\u003C/p>\n\u003Cp>If they say no, choose a lost reason that reflects the truth: competitor, no budget, no decision, not a fit, internal priority shift.\u003C/p>\n\u003Cp>Second, disqualification.\u003C/p>\n\u003Cp>If you confirm they are the wrong segment, wrong geography, wrong use case, or do not meet your minimum deal criteria, mark it lost immediately with a reason like “Not a fit.” Do not let reps “keep it open just in case.” That is how you end up forecasting imaginary money.\u003C/p>\n\u003Cp>Third, inactivity with defined effort.\u003C/p>\n\u003Cp>Non response is not a stage. It is a signal that you need an outreach standard.\u003C/p>\n\u003Cp>A practical rule is “close it when you have done a reasonable, documented attempt pattern and time window for that stage.” Here is a stage based SLA that works for many teams. Adjust the days to match your cycle.\u003C/p>\n\u003Cp>New or Qualified: mark lost after 14 to 30 days with no response after at least 5 to 7 attempts across at least two channels.\u003C/p>\n\u003Cp>Discovery or Needs analysis: mark lost after 21 to 45 days of no response after a clear next step was proposed.\u003C/p>\n\u003Cp>Proposal sent: mark lost after 21 to 45 days of no movement unless a decision date is agreed.\u003C/p>\n\u003Cp>Negotiation or Legal: mark lost after 30 to 60 days without mutual progress milestones.\u003C/p>\n\u003Cp>The policy should require two fields before a deal can be marked lost.\u003C/p>\n\u003Col>\n\u003Cli>Lost reason. Make it a controlled list so reporting stays clean.\u003C/li>\n\u003Cli>Lost date. This should be the day the deal became inactive, not the day someone finally cleaned their pipeline.\u003C/li>\n\u003C/ol>\n\u003Cp>Practical tip: treat “Nurture” as a lost reason, not a stage. Close it as lost with “Timing” and create a follow up activity for a future date, or move the contact to a nurture status. This keeps pipeline velocity honest while preserving future upside.\u003C/p>\n\u003Cp>A note on recycling: if the same account comes back six months later, prefer creating a new deal rather than reopening an old one, unless your team explicitly tracks reopens. A new deal preserves cycle time analysis and makes attribution less confusing. If you care about linking the history, add a custom field like “Previous deal link” or “Lifecycle round” and reference the prior deal.\u003C/p>\n\u003Ch2>People/Organizations retention: delete vs keep vs archive strategy\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Option\u003C/th>\n\u003Cth>Best for\u003C/th>\n\u003Cth>What you gain\u003C/th>\n\u003Cth>What you risk\u003C/th>\n\u003Cth>Choose if\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Mark Contact/Org as 'Archived' (Custom Field)\u003C/td>\n\u003Ctd>Retaining historical data without cluttering active views\u003C/td>\n\u003Ctd>Clean pipeline views. historical reporting preserved. easy to reactivate\u003C/td>\n\u003Ctd>Requires manual filtering. not a true Pipedrive archive function\u003C/td>\n\u003Ctd>You need to keep records for reporting but remove them from daily use\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Keep all Contacts/Orgs indefinitely\u003C/td>\n\u003Ctd>Comprehensive historical data, long sales cycles\u003C/td>\n\u003Ctd>Full historical context. no data loss\u003C/td>\n\u003Ctd>Cluttered CRM. slower performance. higher storage costs. irrelevant data\u003C/td>\n\u003Ctd>Your reporting requires every single record ever created, regardless of relevance\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Define a retention period for inactive Contacts/Orgs\u003C/td>\n\u003Ctd>Balancing data retention with CRM cleanliness\u003C/td>\n\u003Ctd>Manageable database size. relevant data for reps. improved performance\u003C/td>\n\u003Ctd>Requires clear policy and automation. risk of deleting useful data if not well-defined\u003C/td>\n\u003Ctd>You want to maintain a lean CRM while preserving essential historical data for a set period\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Set Contact/Org Status to 'Do Not Contact'\u003C/td>\n\u003Ctd>Opt-outs, legal compliance, or accounts not to be engaged\u003C/td>\n\u003Ctd>Compliance with communication preferences. prevents accidental outreach\u003C/td>\n\u003Ctd>Record remains in active views unless filtered. can be accidentally overridden\u003C/td>\n\u003Ctd>The contact is real but should not be contacted for any reason\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Delete Contact/Org\u003C/td>\n\u003Ctd>Spam, test data, or GDPR deletion requests\u003C/td>\n\u003Ctd>Permanently removes unwanted records. frees up space\u003C/td>\n\u003Ctd>Loss of historical data. breaks deal attribution. irreversible\u003C/td>\n\u003Ctd>The record is definitively not a real prospect/customer and has no associated deals\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>Contacts and organizations are where teams either become hoarders or become reckless. The clean middle ground is to keep what supports revenue history and delete what is clearly invalid.\u003C/p>\n\u003Cp>Use this decision logic.\u003C/p>\n\u003Cp>Keep by default if the person or organization is tied to any legitimate deal, activity, note, or email that you want to preserve for reporting or customer context.\u003C/p>\n\u003Cp>Delete when the record is definitively invalid. That includes spam submissions, fake emails, and records created by a broken integration. Also delete when you have a legal deletion request where retention is not required.\u003C/p>\n\u003Cp>Archive strategy for contacts: Pipedrive has archiving for deals and leads, but contacts are typically managed through status, visibility, and filters rather than a true archive function. The most practical pattern is a custom field such as “Contact status” or “Lifecycle status” with values like Active, Nurture, Do Not Contact, Archived. Then build default filters so reps do not see Archived contacts in day to day lists.\u003C/p>\n\u003Cp>Here is the retention options table you can literally copy into your internal policy.\u003C/p>\n\u003Cp>Mark Contact/Org as 'Archived' (Custom Field): your default for keeping history but removing clutter.\u003C/p>\n\u003Cp>Define a retention period for inactive Contacts/Orgs: your default for staying lean without becoming reckless.\u003C/p>\n\u003Cp>Set Contact/Org Status to 'Do Not Contact': your compliance safety net for opt outs and sensitive accounts.\u003C/p>\n\u003Cp>Delete Contact/Org: your last resort for spam, test data, or legal deletion requests.\u003C/p>\n\u003Cp>If you need a practical retention period, many teams do well with 24 to 36 months since last activity for inactive contacts, with exceptions for strategic accounts and customers. If you are space constrained, follow Pipedrive’s guidance on cleaning up to free space, but keep your reporting needs in mind before bulk deletes: \u003Ca href=\"#ref-2\" title=\"support.pipedrive.com — support.pipedrive.com\">[2]\u003C/a>.\u003C/p>\n\u003Ch2>Merge vs delete decision tree (duplicates and near duplicates)\u003C/h2>\n\u003Cp>Duplicates are expensive because they split context and create double outreach. But sloppy merging is worse because it can fuse two different humans into one Frankenstein record.\u003C/p>\n\u003Cp>Use this simple decision tree.\u003C/p>\n\u003Col>\n\u003Cli>Are you confident these represent the same real person or organization?\u003C/li>\n\u003C/ol>\n\u003Cp>If yes, merge.\u003C/p>\n\u003Cp>If no, do not merge. Instead, add a note, add a label like “Possible duplicate,” and let an owner verify.\u003C/p>\n\u003Col start=\"2\">\n\u003Cli>Is one record clearly junk?\u003C/li>\n\u003C/ol>\n\u003Cp>If yes and it has no meaningful activity, delete the junk record.\u003C/p>\n\u003Cp>If it has any meaningful activity, prefer merging so you retain the history.\u003C/p>\n\u003Col start=\"3\">\n\u003Cli>Choose the master record intentionally.\u003C/li>\n\u003C/ol>\n\u003Cp>Pick the record with the most complete fields, the correct email and domain, the most recent activity, and the cleanest company name.\u003C/p>\n\u003Col start=\"4\">\n\u003Cli>Preserve attribution fields.\u003C/li>\n\u003C/ol>\n\u003Cp>If you track source, UTMs, or partner referrals, decide which fields represent “original source” versus “latest source.” Do not overwrite the original source during a merge just because the newer record has a different campaign tag.\u003C/p>\n\u003Cp>Practical tip: keep a simple merge log note convention, such as “Merged duplicate on 2026 07 08 by Ops, kept email X and phone Y.” When someone asks why attribution changed, you will be glad you did.\u003C/p>\n\u003Ch2>Prevent duplicates at the source (forms, imports, integrations, naming standards)\u003C/h2>\n\u003Cp>The cheapest duplicate is the one you never create.\u003C/p>\n\u003Cp>Most duplicates come from three places: web forms, CSV imports, and integrations that create new contacts instead of updating existing ones.\u003C/p>\n\u003Cp>Set standards that make matching easier.\u003C/p>\n\u003Cp>Require email for creating a person whenever possible. Email is your best unique identifier.\u003C/p>\n\u003Cp>Normalize organization naming. Use “Acme” instead of “Acme Inc.” in the name field and store legal suffixes elsewhere if you care. Consistency is what makes search and matching work.\u003C/p>\n\u003Cp>Match organizations by domain when you can. Domains are not perfect, but they reduce “Acme” versus “Acme Corporation” drift.\u003C/p>\n\u003Cp>During imports, map fields consistently and dedupe before importing. If you import a list twice with slightly different columns, you will get two versions of the same reality.\u003C/p>\n\u003Cp>For integrations, review the settings for “create new record” behavior. Your goal is to update an existing person when the email already exists, not create a new person with the same email spelled the same way but living in a parallel universe.\u003C/p>\n\u003Ch2>Reporting and attribution guardrails (so cleanup doesn’t break dashboards)\u003C/h2>\n\u003Cp>Cleanup should improve accuracy, not rewrite history.\u003C/p>\n\u003Cp>Define a small set of fields that should be treated as immutable once the deal is created.\u003C/p>\n\u003Cp>Created date.\u003C/p>\n\u003Cp>Owner at creation, or at least a separate “Created by” marker.\u003C/p>\n\u003Cp>Pipeline and initial stage.\u003C/p>\n\u003Cp>Source fields such as lead source and UTMs, ideally split into Original source and Latest source.\u003C/p>\n\u003Cp>Won or lost date and lost reason.\u003C/p>\n\u003Cp>The biggest reporting risk is deletion. When you delete closed deals, you reduce denominator counts and inflate conversion rates. When you delete contacts linked to deals, you can break attribution chains and make it harder to explain what drove revenue.\u003C/p>\n\u003Cp>A safer approach is to archive closed deals and leads once they age out of operational relevance, because archiving preserves data while decluttering views. Again, see Pipedrive’s archiving documentation for how it behaves in the product: \u003Ca href=\"#ref-1\" title=\"support.pipedrive.com — support.pipedrive.com\">[1]\u003C/a>.\u003C/p>\n\u003Ch2>Cadence, roles, and permissions (who does what, how often)\u003C/h2>\n\u003Cp>Hygiene works when it is boring and routine.\u003C/p>\n\u003Cp>Weekly, each rep should close or advance stale deals, schedule a next activity for every active deal, and mark dead deals as lost with a reason. Managers should review a “stale deals” view in one pipeline meeting and ask for decisions, not excuses.\u003C/p>\n\u003Cp>Monthly, Sales Ops should run three checks: percentage of open deals with no activity scheduled, completeness of lost reasons, and duplicate trends by source such as a specific form or integration.\u003C/p>\n\u003Cp>Quarterly, run a dedupe sweep and an archive sweep for old closed deals. If storage is a concern, include a review aligned with Pipedrive’s space cleanup recommendations: \u003Ca href=\"#ref-2\" title=\"support.pipedrive.com — support.pipedrive.com\">[2]\u003C/a>.\u003C/p>\n\u003Cp>Annually, review retention rules with legal and finance. Many teams keep closed deal history for 24 to 36 months in the CRM for operational use, and rely on exports or a warehouse for deeper history.\u003C/p>\n\u003Cp>Permissions matter. Limit bulk deletion rights to admins. Require manager approval for any bulk delete of contacts or deals. Give reps the power to mark lost and to merge only when they are trained, otherwise route merges through Ops.\u003C/p>\n\u003Ch2>Concrete playbooks (templates for common scenarios)\u003C/h2>\n\u003Cp>These are intentionally short. The goal is judgment, not bureaucracy.\u003C/p>\n\u003Cp>Zombie deal closure playbook\u003C/p>\n\u003Cp>Trigger: Deal is open, no activity scheduled, and last activity is older than your dormancy threshold.\u003C/p>\n\u003Cp>Steps: Rep attempts one final outreach that references a clear decision, updates the expected close date only if a next step is agreed, otherwise marks Closed Lost.\u003C/p>\n\u003Cp>Required fields: Lost reason “No response” or “Timing” plus a short note about attempts.\u003C/p>\n\u003Cp>Outcome: Deal is closed, and optionally a future follow up activity is created for nurture.\u003C/p>\n\u003Cp>Competitor loss playbook\u003C/p>\n\u003Cp>Trigger: Prospect confirms they chose another vendor.\u003C/p>\n\u003Cp>Steps: Mark Closed Lost immediately, set lost reason “Competitor,” record competitor name in a note or custom field, and tag any objection theme you track.\u003C/p>\n\u003Cp>Outcome: Clean pipeline and usable win loss insights.\u003C/p>\n\u003Cp>No response disqualification playbook\u003C/p>\n\u003Cp>Trigger: You have completed your attempt pattern and exceeded the stage SLA with no response.\u003C/p>\n\u003Cp>Steps: Mark Closed Lost with reason “No response,” add a note with the date of last attempt, and set the person status to Nurture if you plan to retry later.\u003C/p>\n\u003Cp>Outcome: Honest pipeline and a clean nurture pool.\u003C/p>\n\u003Cp>Duplicate person merge playbook\u003C/p>\n\u003Cp>Trigger: Two people share the same email, or clearly the same person with small naming differences.\u003C/p>\n\u003Cp>Steps: Choose the record with the most complete fields as master, merge, then verify that deals and activities are attached as expected.\u003C/p>\n\u003Cp>Outcome: One timeline, less confusion, less double outreach.\u003C/p>\n\u003Cp>Spam lead handling playbook\u003C/p>\n\u003Cp>Trigger: Obvious bot data, nonsense names, disposable emails, or irrelevant region.\u003C/p>\n\u003Cp>Steps: Delete if it has no legitimate activity and no reporting value. If you are uncertain, mark as Invalid via a status field first, then delete in a monthly sweep.\u003C/p>\n\u003Cp>Outcome: Cleaner database and more reliable lead metrics.\u003C/p>\n\u003Cp>Recycled lead playbook (same account returns later)\u003C/p>\n\u003Cp>Trigger: A previously lost account re engages after a meaningful gap.\u003C/p>\n\u003Cp>Steps: Create a new deal with current source, keep original deal closed, and reference the old deal in a link field or note.\u003C/p>\n\u003Cp>Outcome: Accurate cycle time and clean attribution across “rounds.”\u003C/p>\n\u003Cp>If you change only one system choice next, make it this: enforce a rule that every open deal must have a next activity scheduled, and everything else should be closed lost or won and then archived when it ages out. That one habit keeps your pipeline real, your reporting defensible, and your CRM from turning into a digital junk drawer.\u003C/p>\n\u003Ch3>Sources\u003C/h3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https://support.pipedrive.com/en/article/archive-deals-leads\">Archive deals and leads - Knowledge Base | Pipedrive\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://support.pipedrive.com/en/article/how-can-i-free-up-space\">How can I clean up my account and free up space? - Knowledge Base | Pipedrive\u003C/a>\u003C/li>\n\u003C/ul>\n\u003Chr>\n\u003Cp>\u003Cem>Last updated: 2026-07-08\u003C/em> | \u003Cem>Calypso\u003C/em>\u003C/p>\n\u003Ch2>Sources\u003C/h2>\n\u003Col>\n\u003Cli>\u003Ca href=\"https://support.pipedrive.com/en/article/archive-deals-leads\">support.pipedrive.com\u003C/a> — support.pipedrive.com\u003C/li>\n\u003Cli>\u003Ca href=\"https://support.pipedrive.com/en/article/how-can-i-free-up-space\">support.pipedrive.com\u003C/a> — support.pipedrive.com\u003C/li>\n\u003C/ol>\n",{"body":28},"## Answer\n\nA practical Pipedrive retention policy keeps real revenue history intact and removes only what creates noise. Default to marking deals Closed Lost or Closed Won rather than deleting, and use archiving for older closed work so pipelines stay usable without breaking reporting. Reserve deletion for true junk such as spam, test records, or accidental duplicates with no meaningful activity. Then run cleanup on a predictable cadence so the CRM stays clean without heroic one off projects.\n\n## Policy goals and scope (what this policy optimizes for)\nThe biggest CRM leak is not bad data, it is indecision. Open deals that should be closed, duplicates that split activity, and “cleanup” that deletes history all quietly distort forecasting and attribution.\n\nThis policy optimizes for four things.\n\nFirst, pipeline truth. Every open deal should represent a real next step and a real chance to close.\n\nSecond, reporting integrity. Conversion rates, stage performance, and source attribution should not change just because someone wanted a cleaner list view.\n\nThird, rep usability. The CRM should feel like a working board, not a storage unit.\n\nFourth, defensible retention. You should be able to explain why you kept data, why you removed data, and who approved it.\n\nScope covers Deals, Leads (if you use them), People, Organizations, and the minimum supporting data tied to those records such as activities and emails. The “source of truth” for commercial history is the deal record and its close status, close date, owner, and lost reason. If you protect those fields, you can be aggressive about reducing clutter without ruining your dashboards.\n\nPipedrive supports archiving for deals and leads, which is your best friend for keeping history while removing day to day noise. Pipedrive also provides guidance on cleaning up your account and freeing space, which is useful when you are carrying years of old items that no longer need to live in active views. See Pipedrive’s documentation on archiving and cleanup for the official mechanics and constraints: [[1]](#ref-1 \"support.pipedrive.com — support.pipedrive.com\") and [[2]](#ref-2 \"support.pipedrive.com — support.pipedrive.com\").\n\n## Classify CRM records by lifecycle state (Active, Dormant, Closed, Invalid)\nIf you only adopt one habit, make it this: every record should have a lifecycle state that tells a manager what to do next. You can implement this through conventions, views, and a small set of required fields.\n\nUse these four states.\n\nActive: A deal or contact with a next step scheduled or recent engagement. It belongs in the pipeline or active outreach lists.\n\nDormant: Real, but currently not moving. No upcoming activity and no meaningful engagement for a defined window.\n\nClosed: Won or lost. It should not remain open. It can remain visible for reporting or be archived once it is no longer operationally useful.\n\nInvalid: Spam, test data, wrong region, wrong company, or garbage created by an integration. Invalid records should be deleted quickly to avoid infecting reporting.\n\nDormant thresholds should match your sales cycle.\n\nIf you sell SMB with a 15 to 45 day cycle, dormancy often starts at 14 to 30 days of no activity.\n\nIf you sell mid market with a 60 to 120 day cycle, dormancy often starts at 30 to 60 days.\n\nIf you sell enterprise with long procurement, dormancy might start at 60 to 120 days, but you should still require a next step. “Waiting on legal” without a calendar commitment is just procrastination with better vocabulary.\n\nPractical tip: create one saved filter view per pipeline that surfaces “Open deals with no activity scheduled” and “Open deals with last activity older than X days.” This turns hygiene into a weekly routine rather than a quarterly panic.\n\n## Deal retention rules: keep, mark lost, or delete (rare)\nFor deals, the clean policy is simple: keep almost everything, close aggressively, delete almost nothing.\n\nKeep deals when they represent legitimate commercial work, even if they ended badly. Closed Lost deals are not clutter, they are your pricing intelligence, positioning feedback, and pipeline math.\n\nMark deals Closed Lost when the opportunity is no longer active, even if the door is not permanently closed. Use a lost reason like “Timing” or “Nurture” to signal you may re engage later. Leaving it open is how pipelines become museum exhibits.\n\nArchive deals when they are closed and no longer needed for daily operations, but you want to retain them for historical reporting and reference. Archiving is the healthiest way to reduce noise while keeping the data accessible when needed. Pipedrive’s archiving feature is designed for exactly this problem: [[1]](#ref-1 \"support.pipedrive.com — support.pipedrive.com\").\n\nDelete deals only in rare cases.\n\n1. Test deals created during training.\n2. Spam deals created by bots or junk forms.\n3. Accidental duplicate deals where one has no meaningful activity, no notes, no emails, and no reporting value.\n\nCommon mistake: teams delete old Closed Lost deals to make conversion rates “look better” or to clean the pipeline. What to do instead is close them properly with a lost reason, then archive them once they are operationally irrelevant. Deletion makes your funnel look healthier than it is, which is like weighing yourself after taking off your shoes and calling it a fitness plan.\n\n## When to mark deals lost (timing, triggers, and stage rules)\nYour best hygiene lever is not a delete button. It is a clear definition of “this deal is no longer active.”\n\nUse three categories of triggers.\n\nFirst, explicit outcomes.\n\nIf they say no, choose a lost reason that reflects the truth: competitor, no budget, no decision, not a fit, internal priority shift.\n\nSecond, disqualification.\n\nIf you confirm they are the wrong segment, wrong geography, wrong use case, or do not meet your minimum deal criteria, mark it lost immediately with a reason like “Not a fit.” Do not let reps “keep it open just in case.” That is how you end up forecasting imaginary money.\n\nThird, inactivity with defined effort.\n\nNon response is not a stage. It is a signal that you need an outreach standard.\n\nA practical rule is “close it when you have done a reasonable, documented attempt pattern and time window for that stage.” Here is a stage based SLA that works for many teams. Adjust the days to match your cycle.\n\nNew or Qualified: mark lost after 14 to 30 days with no response after at least 5 to 7 attempts across at least two channels.\n\nDiscovery or Needs analysis: mark lost after 21 to 45 days of no response after a clear next step was proposed.\n\nProposal sent: mark lost after 21 to 45 days of no movement unless a decision date is agreed.\n\nNegotiation or Legal: mark lost after 30 to 60 days without mutual progress milestones.\n\nThe policy should require two fields before a deal can be marked lost.\n\n1. Lost reason. Make it a controlled list so reporting stays clean.\n2. Lost date. This should be the day the deal became inactive, not the day someone finally cleaned their pipeline.\n\nPractical tip: treat “Nurture” as a lost reason, not a stage. Close it as lost with “Timing” and create a follow up activity for a future date, or move the contact to a nurture status. This keeps pipeline velocity honest while preserving future upside.\n\nA note on recycling: if the same account comes back six months later, prefer creating a new deal rather than reopening an old one, unless your team explicitly tracks reopens. A new deal preserves cycle time analysis and makes attribution less confusing. If you care about linking the history, add a custom field like “Previous deal link” or “Lifecycle round” and reference the prior deal.\n\n## People/Organizations retention: delete vs keep vs archive strategy\n\n| Option | Best for | What you gain | What you risk | Choose if |\n| --- | --- | --- | --- | --- |\n| Mark Contact/Org as 'Archived' (Custom Field) | Retaining historical data without cluttering active views | Clean pipeline views. historical reporting preserved. easy to reactivate | Requires manual filtering. not a true Pipedrive archive function | You need to keep records for reporting but remove them from daily use |\n| Keep all Contacts/Orgs indefinitely | Comprehensive historical data, long sales cycles | Full historical context. no data loss | Cluttered CRM. slower performance. higher storage costs. irrelevant data | Your reporting requires every single record ever created, regardless of relevance |\n| Define a retention period for inactive Contacts/Orgs | Balancing data retention with CRM cleanliness | Manageable database size. relevant data for reps. improved performance | Requires clear policy and automation. risk of deleting useful data if not well-defined | You want to maintain a lean CRM while preserving essential historical data for a set period |\n| Set Contact/Org Status to 'Do Not Contact' | Opt-outs, legal compliance, or accounts not to be engaged | Compliance with communication preferences. prevents accidental outreach | Record remains in active views unless filtered. can be accidentally overridden | The contact is real but should not be contacted for any reason |\n| Delete Contact/Org | Spam, test data, or GDPR deletion requests | Permanently removes unwanted records. frees up space | Loss of historical data. breaks deal attribution. irreversible | The record is definitively not a real prospect/customer and has no associated deals |\n\nContacts and organizations are where teams either become hoarders or become reckless. The clean middle ground is to keep what supports revenue history and delete what is clearly invalid.\n\nUse this decision logic.\n\nKeep by default if the person or organization is tied to any legitimate deal, activity, note, or email that you want to preserve for reporting or customer context.\n\nDelete when the record is definitively invalid. That includes spam submissions, fake emails, and records created by a broken integration. Also delete when you have a legal deletion request where retention is not required.\n\nArchive strategy for contacts: Pipedrive has archiving for deals and leads, but contacts are typically managed through status, visibility, and filters rather than a true archive function. The most practical pattern is a custom field such as “Contact status” or “Lifecycle status” with values like Active, Nurture, Do Not Contact, Archived. Then build default filters so reps do not see Archived contacts in day to day lists.\n\nHere is the retention options table you can literally copy into your internal policy.\n\nMark Contact/Org as 'Archived' (Custom Field): your default for keeping history but removing clutter.\n\nDefine a retention period for inactive Contacts/Orgs: your default for staying lean without becoming reckless.\n\nSet Contact/Org Status to 'Do Not Contact': your compliance safety net for opt outs and sensitive accounts.\n\nDelete Contact/Org: your last resort for spam, test data, or legal deletion requests.\n\nIf you need a practical retention period, many teams do well with 24 to 36 months since last activity for inactive contacts, with exceptions for strategic accounts and customers. If you are space constrained, follow Pipedrive’s guidance on cleaning up to free space, but keep your reporting needs in mind before bulk deletes: [[2]](#ref-2 \"support.pipedrive.com — support.pipedrive.com\").\n\n## Merge vs delete decision tree (duplicates and near duplicates)\nDuplicates are expensive because they split context and create double outreach. But sloppy merging is worse because it can fuse two different humans into one Frankenstein record.\n\nUse this simple decision tree.\n\n1. Are you confident these represent the same real person or organization?\n\nIf yes, merge.\n\nIf no, do not merge. Instead, add a note, add a label like “Possible duplicate,” and let an owner verify.\n\n2. Is one record clearly junk?\n\nIf yes and it has no meaningful activity, delete the junk record.\n\nIf it has any meaningful activity, prefer merging so you retain the history.\n\n3. Choose the master record intentionally.\n\nPick the record with the most complete fields, the correct email and domain, the most recent activity, and the cleanest company name.\n\n4. Preserve attribution fields.\n\nIf you track source, UTMs, or partner referrals, decide which fields represent “original source” versus “latest source.” Do not overwrite the original source during a merge just because the newer record has a different campaign tag.\n\nPractical tip: keep a simple merge log note convention, such as “Merged duplicate on 2026 07 08 by Ops, kept email X and phone Y.” When someone asks why attribution changed, you will be glad you did.\n\n## Prevent duplicates at the source (forms, imports, integrations, naming standards)\nThe cheapest duplicate is the one you never create.\n\nMost duplicates come from three places: web forms, CSV imports, and integrations that create new contacts instead of updating existing ones.\n\nSet standards that make matching easier.\n\nRequire email for creating a person whenever possible. Email is your best unique identifier.\n\nNormalize organization naming. Use “Acme” instead of “Acme Inc.” in the name field and store legal suffixes elsewhere if you care. Consistency is what makes search and matching work.\n\nMatch organizations by domain when you can. Domains are not perfect, but they reduce “Acme” versus “Acme Corporation” drift.\n\nDuring imports, map fields consistently and dedupe before importing. If you import a list twice with slightly different columns, you will get two versions of the same reality.\n\nFor integrations, review the settings for “create new record” behavior. Your goal is to update an existing person when the email already exists, not create a new person with the same email spelled the same way but living in a parallel universe.\n\n## Reporting and attribution guardrails (so cleanup doesn’t break dashboards)\nCleanup should improve accuracy, not rewrite history.\n\nDefine a small set of fields that should be treated as immutable once the deal is created.\n\nCreated date.\n\nOwner at creation, or at least a separate “Created by” marker.\n\nPipeline and initial stage.\n\nSource fields such as lead source and UTMs, ideally split into Original source and Latest source.\n\nWon or lost date and lost reason.\n\nThe biggest reporting risk is deletion. When you delete closed deals, you reduce denominator counts and inflate conversion rates. When you delete contacts linked to deals, you can break attribution chains and make it harder to explain what drove revenue.\n\nA safer approach is to archive closed deals and leads once they age out of operational relevance, because archiving preserves data while decluttering views. Again, see Pipedrive’s archiving documentation for how it behaves in the product: [[1]](#ref-1 \"support.pipedrive.com — support.pipedrive.com\").\n\n## Cadence, roles, and permissions (who does what, how often)\nHygiene works when it is boring and routine.\n\nWeekly, each rep should close or advance stale deals, schedule a next activity for every active deal, and mark dead deals as lost with a reason. Managers should review a “stale deals” view in one pipeline meeting and ask for decisions, not excuses.\n\nMonthly, Sales Ops should run three checks: percentage of open deals with no activity scheduled, completeness of lost reasons, and duplicate trends by source such as a specific form or integration.\n\nQuarterly, run a dedupe sweep and an archive sweep for old closed deals. If storage is a concern, include a review aligned with Pipedrive’s space cleanup recommendations: [[2]](#ref-2 \"support.pipedrive.com — support.pipedrive.com\").\n\nAnnually, review retention rules with legal and finance. Many teams keep closed deal history for 24 to 36 months in the CRM for operational use, and rely on exports or a warehouse for deeper history.\n\nPermissions matter. Limit bulk deletion rights to admins. Require manager approval for any bulk delete of contacts or deals. Give reps the power to mark lost and to merge only when they are trained, otherwise route merges through Ops.\n\n## Concrete playbooks (templates for common scenarios)\nThese are intentionally short. The goal is judgment, not bureaucracy.\n\nZombie deal closure playbook\n\nTrigger: Deal is open, no activity scheduled, and last activity is older than your dormancy threshold.\n\nSteps: Rep attempts one final outreach that references a clear decision, updates the expected close date only if a next step is agreed, otherwise marks Closed Lost.\n\nRequired fields: Lost reason “No response” or “Timing” plus a short note about attempts.\n\nOutcome: Deal is closed, and optionally a future follow up activity is created for nurture.\n\nCompetitor loss playbook\n\nTrigger: Prospect confirms they chose another vendor.\n\nSteps: Mark Closed Lost immediately, set lost reason “Competitor,” record competitor name in a note or custom field, and tag any objection theme you track.\n\nOutcome: Clean pipeline and usable win loss insights.\n\nNo response disqualification playbook\n\nTrigger: You have completed your attempt pattern and exceeded the stage SLA with no response.\n\nSteps: Mark Closed Lost with reason “No response,” add a note with the date of last attempt, and set the person status to Nurture if you plan to retry later.\n\nOutcome: Honest pipeline and a clean nurture pool.\n\nDuplicate person merge playbook\n\nTrigger: Two people share the same email, or clearly the same person with small naming differences.\n\nSteps: Choose the record with the most complete fields as master, merge, then verify that deals and activities are attached as expected.\n\nOutcome: One timeline, less confusion, less double outreach.\n\nSpam lead handling playbook\n\nTrigger: Obvious bot data, nonsense names, disposable emails, or irrelevant region.\n\nSteps: Delete if it has no legitimate activity and no reporting value. If you are uncertain, mark as Invalid via a status field first, then delete in a monthly sweep.\n\nOutcome: Cleaner database and more reliable lead metrics.\n\nRecycled lead playbook (same account returns later)\n\nTrigger: A previously lost account re engages after a meaningful gap.\n\nSteps: Create a new deal with current source, keep original deal closed, and reference the old deal in a link field or note.\n\nOutcome: Accurate cycle time and clean attribution across “rounds.”\n\nIf you change only one system choice next, make it this: enforce a rule that every open deal must have a next activity scheduled, and everything else should be closed lost or won and then archived when it ages out. That one habit keeps your pipeline real, your reporting defensible, and your CRM from turning into a digital junk drawer.\n\n### Sources\n\n- [Archive deals and leads - Knowledge Base | Pipedrive](https://support.pipedrive.com/en/article/archive-deals-leads)\n- [How can I clean up my account and free up space? - Knowledge Base | Pipedrive](https://support.pipedrive.com/en/article/how-can-i-free-up-space)\n\n---\n\n*Last updated: 2026-07-08* | *Calypso*\n\n## Sources\n\n1. [support.pipedrive.com](https://support.pipedrive.com/en/article/archive-deals-leads) — support.pipedrive.com\n2. [support.pipedrive.com](https://support.pipedrive.com/en/article/how-can-i-free-up-space) — support.pipedrive.com\n",{"date":15,"authors":30},[31],{"name":32,"description":33,"avatar":34},"Mateo Rojas","Calypso AI · Lead quality, follow-up timing, qualification judgment, and conversion advice",{"src":35},"https://api.dicebear.com/9.x/personas/svg?seed=calypso_revenue_strategy_advisor_v1&backgroundColor=b6e3f4,c0aede,d1d4f9,ffd5dc,ffdfbf",[37,40,44,48,52,55],{"slug":38,"name":38,"description":39},"support_systems_architect","These topics should stay grounded in real support workflow design, escalation logic, routing, SLAs, handoffs, and the messy reality of serving customers when volume spikes and patience drops.\n\nWrite like someone who has watched support automation fail at the escalation layer, seen teams confuse a chatbot with a support system, and knows exactly which shortcuts create rework later. Keep it useful and engaging: practical tips, failure-mode awareness, a touch of humor, and SEO angles tied to real operational questions support leaders actually search for.\n\nPriority storylines:\n- What support leaders should fix first when volume jumps and quality slips\n- When to route, resolve, escalate, or hand off without losing the thread\n- How to balance speed and quality when customers demand both at once\n- Where duplicate threads and fuzzy ownership start making support feel blind\n- What branch teams should watch besides ticket counts\n- Which warning signs show up before a support mess becomes obvious",{"slug":41,"name":42,"description":43},"revenue_workflow_strategist","Lead capture, qualification, and conversion systems","These topics should stay authoritative on lead capture, qualification, routing, scheduling, follow-up, and the awkward little leaks that quietly kill pipeline before sales blames marketing.\n\nWrite like a revenue operator who has seen junk leads flood inboxes, 'fast response' turn into low-quality chaos, and automations help only when the logic is brutally clear. The tone should be expert, practical, slightly opinionated, and engaging enough that readers feel guided instead of lectured. Strong SEO should come from high-intent workflow questions, not generic funnel chatter.\n\nPriority storylines:\n- Which inquiries deserve real energy and which ones need a graceful filter\n- What makes fast follow-up feel useful instead of chaotic\n- How teams route urgency, fit, and buying stage without turning ops into a maze\n- Where WhatsApp lead capture helps and where it quietly creates junk\n- What to automate first when the pipeline is leaking in five places at once\n- Why shared context often converts better than simply replying faster",{"slug":45,"name":46,"description":47},"conversational_infrastructure_operator","Messaging infrastructure and workflow reliability","These topics should sound grounded in real messaging operations that have already lived through retries, duplicates, broken handoffs, and the 2 a.m. dashboard panic nobody wants to repeat.\n\nWrite for operators and leaders who need reliability without being buried in infrastructure jargon. Keep the tone practical, confident, and human: tips that save time, common mistakes that quietly wreck reporting, and the occasional line that makes the pain feel familiar instead of robotic. Strong SEO angles should still be specific and high-intent.\n\nPriority storylines:\n- When branch numbers start looking better than the customer experience feels\n- How teams keep context intact when conversations move across people and channels\n- What leaders should fix first when messaging operations start feeling messy\n- Where duplicate activity quietly distorts dashboards and confidence\n- Which habits restore trust faster than another round of heroic firefighting\n- What 'ready for real volume' looks like when you strip away the swagger",{"slug":49,"name":50,"description":51},"growth_experimentation_architect","Growth systems, lifecycle messaging, and experimentation","These topics should show a sharp understanding of activation, retention, re-engagement, lifecycle messaging, and growth experimentation without slipping into generic personalization talk.\n\nWrite like someone who has seen onboarding flows underperform, win-back campaigns overstay their welcome, and A/B tests prove something useless with great confidence. Make it engaging, specific, and commercially smart: practical tips, what people get wrong, tasteful humor, and search-friendly angles that map to real buyer/operator intent.\n\nPriority storylines:\n- What an honest first-win moment in activation actually looks like\n- How re-engagement can feel timely instead of clingy\n- When trigger-first thinking helps and when segment-first wins\n- Which experiments deserve attention and which are just theater\n- How shared context changes retention more than one more campaign\n- What growth teams usually notice too late in lifecycle messaging",{"slug":12,"name":53,"description":54},"Research, signal design, and decision systems","These topics should turn messy signals, conversations, and branch-level events into trustworthy decisions without sounding academic or technical for the sake of it.\n\nWrite like an experienced advisor who knows that bad data usually looks fine right up until a team makes a confident wrong decision. Bring judgment, practical tips, and a little wit. The reader should leave with sharper instincts about what to trust, what to measure, and what usually goes wrong first. Keep the SEO intent strong by favoring concrete, decision-shaped subtopics over abstract thought leadership.\n\nPriority storylines:\n- Which branch numbers deserve trust and which are just polished noise\n- How to spot dirty signal before a confident meeting goes off the rails\n- When leaders should trust automation and when they still need human judgment\n- How to turn messy evidence into usable insight without cleaning away the truth\n- What teams repeatedly misread when comparing branches, conversations, and attribution\n- How to build a signal culture that helps decisions happen, not just slides",{"slug":56,"name":57,"description":58},"vertical_operations_strategist","Industry-specific authority topics","These topics should map cleanly to how each industry actually operates and feel unusually credible inside real operating environments, not generic across sectors.\n\nWrite like a strategist who understands that clinics, retail, real estate, education, logistics, professional services, and fintech each break in their own charming way. Keep the voice expert, practical, and engaging, with field-tested tips, sharp tradeoffs, and examples that feel rooted in how teams actually work. SEO should come from highly specific, industry-shaped searches with clear workflow intent.\n\nPriority storylines by vertical:\n- Clinics: what keeps schedules moving when patients refuse to behave like calendars\n- Retail: how teams stay calm when demand spikes and patience disappears\n- Real estate: what serious follow-up looks like after the first inquiry\n- Education: how admissions feels smoother when reminders and handoffs stop fighting each other\n- Professional services: how intake and approvals stay clear when requests get messy\n- Logistics and fintech: what keeps urgent cases controlled without slowing the business",1785947678818]