Property History Table Updates

Tuesday, August 11, 2026

Smart CRMFreeStarterProfessionalEnterprisePublic beta

What it is

The property history table on a record's side panel gets a cleaner layout, a new column structure, filtering by date range and source, search, and a direct entry point to restore property changes from the history view. Changes older than two weeks cannot be restored.

Why it matters

Until now, spotting a problematic change in property history meant leaving the record for a separate restore tool and rebuilding the same filter criteria from scratch. This lets you investigate and act in one place.

The Take

Casey Hawkins

The two-week cutoff on restores is what makes this a governance feature, not just a UI facelift.
Casey Hawkins

This was our deep dive today, and it's worth the screen time. The property history table on a record's side panel has a cleaner layout, a real column structure, filtering by source and date range, search — and, new, a direct restore entry point right there in the table. Before this, if you spotted a bad change in a record's history, you had to leave the record, go find a separate restore tool, and rebuild the same filter criteria from scratch. Now you can investigate and act without leaving the view you're already in.

The detail I actually care about: changes older than two weeks can't be restored from this view. That's not a limitation, that's the point — it's a governance guardrail, and it tells me HubSpot built this with compliance in mind, not just convenience.

There's a bigger story here than the UI. A client of mine reached out a couple of weeks ago wanting to know why someone had been set to "customer" — turned out to be a sync lifecycle stage setting, and I had to backtrack through multiple possible sources (workflow? sync setting? manual edit?) to find the real answer. Having that source data visible directly in the history table would have saved real time. And it points at something bigger: people don't engage in the CRM because they can't just Control-Z a mistake the way they can in a spreadsheet. When you make it that easy to check and fix a record's history without navigating away, you're not just shipping a UI update — you're removing a reason people avoid owning their own data in the first place.

Watch Us Discuss This

The full segment from the show, us working through this update start to finish.

Restore from the history table: Control-Z, governance, and who gets to click revert10:47

FAQ

What's actually new in the layout?

A cleaner layout, a new column structure, filtering by source and date range, search — and, new, a direct restore entry point right in the table, so you no longer have to leave the record and rebuild your filter criteria in a separate restore tool.

Is there a limit on what can be restored from this view?

Yes — changes older than two weeks cannot be restored from the property history table. That's a governance guardrail, not a bug.

Does this show me where a change actually came from?

Yes — source data is visible in the history, which is what let Casey trace a lifecycle-stage confusion back to a sync setting for a client, rather than guessing between a workflow, a sync setting, and a manual edit.

Produced by Value-First Media