HubSpot property history: per-record only

HubSpot's property history is per-record. Admins need it across records, and the workarounds don't cover the gap. Here's what's missing and why it matters.

Updated 3 min read

Open a deal in HubSpot, click any property's history icon, and you get a clean log: every change, timestamped, with source attribution. Useful.

Now try to answer this question: which deals had their stage changed in the last seven days, and what were they before?

There's no native report for that. Not in the standard reports library, not in custom report builder, not in workflows. Property history is locked to single-record view, one property at a time, manual.

The workarounds are all bad in similar ways.

Custom date-stamp properties is the most common one. You build a workflow that fires on property change and writes a timestamp to a separate "stage last changed" property. It works, but only forward from the moment you set it up. It captures one signal (when), not the full trail (when, from what, to what, by whom). And every property you care about needs its own workflow, its own timestamp property, its own ongoing maintenance. Multiply by ten properties across three objects and you've built a small fragile system that breaks the moment somebody renames anything.

Per-property history exports is the manual option. You can dig into individual records and screenshot or copy the change log. Fine for one-off audits. Useless when you need to see ten records' worth of behavior at once, and impossible at scale.

Last Modified Date reports give you the wrong abstraction. You can build a table report filtered by "Stage was updated in the last 7 days" and get a list of records. But you don't get the prior value, the new value, the source, or the user. Just the fact that something changed. That's enough to know there's a question to ask. It's not enough to answer the question.

This matters because the question gets asked constantly, just in different shapes. Why did our pipeline forecast jump on Tuesday. Did the new lead routing workflow misfire. Which records did the Salesforce sync touch this week. Who's been overriding deal stage manually. What did this account look like before the sales rep took it over. All of these are property change history questions, and none of them are answerable in HubSpot today without exports, spreadsheets, and an afternoon.

Property Pulse currently shows the same per-record view HubSpot does, just centralized and easier to scan on the record page. That's the foundation, not the destination. The version we're building toward surfaces tracked property changes across records: filterable by property, by date range, by source, by user. The same change log HubSpot already has, presented at the level admins actually need to operate.

If your audit question right now starts with "across all our..." and ends with property change, HubSpot doesn't have an answer. We're exploring one.

Frequently asked questions

Why doesn't HubSpot have a native across-records property change view?

HubSpot's property history is locked to single-record view, one property at a time, accessed manually by clicking the history icon on a record. There is no native report in the standard library, custom report builder, or workflows that surfaces 'which records changed property X in the last seven days, and what were the prior and new values.' The data is captured per record but is not exposed at a portfolio level.

What's wrong with custom date-stamp property workflows?

They work, but only forward from the moment you set them up. They capture one signal (when something changed), not the full trail (when, from what, to what, by whom). Each property you care about needs its own workflow, its own timestamp property, and its own ongoing maintenance. Multiply by ten properties across three objects and you have a small fragile system that breaks the moment someone renames anything.

Why does this question come up so often?

Because the same shape of question appears in different forms across operations: why did our pipeline forecast jump on Tuesday, did the new lead routing workflow misfire, which records did the Salesforce sync touch this week, who has been overriding deal stage manually, what did this account look like before the sales rep took it over. All of them are property change history questions across records, and none are answerable in HubSpot today without exports and spreadsheets.

Will Property Pulse eventually show property changes across records?

Yes, that is what we are building toward. Property Pulse currently shows the same per-record view HubSpot does, centralized into one CRM card and easier to scan. The next surface filters tracked property changes across records by property, date range, source, and user. The same change log HubSpot already has, presented at the level admins actually need to operate.