A CRM snapshot tells you the current value of a deal’s properties. A deal-history collection can show earlier stages, activities and recorded reasons for change. Those are different scopes. Begin with the deal ID, then identify which properties have saved history and which activities or documents can be linked to that deal.
A current stage is not the path to that stage
Fictional deal D-41 is currently won. Its retained events might show discovery, proposal, review, a return to proposal and final acceptance. Without those events, the current row does not establish the sequence.
Separate property changes from activities. A stage change records one kind of event; a call note or approval can explain context. A complete activity list does not necessarily contain the earlier values of every property.
| Collection layer | Example to inspect | Question answered |
|---|---|---|
| Snapshot | Current stage and value | What is recorded now? |
| Property history | Stage change dates | What values changed? |
| Activity | Call, email or task linked to D-41 | What interaction was recorded? |
| Reason | Recorded explanation | Why was the change made? |
| Related document | Quote or agreement reference | What scope was discussed? |
Keep the persistent identity
A company can have several deals with similar names. Preserve the original deal ID and its associations to accounts, contacts and documents. If a migration created new IDs, record whether a cross-reference survives rather than joining on deal title alone.
Inspect a deal that moved backward
A deal returned from review to proposal is a useful test. Can you locate the stage changes, the activity that explains the change and the revised quote? If the events exist but the reason does not, describe stage history without recorded rationale.
Do not convert a salesperson’s later recollection into an original event. It can be an explanation for your own preparation, but it is a different evidence type from a contemporaneous record.
Check the history route separately from record export
Vendor guidance can distinguish current record exports from property history and other related records. The system guides explain the relevant official routes. Your inventory should say which route was inspected and which fields survived, rather than calling every CRM download a full history.
- Deal ID and account association
- Property names and saved change events
- Activity-to-deal references
- Recorded reasons or approval notes
- Quote/document version references
- Observed history and migration gaps
Keep deleted or merged identities as questions
A merge can move relationships onto a surviving record while older exports retain another ID. Record any available merge or migration reference. If the link is not known, keep the earlier and later groups separate. Reusing the current deal name as a historical key can make unrelated records appear connected.
Name the collection accurately
Current deals with associated activities, selected property history, and full deal lifecycle are different descriptions. Choose the narrowest one your inspection supports, then use the provider matrix to ask about that actual collection.
Questions about this comparison
Can we infer past stages from the current deal row?
No. Saved change events or another retained record are needed.
Does an activity export contain property history?
Do not assume so. Inspect the export route and fields separately.
What if deal names changed?
Use persistent IDs where available and preserve any migration or rename references.