You can restore HubSpot content to recover from deletion or corruption. Restores are supported to the same HubSpot portal (in place). Cross-account restore is not supported.
Restore destinations
| Destination | When to use |
|---|---|
| In place (same HubSpot portal) | Recovering from accidental deletion, corruption, or ransomware on the original HubSpot instance. |
Permissions and prerequisites
Restore requires the same service key credential used for backup, but the credential must include the write scopes listed in Configure HubSpot user and permissions. If the service key was created with only read scopes, you must update the service key's Scopes tab to grant the required write scopes before running a restore.
The following object types have known restore limitations:
- Meeting links: Meeting link definitions are backed up but not fully restorable. The HubSpot API does not support creating or updating meeting links via API.
- Sales sequences: Sales sequence definitions are backed up but not fully restorable. Sales sequence enrollment requires live user context and cannot be automated via API.
- Built-in properties and default pipelines: Built-in HubSpot properties and default pipelines are skipped during restore because they already exist on the target portal.
If a restore job completes with warnings, check the job log for specific objects that could not be restored due to these limitations.
You can restore HubSpot content to the original portal.
- From the Command Center navigation pane, go to Protect → SaaS Applications.
- Click the HubSpot instance that you want to restore.
- On the Content tab, browse to the hub or object type that you want to restore, or use the search box to find specific content.
- Right-click the content to restore, and then click Restore.
- On the Restore page:
- Restore time: Select the recovery point (backup job) to restore from.
- Restore content: Confirm the selected content. You can expand the tree to select individual hubs, object types, or objects.
- Restore destination: Confirm that the destination is set to the original HubSpot portal.
- Click Submit.
- Monitor the restore job in the Jobs view.
Restore proceeds in parent-first order: schemas and properties are restored first, then CRM and commerce object records, then engagement activities and associations. This ensures that object definitions exist before records that reference them are created.