Opportunity field history is the CRM audit log of changes to fields on a deal record. Each entry names the field, the old value, the new value, the user, and the timestamp. The current record tells you what a deal is. The history tells you what it has been doing, which is where nearly every useful pipeline signal lives.
Track the three fields that define movement
ORM defines meaningful activity on an opportunity as a change in stage, close date, or amount. That definition is worth adopting directly, because it draws a clean line between a deal that is progressing and a deal that is merely open.
Stage changes give you time in stage and stage-to-stage conversion. Close date changes give you push counts. Amount changes give you the revision pattern that shows whether deals get discounted on the way to signature or inflated on the way in. Salesforce caps tracked fields per object, so spend the allocation on these before adding anything else.
The change log beats the snapshot
A pipeline report shows the state of every open deal right now. It cannot distinguish a $200,000 opportunity created last week from a $200,000 opportunity that has been pushed out of three consecutive quarters. Both sit in the same stage with the same amount and the same close date inside the period.
Field history separates them in one query. That separation matters because ORM identifies a rep changing the close date as the strongest available signal of deal slippage. A deal that slips from one quarter to the next is less likely to close even when it sits in commit. You cannot detect that pattern from a snapshot, only from the log.
Absence of change is also a reading
The earliest warning on a deal is the lack of any signal at all. No stage movement, no date revision, no amount edit, no notes. ORM calls this out as the first indicator that shows up, earlier than the close date push, because a rep who is still working a deal generates changes and a rep who has quietly given up does not.
This is why aged pipeline is measurable rather than anecdotal. In ORM's customer base, more than 10% of pipeline has not been touched in twelve months. Field history is how you find that 10% instead of guessing at it, and removing it is one of the fastest corrections available to a distorted pipeline coverage number.
Get the history out of the CRM
Retention limits mean the log ages out before it becomes most valuable. Export tracked-field changes on a schedule into a warehouse, then replay them to reconstruct the daily state of every opportunity. With that reconstruction you can answer questions the CRM cannot: what the pipeline looked like on day one of a closed quarter, how much of it converted, and which cohorts of deals slipped together.
That reconstructed history is also the training input for any model that predicts close timing, and it is the foundation any serious approach to forecast accuracy has to sit on.
Frequently Asked Questions
What is opportunity field history?
It is the audit trail your CRM keeps for tracked fields on an opportunity. Each entry records the field, the old value, the new value, the user who made the change, and the timestamp. Salesforce calls it Field History Tracking and limits it to a fixed number of fields per object, so choosing which fields to track is a real decision.
Which opportunity fields should you track?
Stage, close date, and amount cover most analytical needs. ORM defines meaningful activity on a deal as a change to one of those three, so tracking them gives you the exact signal that separates a moving deal from a dormant one. Owner and forecast category are worth adding if reassignment or category overrides are common on your team.
Why does field history matter for forecasting?
A snapshot of the pipeline tells you where deals are. Field history tells you how they got there and how fast. Time in stage, push counts, and amount revisions all come from the change log rather than the current record. Without it, a deal pushed four times and a deal created yesterday look identical in a pipeline report.
How long is field history retained?
Retention is capped in most CRMs, and older entries age out of the standard object. Teams that want multi-year trend analysis export the history on a schedule into a warehouse and rebuild the daily state of every opportunity from it. That reconstructed history is what makes cohort-level cycle and slippage analysis possible.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like opportunity field history into prescriptive action for your team.
Schedule a Demo