How to Archive Stale Opportunities in Your CRM Without Losing the History

What actually counts as a stale opportunity?

An opportunity is stale when nothing meaningful has changed on it, and meaningful means a change to stage, close date, or amount. Any definition based on logged activity will fail, because logged activity is the easiest thing in a CRM to manufacture.

This distinction is the whole game. A deal with a weekly automated sequence and a monthly logged call can look active for a year while the buyer has gone silent. A deal with no logged activity but a stage change and a revised amount last month is genuinely moving. Activity counts measure rep behavior. Field changes measure deal progress.

At ORM we use a twelve month rule with most customers, and across those customers ten percent or more of open pipeline has not been touched in twelve months. That is untouched by the field-change definition, which is why it surprises teams whose activity dashboards look healthy.

How do you build an opportunity aging report?

Rank open opportunities by days since the last meaningful field change, and use that list rather than a stage report as your review agenda. Stage tells you where a deal is. Age tells you whether it is alive.

Build three columns beyond the standard opportunity fields: days since last stage change, days since last close date change, and days since last amount change. Take the minimum of the three as the age. Then bucket.

The thresholds should reflect your own sales cycle rather than these defaults. Pull the distribution of days-to-close on your closed-won deals from the last two years and set the buckets against it. A business whose deals almost never take longer than six months should not be carrying a twelve month tolerance.

Worth knowing what the underlying distribution tends to look like. Deal groups have close curves that run anywhere from one to eighty weeks, with most of the expectation concentrated before week twelve. Very few groups carry meaningful close expectation past fifty-two weeks. That shape is why a twelve month rule holds up as a default even though the right number varies.

What is the right archive process?

Close the record with a reason, never delete it, and keep the archive decision reversible for one cycle. Deletion destroys the history that every conversion and cycle time calculation runs on.

Run the process in four steps.

1. Snapshot first. Export open pipeline by stage, owner, and amount before any changes. This is your reconciliation baseline and your evidence when someone asks where the coverage went. 2. Distribute by owner. Send each rep only their own aged deals. Give a deadline, typically one week. 3. Force a decision per record. Three options: revive with a documented customer commitment, close-lost with a reason code, or move to a nurture bucket that does not count as forecast coverage. 4. Bulk close the remainder. Anything with no decision by the deadline closes with a standard reason such as no activity, applied as a tagged batch.

The tag on the batch matters. Six months later when someone asks why win rate dropped in that period, the tag is the answer. An untagged bulk close looks like a real performance event forever.

Why does the nurture bucket matter so much?

Reps resist closing deals they believe will return, and without a third option they defend stale records instead of clearing them. The nurture bucket removes the reason to argue.

Set it up as a stage or a flag that is excluded from all forecast and coverage reporting. Every record in it carries an owner and a review date. Nothing sits there without a date.

Two rules keep it from becoming a landfill. Records get reviewed on their date or they close automatically. The bucket has a reported size, published monthly, so it cannot grow quietly. A nurture bucket that nobody measures becomes the new stale pipeline within three quarters.

How does stale pipeline distort the numbers you report?

Stale deals inflate coverage and depress conversion rates at the same time, which makes both metrics unreadable. The two errors run in opposite directions, so a summary view looks plausible while both inputs are wrong.

Coverage is the more dangerous of the two. A team reporting comfortable coverage may be carrying a meaningful share of it in records nobody has touched in a year. Across ORM customers most sit near 3.5x coverage, and a coverage number that includes year-old records is describing your CRM rather than your quarter. This is one of several reasons the 3x to 5x coverage rule fails as a health check, and why pipeline coverage should be read only after an aging pass.

Conversion math suffers differently. Stale open records sit in the denominator of stage conversion rates forever without ever resolving, which suppresses every rate you calculate. Reported win rate stays artificially low until the cleanup, then jumps, and neither number reflects how the team is actually selling.

What keeps stale pipeline from rebuilding?

Automate the aging flag and put it in a meeting people already attend. A one-time archive project regrows within a year without a standing mechanism.

Three controls hold the line.

An automated age field. Calculate days since last meaningful change on every open opportunity, updated nightly. Put it on the opportunity page layout so reps see it on the record rather than in a report. A stage gate at the aging threshold. Deals past your mid-tier threshold require a next step with a future date to remain open. This is a validation rule, not a policy reminder. Aging in the forecast pack. Report aged pipeline as a share of total coverage every week. Once the number is visible next to the coverage ratio, it stops being ignorable.

The reason to do all of this is timing rather than tidiness. A forecast built on aged records tells you the quarter is fine until the last few weeks, and getting the number right in the final week of the quarter helps nobody because the quarter already happened. Clearing stale pipeline is what makes a week one read on the quarter worth anything, which is the whole point of forecasting revenue rather than reporting it.