Skip to content
Book a build

How do I export property history in HubSpot?

To export property history in HubSpot, go to Settings > Properties, choose the object, hover over the property, click More and select Export property history. Pick a file format, optionally include the user or tool behind each change, and export. HubSpot keeps up to 45 revisions for contact properties and 20 for companies, deals, tickets and custom objects.

On this page

What HubSpot supports natively

TopicWhat HubSpot says
AvailabilityAll products and plans
PermissionsEdit All permission for the object, plus CRM export permission
ObjectsContacts, companies, deals, tickets and custom objects
Revisions keptContacts: up to 45 per property. Companies, deals, tickets, custom objects: up to 20
What countsChanges made in HubSpot and through the API
ContentsCurrent and past values with timestamps (UTC); optionally the user or tool that made each change
RecordsOnly those that have or had a value
DeliveryDownload link by email and in the notification center

The revision cap matters: a property that a workflow or integration updates often may have lost the older values you’re looking for.

How to export property history in HubSpot

  1. Go to Settings > Properties and select the object.
  2. Find the property, hover over it, click More and choose Export property history.
  3. Choose the file format. Tick Include source information if you need to know which user, workflow or integration made each change.
  4. Click Export and download the file from the email or the notification center.

How to restore previous property values

  1. Export the history with source information, so you can identify the bad change.
  2. Filter the file to rows changed at the time, or by the source, of the mistake.
  3. Take the value from just before that change for each affected record.
  4. Build an import file with two columns: Record ID and the property, holding the earlier value.
  5. Import it as an update to the same object. Check a few records afterwards.

For a quick look at one record, the property’s history is also on the record itself. Very recent bulk changes may be easier to reverse with HubSpot’s separate restore tool for CRM changes, which covers the last 14 days.

Common mistakes

  • Waiting too long. Each new change pushes an old revision out once the cap is reached.
  • Exporting values instead of history. A normal record export shows only the current value.
  • Importing without Record ID. Rows without it can create new records instead of updating.

Where Jetstack AI fits

Jetstack AI works with property definitions, not values on records, so it doesn’t export property history. When a property’s definition is the problem (the wrong type, a missing option, or the same field set up differently in two portals), its Portal reuse imports and reconciles property definitions; see how properties are handled. For an overview of property health, see Portal Audit.

Sources

Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

HubSpot admin

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

HubSpot admin

Related questions.

How do I export property history in HubSpot?

To export property history in HubSpot, go to Settings > Properties, choose the object, hover over the property, click More and select Export property history. Pick a file format, optionally include the user or tool behind each change, and export. HubSpot keeps up to 45 revisions for contact properties and 20 for companies, deals, tickets and custom objects.

Can I export the history of several properties at once?

HubSpot's property history export works one property at a time. For many properties, repeat the export or use the API.

Which records are in the file?

Only records that have, or previously had, a value for the property. Dates are in UTC.

Can I undo a bad bulk update with it?

Yes, if the change is within the stored revisions. Filter the file to the values from just before the bad change, keep the Record ID and that value column, and import the file to set the property back.