A current HubSpot record and its saved property history answer different questions. Inventory the current object, the changes you can retrieve, the activities and the associations separately. That makes it possible to describe a deal or support lifecycle without assuming a record export contains every earlier value and interaction.
The documented history route
HubSpot provides a separate property-history export, including an option for source information. Saved revision limits vary by object, and exported change dates use UTC. Treat the available history as a bounded record group, not an unlimited reconstruction of every past value.
Sources: HubSpot
Keep each object and association visible
Fictional deal D-41 is associated with company CO-8 and contacts CT-2 and CT-7. Activity A-14 concerns the deal. A property-history file refers to D-41 and a particular property. The relationship is clearer when the inventory preserves those identities instead of flattening every associated value into one row.
The same contact can be associated with several deals, and a company can have several open processes. A shared contact or company name is not enough to assign every activity to one deal.
| Group | Reference to inspect | Question answered |
|---|---|---|
| Current deal | Record ID | What is recorded now? |
| Property history | Record ID and property | Which saved values changed? |
| Activity | Activity ID and associations | What interaction is retained? |
| Company/contact | Object IDs and associations | Who or what was involved? |
| Related file | File or URL reference | Which supporting content survives? |
Inspect a change and its recorded source
Choose a property that changed during a known deal event. Compare the history dates with a related activity and note the time convention. A source label can help identify how the value changed, but it does not necessarily explain the business reason. Keep the reason as a separate question.
Do not overstate the older period
A record created years ago may have only a bounded set of saved revisions. The creation date therefore does not establish continuous property history. Describe the actual earliest and latest changes observed for the selected properties.
If the company migrated into HubSpot, distinguish imported values from events originally recorded there. An imported stage history may have a different structure or provenance from native changes. Preserve the migration references if they survive.
Keep exported history unchanged
Preserve the original history file and time convention before preparing a comparison. A later reformatted worksheet should remain distinguishable from the source output.
Build the HubSpot inventory card
Name the objects and properties inspected, their observed history and the associations used to connect them. Then add the relevant buyer-interest question. A provider’s CRM category does not certify that every property or association is in scope.
- Object type and Record ID
- Selected properties and observed revisions
- UTC dates kept with their original meaning
- Source information where available
- Activities and association level
- Imported history and unresolved file references
Questions about this comparison
Is a current record export the same as property history?
No. They answer different questions and should be inventoried separately.
Does the record creation date establish all earlier changes?
No. Inspect the retained revisions for the selected properties.
Does source information explain why a deal changed?
It may identify the source of the update. The business reason needs its own recorded evidence.
Sources
- Export property historyHubSpot · Checked 2026-10-06