On this page
What HubSpot supports natively
HubSpot’s own export guide lists exports area by area. The main ones:
| Area | How to export | Watch out for |
|---|---|---|
| CRM records | Index page > Export, per object; or a CRM backup (Super Admin) | Backups exclude associations and activity data |
| Properties | Settings > Properties > Export all properties | Definitions and usage, not values |
| Property history | Per property: More > Export property history | Capped revisions per object |
| Website pages, blog posts, templates | Exported as HTML files, plus data exports | |
| Files, HubDB, URL redirects | From each tool | |
| Marketing emails | Export email design as HTML or PDF | Performance data is a separate export |
| Forms, segments, campaigns | Form submissions, segment members, campaign data | |
| Workflows | Spreadsheet of the workflow list; PNG of one workflow | No performance data or history |
| Reports and dashboards | Export from each report or dashboard | |
| Account | Users, activity history and audit logs | |
| Inbox conversations | No direct export; Conversations API | |
| Sales activity (calls, meetings) | Custom reports or the Engagements API |
How to export all data from HubSpot
- Start with a CRM backup for contacts, companies, deals, tickets, custom objects, products, calls, conversations and tasks. See backing up CRM data.
- Export records with associations for the objects whose relationships you need, since the backup doesn’t include them. Use CSV. See exporting contacts.
- Export all properties for every object to keep the data dictionary, then property history for the fields you might need to restore.
- Export content: pages, blog posts, templates, files, HubDB tables and URL redirects.
- Export marketing emails you want to keep as HTML.
- Export the workflow list and screenshot or PNG-export the workflows that matter, with their settings written down.
- Export reports, form submissions and segments you rely on.
- Use the API for inbox conversations, engagements and anything not covered above.
- Keep a log of what you exported, when and from which Hub ID.
Common mistakes
- Treating a backup as a migration. Exports give you data, not a working portal. Workflows, settings and references have to be rebuilt.
- Forgetting associations. Without them, deals and contacts lose their companies.
- Leaving it until the account closes. Some features stop working after deactivation; export while you still have full access.
Where Jetstack AI fits
Jetstack AI doesn’t export records. When the reason for the export is moving a setup to another HubSpot portal, Portal reuse copies the configuration that exports can’t carry: workflows, properties, pipelines, lists, forms, emails and CMS assets, with references remapped for the destination. See the supported assets.
Sources
- Export your content and data (HubSpot Knowledge Base)
- Back up CRM data (HubSpot Knowledge Base)
- Export records (HubSpot Knowledge Base)
- Supported assets (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
HubSpot admin
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse