Exporting your contacts from HubSpot takes about four minutes. Open the contacts page, click Export, pick CSV and wait for the email. Most guides stop there, and the contacts are the one export that can wait. They’ll still be exportable on your last paid day, and most of what matters won’t be. HubSpot’s own export index names two things that break when the account is deactivated: forms lose their paid features, and legacy CTAs stop working on every outside page they were pasted into. Dropping to the free tier isn’t a deactivation, but anything that needs a paid tier still ends with the subscription. 1 Source 1 HubSpot Knowledge Base, “Export your content and data,” updated 25 September 2026, read 5 November 2026. The page is HubSpot’s own index of every export path. The workflows, the email data and the API access close before the contacts do, so when we run an exit, the contacts come out last.
If you came here for how to export contacts from HubSpot, the steps are in section 3. The rest of this guide is the order to run everything else in, the format each export arrives in, and one line per export on what it leaves out. Every statement about what HubSpot exports comes from HubSpot’s own documentation, read on 5 November 2026, rechecked on 16 November and cited at the end. What the gaps cost on one portal is in Dies With the Portal; this piece only points at them.
Why the order matters: what closes with your contract, and what needs a login
Two clocks run against an exit, and a door closes at the end of it.
The first clock is the downgrade. A private app, a common way to pull from the API and one HubSpot now files under legacy apps, loses every scope the downgraded account no longer qualifies for. Until another app type’s documentation says otherwise, assume it behaves the same. 2 Source 2 HubSpot developer documentation, “Legacy private apps” overview, modified 30 October 2026, read 5 November 2026: “Private apps will lose access to scopes when your HubSpot account is downgraded and loses access to functionality.” A script that read workflows or HubDB on a Professional subscription reads nothing once you’ve downgraded. The CRM backup tool needs Starter or above, and the workflow details page, where the logs live, needs Professional. Those pulls happen before your contract ends or not at all.
The second clock is retention. Workflow action logs are kept 90 days and enrollment history six months. Export download links expire after 30 days, and a CRM backup has to be downloaded within 14. None of this matters if the files leave HubSpot the day they’re made. All of it matters if “we exported it” means a download link in someone’s inbox, counting down to day 30.
Then the door. A few things in a portal aren’t exports at all. They’re screens, readable only by a person or a browser session while the account is open: the enrollment rules inside a workflow, the subscription timeline holding the opt-outs of contacts you deleted years ago, a report nobody rebuilt as a dataset. 3 See also 3 See Dies With the Portal for the seven things no export on this page gives you, and what each one cost on one portal.Read Dies With the Portal: Seven Things a HubSpot Export Will Not Give You Those go first. If the account drops to the free tier, some of those screens may stay readable. The paid-tier screens close either way, and a closed account keeps none of them.
So the order runs like this: the login-only reads and the paid-tier pulls first, then the marketing and content exports, then the CRM, and the CRM again on the last paid day.
1. Subscription status and suppression, before anything else
A new sending domain has no reputation, and the fastest way to lose one is to mail people who already said no. Pull consent first, through the API. The contact export carries it too, but that’s the last export on this list.
The contact-level state lives in properties HubSpot names: Unsubscribed from all email, Opted out of email for each subscription type, Email hard bounce reason, Email address quarantined, and Marketing contact status, which is a billing flag and not consent. 4 Source 4 HubSpot Knowledge Base, “HubSpot’s default contact properties,” updated 21 September 2026, and HubSpot developer documentation, “Subscriptions preferences v3,” modified 9 June 2026, read 5 November 2026, and “Subscriptions preferences” (v4), modified 5 June 2026, read 16 November 2026. Over the API, the v4 subscriptions endpoint reads the statuses of many addresses in one batch request and returns a status per subscription type, with its source: an individual preference, a portal-wide opt-out, or a brand-wide one. The v3 endpoint most older guides describe reads one address per request. The same properties come out again in the contact export in section 3 if you choose all properties, and that file, taken on the last paid day, is the one to load.
HubSpot’s export index helpfully points out that exporting all your contacts will include unsubscribes, and then explains how to filter them out. Please don’t. For a migration they’re the most valuable rows in the file.
What it leaves out: everyone you deleted. We found this on a portal where HubSpot had kept each address’s opt-out after the contact was deleted, in the email subscription timeline and in no export. The contact file showed 602 suppressed contacts, and the portal was refusing to mail 6,714 addresses. The load order that handles both is in Marketable Is Not Subscribed. 5 See also 5 See Marketable Is Not Subscribed for the load order and for why the billed marketing-contact count is the wrong number to migrate.Read Marketable Is Not Subscribed: The Consent Trap When You Move Email Off HubSpot
2. Workflows: the spreadsheet, the picture, and the API
You get two workflow exports from the interface, and neither one gives you the logic. From Automation > Workflows, Table actions > Export view downloads a spreadsheet of every workflow not in a folder; each folder exports separately. It holds the name, whether the workflow is on, total and current enrollments, goal conversions, create and modify dates with the user, and the type. There’s no performance data in it and no history.
From inside a workflow, File > Export as .PNG gives you a picture of the canvas. Yes, it’s a picture. It’s good for a slide and no use for rebuilding anything.
The details page adds two more on Professional and Enterprise: Action logs > Export action logs to .csv, covering 90 days, and the enrollment history, six months, which the details page exports to CSV and the workflow editor exports into a static segment. 6 Source 6 HubSpot Knowledge Base, “Understand your workflow details page,” updated 26 October 2026, and “Review your workflow’s enrollment history,” updated 3 August 2026; HubSpot developer documentation, “Workflows API” (v4), modified 15 April 2026. All read 5 November 2026. HubSpot’s export index page, read the same day, says action logs are kept 180 days; the details page says 90. Plan on 90. The one route to the logic is the workflows v4 API, in beta when we read it: a GET per workflow returns the full definition as JSON, enrollment criteria included, for an app granted the automation scope. The list endpoint returns only key fields, so the definitions come from a GET per workflow or a batch read of many workflow IDs in one request. That scope goes with the downgrade, so this pull can’t wait.
What it leaves out: the logic. You get a list of names and a picture, and nothing a person can read as rules. The spam patterns and territory exclusions written into enrollment criteria exist only on the canvas or in that JSON, and on that portal deleted workflows returned nothing on any read. That’s item 2 in Dies With the Portal.
3. How do you export contacts from HubSpot?
Open the contacts index page and the All contacts view, then choose Export under View settings. Pick CSV and click Customize: all properties and associations, all email addresses, all associated records. HubSpot emails a download link that dies in 30 days. The same steps work for companies, deals, tickets, calls and custom objects.
- Open the object’s index page and its All view (All contacts, for contacts).
- Click the view configuration icon in the upper right to open View settings, and under Sharing select Export.
- Choose CSV. The reason is just below.
- Click Customize, because the default export is only the columns in the view, and set Properties included to All properties and associations on records.
- Tick Include all email addresses for contacts, or Include all domains for companies.
- Set associations to All associated records. It’s CSV only, and it lifts the default cap of 1,000 associated IDs per column.
HubSpot emails you a link, and it expires in 30 days. Stick with CSV, which has no column limit. XLS stops at 256 columns and XLSX at 16,384, and anything past the cap is dropped. 7 Source 7 HubSpot Knowledge Base, “Export your records,” updated 12 November 2026, read 16 November 2026; “Back up CRM data,” updated 4 June 2026; “Organize, delete, and export properties,” updated 11 June 2026; “Export property history,” updated 8 September 2026; HubSpot developer documentation, “Exports” API, modified 15 April 2026, and “Pipelines” API, modified 3 September 2026. The others read 5 November 2026; the Pipelines page read 16 November 2026.
Two companion exports are worth running alongside it. Settings > Properties > Export all properties gives you the definitions, with internal names, types, options, fill rates and where each property is used. That’s the file the new schema gets built from. Export property history, per property, gives past values with UTC timestamps, but only 45 revisions per contact property and 20 on company, deal, ticket and custom object properties.
The CRM backup at Settings > Backup & Restore (Starter and above) is a zip with a CSV per object and the easiest full snapshot, with one catch: no associations and no activity data, although calls, conversations and tasks come out as objects of their own. The record export also exists as an API: one POST to the exports endpoint, 30 exports a day, one at a time, and a download URL good for five minutes, so whatever fetches it had better be awake.
What it leaves out: the ladder your deals climb. An export shows each deal’s stage as a value, never the stage labels and their order, and it leaves out every file ever attached to a record. The stages are the cheap fix: a GET to the pipelines endpoint, one per object type, returns each stage’s label and display order, and for deals its win probability. Items 3 and 4 in Dies With the Portal.
4. Segments, which used to be lists
From CRM > Segments, hover over the segment, choose More > Export, tick the properties and pick the format. You get the members and their property values and nothing else: no associated records, and of a contact’s company only the primary one. 8 Source 8 HubSpot Knowledge Base, “Export segments,” updated 16 September 2026, read 5 November 2026.
What it leaves out: the definition. An active segment is a filter tree, and the file only holds what that filter returned on the day you ran it, so write the criteria down while the screen is open. On one portal, eleven of fourteen “suppression” lists turned out to be targeting rules rather than consent; the sorting is in Marketable Is Not Subscribed.
5. Engagements, activities and attachments
There’s no Export button for emails, notes or meetings. You have three routes: export one contact’s data from its record (Actions > Export contact data, with the Contact activities box ticked, which arrives as separate files), build an activity report, or use the engagements API, which HubSpot’s developer documentation now calls the activities API. 9 Source 9 HubSpot Knowledge Base, “Export contact data,” updated 2 October 2025, and “Manage your files,” updated 3 August 2026; HubSpot developer documentation, “Activities | Email,” “Activities | Notes,” both modified 13 April 2026, and “Files API,” modified 15 September 2026. All read 5 November 2026. Calls and tasks are the exceptions, each with its own index page and Export. For a whole portal the API is the only practical route. Email objects carry the subject, the body and a semicolon-separated list of attachment IDs, note objects carry the body and the same list, and the Files API turns an ID into a signed URL, since a private file’s plain URL returns a 404. Files in the Files tool export as a zip, Super Admin only.
Before you pull them all, look at what they are. On one portal most of the activity log was copies of email that had never left the inboxes it came from, so it belongs in an archive you own. 10 Editor's note 10 130,935 of about 168,000 engagement records on that portal were emails copied in from the team’s connected inboxes.
What it leaves out: the attachments, unless you walk every engagement for them. That’s item 4 in Dies With the Portal.
6. Marketing email: the performance, not the emails
Marketing > Email > Export emails gives you a spreadsheet of every email’s performance, with a box for advanced delivery data on bounces and non-sends, and an Associated workflows column that’s the only cross-reference between an email and the automation using it. Per email, the Recipients tab exports who was delivered, opened, clicked, bounced or unsubscribed, and the version with timestamps needs Marketing Hub Starter or above. 11 Source 11 HubSpot Knowledge Base, “Export marketing email performance data,” updated 22 September 2026, and “Delete contacts who no longer receive your marketing emails,” updated 5 October 2026; HubSpot developer documentation, “Marketing API | Marketing Email,” modified 13 April 2026. All read 5 November 2026.
Email tools > Create segment of hard-bounced contacts builds the bounce list, which then exports as a segment. Addresses that bounced in three or more HubSpot accounts never appear in it.
What it leaves out: the emails themselves. HubSpot’s export index has no HTML export for a marketing email body. The Marketing Emails v3 API returns the email’s definition, and turning that into something another platform will send means rebuilding it. Pull the images they reference through the Files export before the portal stops serving them.
7. Forms
Each form’s submissions export from Marketing > Forms, under Actions > Export submissions, as CSV, XLS or XLSX for a date range you choose. 12 Source 12 HubSpot Knowledge Base, “Export form submissions,” updated 16 June 2026; “Export web content and data,” updated 28 August 2026; “Create and populate HubDB tables,” updated 27 July 2026; “Create and manage URL redirects,” updated 20 October 2026. All read 5 November 2026. Submissions from IP addresses or referrers you excluded from analytics can’t be exported at all. The per-page export needs Marketing Hub Professional.
What it leaves out: the form itself. It stays embedded on every page that carries it, and once the account is deactivated it loses its paid features. Replace the embeds before your contract ends.
8. Pages, posts, templates, HubDB, redirects and files
From Website Pages, Landing Pages or Blog, Actions > Export all pages and blog posts (HTML) produces one download with the templates in a Styles folder. You’ll need Super Admin or Publish permission. Blog posts also export as a data file. HubDB tables export as CSV from the table’s Actions menu and download at once, with images rendered as URLs. URL redirects export as CSV from Settings > Domains & URLs; the page lists the feature for Professional and Enterprise on Marketing and Service Hub, and Starter and above on Content Hub. Files export as a zip from the Files tool.
What it leaves out: video hosted on HubSpot’s video domain, which isn’t in the Files tool, and a marketplace theme’s source, which HubSpot won’t let you download. Items 5 and 6 in Dies With the Portal.
9. The rest of HubSpot’s list
HubSpot’s export index runs longer than the eight sections above, and most of what’s left is quick work. Reports and dashboards, quotes, invoices, payments, products, subscriptions, contracts, credit memos, knowledge base article data, published social posts, SMS, CTA data, SEO data, the sitemap, membership data, users and the account’s audit logs each have their own export, linked from the index. Marketing events leave only through the Marketing Events API. Sales documents download one at a time.
Two are harder. The inbox has no export button. HubSpot’s answer for past chat transcripts is the Conversations API, or copying, printing or saving them by hand. We hope nobody is printing them. Some tools aren’t on the index at all: sales email templates, sequences and snippets have no listed export path, so list the ones still in use and rebuild them in the new tools while the portal is open.
HubSpot’s own export page tells you how to filter the unsubscribes out of a contact export. For a migration they’re the most valuable rows in the file.
Every export, where it lives, and the gap
| Export | Where it lives | Format | What it leaves out |
|---|---|---|---|
| Subscription status | Contact properties; subscriptions preferences API | CSV; JSON per address | Opt-outs on deleted contacts (why) |
| Workflows | Automation > Workflows, Table actions and File menus; v4 API | Spreadsheet; PNG; JSON | The rules in readable form; deleted workflows (item 2) |
| Contacts, companies, deals, tickets | Object index page > View settings > Export > Customize; exports API; pipelines API for stages | CSV by emailed link, 30 days | Stage order and labels, unless pulled from the pipelines API; attachments (items 3, 4) |
| CRM backup | Settings > Backup & Restore (Starter+) | Zip of CSVs, 14 days | Associations and activity (calls, conversations and tasks excepted) |
| Properties and history | Settings > Properties | Spreadsheet | History past 45 revisions (20 on non-contacts) |
| Segments | CRM > Segments > More > Export | Spreadsheet, by emailed link | Associations; the filter definition |
| Activities | Per contact, a report, or the activities API | Separate files; JSON | Attachments, unless walked by ID |
| Marketing email | Marketing > Email > Export emails; Recipients tab | CSV, XLS, XLSX | The email bodies, which have to be rebuilt |
| Forms | Marketing > Forms > Export submissions | CSV, XLS, XLSX | Excluded-IP submissions; the live embeds |
| Pages, posts, templates | Content > Actions > Export all (HTML) | HTML files | Hosted video; marketplace theme source (items 5, 6) |
| HubDB, redirects, files | HubDB table Actions; Domains & URLs; Files tool | CSV; CSV; zip | Nothing in the file, but each needs a paid tier or a Super Admin |
| Inbox and chat | Conversations API | JSON | No export button; transcripts by API or by hand |
| Templates, sequences, snippets | Not on HubSpot’s export index | None listed | Everything; rebuild the ones in use |
Verify the export against the portal’s own counts
An export is a claim until someone checks it, and HubSpot gives you the numbers to check against. Settings > Import & Export is the export log: each export, its source, the user, and a Records column with the count HubSpot thinks it wrote. Only a Super Admin sees every export in the account (everyone else sees only their own), so run the check as a Super Admin. 13 Source 13 HubSpot Knowledge Base, “Set up export notifications and view a log of exports in your account,” updated 16 March 2026, read 5 November 2026. Large exports arrive in pieces. HubSpot splits a CSV or XLSX of more than 1,000,000 rows (an XLS of more than 65,535) into several files in one zip, and zips any CSV over 2 MB, so add the parts up first. Count the rows against that column and against the record count on the index page you exported from, and check segment files against the sizes HubSpot shows. The numbers should agree, and if they don’t, you want to find out now rather than after the load.
Then read values, not rows. Pick a sample of Record IDs from each file, open those records in the portal, and compare property values field by field. Start with the consent properties, because a wrong unsubscribe loads as a wrong subscriber. The catch is that an exported funnel report contains the objects created in the date range, not the ones that changed stage, so it won’t match the report on screen.
Do all of it again on the last paid day. Unsubscribes keep arriving while you plan the migration, and the only snapshot that counts is the one taken before the load. 14 See also 14 See The HubSpot Renewal Calendar for the T-minus dates these exports hang off, and why cancelling early is the one unforced error.Read The HubSpot Renewal Calendar: What Must Happen Before the Contract Ends, and What Cannot Be Done After Hash every file as it lands and store it somewhere that isn’t a HubSpot download link.
The HubSpot Renewal Calendar gives the dates, and Dies With the Portal lists what no export will ever contain.
If you only do one thing from this guide, pull consent first and keep every unsubscribe. A missed workflow export costs you a rebuild. A bad first send from a new domain, to people who already said no, costs you the domain’s reputation, and that’s the hardest mistake here to undo.
The research is free. So is the diagnosis. 60 seconds →