Somebody changed the amount on your biggest open deal. The forecast call is in an hour, the rep says they didn’t touch it, and the HubSpot record shows a number nobody remembers agreeing to. Three questions follow fast: who changed it, what was it before, and can you put it back?
HubSpot answers all of them, with three different tools, and each tool has a limit that decides what you get. Record property history shows who or what changed a value and when. The property history export hands you the past values as a file. The restore tool rolls records back, but only within 14 days. And the history itself has a ceiling: a deal property keeps up to 20 revisions, a contact property up to 45.
Learn which tool answers which question before the forecast call, not during it.
How do you see who changed a property in HubSpot?
Open the record, click Actions in the upper right of the left sidebar and select View property history. HubSpot’s Knowledge Base page “View record property history“ (last updated October 16, 2026) says the panel shows past values for all of the record’s properties, the date and time of each change and its source, and lets you search by property name or change source and filter by property, source or date.
The source column is where the answer lives: a user, an import, a workflow, an integration. If a custom agent made the change, HubSpot shows the agent’s name as a link, plus who created the agent. If you’ve given AI agents write access to your CRM, that line is how you tell their edits from your reps’ (more on agent write access).
The same panel has a restore option. Hover over a row, click Restore, then click Restore all changes from this source. HubSpot files this under restoring an individual property value, but the button you click says “all changes from this source,” so read the row before you click it. And the option isn’t on every row. Per the same page, it only appears when the source is a CRM UI edit, an import or a workflow.
How much history does HubSpot keep?
HubSpot caps the revisions it saves for each property, by object. HubSpot’s Knowledge Base page “Export property history“ (last updated September 8, 2026) says contact properties keep up to 45 revisions and company, deal, ticket and custom object properties keep up to 20, counting changes made in HubSpot and through the API. The restore tool reaches back 14 days, and an actioned restore stays in Restore History for 90 days, per “Restore CRM changes“ (October 13, 2026).
HubSpot’s history is limited on both ends.
Sources: HubSpot Knowledge Base: Export property history, 2026; HubSpot Knowledge Base: Restore CRM changes, 2026
| Figure | Label |
|---|---|
| 45 | revisions kept for each contact property |
| 20 | revisions for each deal or company property |
| 14 days | the restore tool reaches back |
| 90 days | an actioned restore stays in Restore History |
HubSpot’s history is limited on both ends: a count of revisions per property, and a 14-day window to roll back.
The count is the one that sneaks up on you. A deal property that reps, workflows and integrations all write to spends its 20 revisions faster than a field one person edits by hand, and API changes count too. Close date is the obvious case, because every push is a revision (how to count close date pushes in HubSpot). HubSpot’s page doesn’t say what happens to revisions past the limit. So don’t plan next year’s audit around history you haven’t checked is still there.
Three ways to put a value back
Each tool reaches a different distance and undoes different sources. Side by side, from the three HubSpot pages above:
| Tool | Reaches back | Who can use it | What it can undo | Best for |
|---|---|---|---|---|
| Row restore in property history | As far as the property’s saved revisions go (45 for contacts, 20 for deals, companies, tickets and custom objects) | HubSpot’s page doesn’t list a permission | Changes from a CRM UI edit, an import or a workflow | One wrong value on one record |
| Property history export | The same revision limits | Users with CRM Export and the Edit All permission for that object, on all products and plans | Nothing directly: the file holds past values, and with Include Source Information, who or what set each one | Changes older than 14 days, or a record you want on file |
| Restore tool | Up to 14 days | Super Admins | Changes by source (CRM changes, Import, Integration or Workflow), down to a named import, integration or workflow | One bad import, integration or workflow run across many records |
Two details on the export from HubSpot’s page: it includes only records that had or have a value for the property, and its change dates are in UTC. The download link arrives by email and in your notification center. On the restore tool, a prepared restore stays available to action for up to 14 days.
The gap worth knowing is the integration. The row restore lists CRM UI edits, imports and workflows. The restore tool also lists Integration. So if a sync overwrote deal amounts last Tuesday, the restore tool is your way back, and you have 14 days to use it (two-CRM sync duplicates).
The verdict, by situation:
- Under 14 days, one known import, integration or workflow: roll it back with the restore tool, filtered to that source and its name.
- Older than 14 days: work from the property history export.
- One wrong value on one record, with Restore showing on the row: use the row restore.
- An integration’s change on one record: the row won’t offer Restore, so use the restore tool inside 14 days or the export after.
The audit routine
Run it in this order the next time a value looks wrong, before anyone edits the record by hand and adds another revision to the pile.
- Open the record’s property history and filter by the property and the date range in question.
- Read the source of each change: a user, an import, a workflow, an integration or an agent.
- If the bad change came from one import, integration or workflow and is under 14 days old, open the restore tool and select that source and its name.
- If it’s older, export the property’s history with Include Source Information checked, convert the UTC dates to your time zone, and rebuild the right values from the file.
- Write down which source caused it, so whoever owns that import, workflow or integration corrects it before it runs again.
Don’t skip step 5. The restore puts the value back. The workflow that wrote the bad value runs again tomorrow.
Which deal fields should you snapshot before the history runs out?
Close date, amount, deal stage and deal owner are the fields that explain how a quarter slipped, and each can change many times on a single deal. Twenty revisions may not cover a long sales cycle with weekly pipeline reviews.
Build the habit with a tool you already have: export the property history for those four fields on a schedule you’ll keep (monthly, or before each board meeting), with source information included, and store the files somewhere your team can find them. Pick the schedule based on how often those fields change in your portal, not on a number from a blog post.
The source column tells you which system wrote a value. It doesn’t tell you why a rep typed it (why good reps enter bad data). And if your HubSpot reports already disagree with each other, a property history you can’t see makes the reason harder to trace (why HubSpot reports don’t match).
Trust the history, or keep your own
You can trust the record’s history to be there when someone asks who moved the close date in March, or you can export the fields that matter on a schedule and stop hoping. HubSpot gives you both options. Only one of them doesn’t depend on a revision limit you haven’t checked.
Reading one record’s history is manageable. Seeing which imports, workflows and integrations keep rewriting the same fields across your whole portal is where it gets harder. AeolusGTM is CRM, RevOps and GTM advisory, with Atlas connecting to your CRM to find gaps the CRM can’t show natively. For a starting read on your own setup, run the free HubSpot audit tool.
This week, open property history on your largest open deal, filter to Close date and Amount, and count how many of the 20 revisions each one has already used.