9 Ways to Export HubSpot Data (Records, Tickets, Emails, Inbox)
HubSpot export compared: record export, property history, Exports API, CRM backup, object APIs, Search, Conversations, knowledge base, workflows.
Published 8 min read

On this page
There are nine ways to run a HubSpot export: record exports from an index page, property history exports, the Exports API, CRM backups, the CRM object APIs, the CRM Search API, the Conversations API, the knowledge base export and the workflow export. Record exports and backups leave out activities such as calls and notes. For tickets with emails, notes and conversations, use the APIs.
This guide is for HubSpot admins and operations leads who need their data out, for a backup, a report or a move to another platform. Every limit is from HubSpot's own Knowledge Base or developer documentation, as of November 2026. Tier names (Starter, Professional, Enterprise) apply to HubSpot Smart CRM and the Hubs.
Which HubSpot export method fits which job?
The record export for lists, the backup for a safety copy, and the APIs for anything with activities. Only the APIs return emails, notes and conversations with their records.
The nine routes side by side:
| Method | Gets you | Leaves out | Limit to plan around |
|---|---|---|---|
| 1. Record export | Records, properties and associations from one index page | Activities such as calls and notes | 300 exports per rolling 24 hours |
| 2. Property history export | One property's current and past values across all records | Revisions beyond 45 (contacts) or 20 (other objects) | One property per export |
| 3. Exports API | The same, scripted, with associated record IDs | Activity content | 30 exports per rolling 24 hours, one at a time |
| 4. CRM data backup | A scheduled copy of core objects | Associations and activity data | Weekly on Starter and Professional, daily on Enterprise |
| 5. CRM object APIs | Records, emails, notes and their associations | Nothing in principle; costs calls | 625,000 calls a day on Professional |
| 6. CRM Search API | Filtered sets of records | Archived records | 10,000 results per query |
| 7. Conversations API | Inbox and help desk threads, message by message | Full email reply history, unless fetched separately | No separate limit stated |
| 8. Knowledge base export | Article data such as title, language and URL | Article bodies: HubSpot does not say; test first | Service Hub Professional or Enterprise |
| 9. Workflow export | A list of your workflows | Performance data, history and the emails used | Spreadsheet only |
1. Record export from an index page
What it is. An export of records from an object's index page (contacts, companies, deals, tickets) as CSV, XLS or XLSX. You need Export permissions.
What it gets you. A spreadsheet of the records' current property values and associations, delivered as a download link. By default HubSpot includes only the view's columns; "Customize" switches to all properties, with or without associations. Associations come as up to 1,000 associated record IDs per column plus the record name, or all of them in CSV files only.
What it leaves out. Activities. HubSpot's export article says record exports do not include contact activities such as calls and notes, and points to a single contact's data export, activity reports or the engagements API.
Limits. 300 exports within a rolling 24 hours, three at a time. Files over 1,000,000 rows (CSV, XLSX) or 65,535 rows (XLS) are split. XLS stops at 256 columns and XLSX at 16,384. Download links expire after 30 days.
Who sees it. Every export lands in the export log under Settings > Import & Export, kept for three years. Super Admins see every user's exports and can set a large-export notification of up to 275,000 records; other users see only their own.
Use it when you need a list: contacts for a campaign, tickets for a report, deals for finance.
2. Property history export
What it is. An export of one property's history across all records, from Settings > Properties > More > Export property history. It is available on all HubSpot plans and needs the CRM Export and [Object] Edit All permissions.
What it gets you. Each record that has or had a value for the property, its current and historical values, and when each changed. Tick "Include Source Information" to add the user or source behind each change.
What it leaves out. Older revisions. HubSpot keeps up to 45 revisions per contact property and 20 per company, deal, ticket and custom object property, whether the change came from HubSpot or the API.
Use it when you need an audit trail for a few key properties, such as ticket status or deal stage, before you leave.
3. Exports API
What it is. The same kind of export started from code, so it can run on a schedule.
What it gets you. Records plus up to four associated objects per request, exported as the associated record IDs.
What it leaves out. Activity content. Associations come as IDs, so you still rejoin them.
Limits. Thirty exports in a rolling 24 hours, one at a time. Associations are capped at 1,000 per row unless an override flag is set.
Use it when a script needs a nightly or weekly extract of a few objects with their links.
4. CRM data backup
What it is. A scheduled backup of your CRM data that a Super Admin downloads.
What it gets you. Contacts, companies, deals, tickets, custom objects, products, calls, conversations and tasks, according to HubSpot's backup article.
What it leaves out. HubSpot says "associations and activity data aren't included", so the backup cannot tell you which contact belongs to which ticket.
Limits. Once a week on Starter or Professional; once every 24 hours on Enterprise.
Use it when you want a recurring safety copy of core records and can live without the links between them.
5. CRM object APIs
What it is. HubSpot's APIs for every CRM object, including activities, plus the associations API for the links between records.
What it gets you. The complete picture. Email activities keep their body in hs_email_text, their time in hs_timestamp and their attachments as semicolon-separated IDs in hs_attachment_ids; notes do the same, with up to 65,536 characters in hs_note_body. Reading records with propertiesWithHistory returns past property values too. Survey responses (NPS, CSAT, CES) can be read through their own read-only API.
Files. HubSpot's Files API returns a file's details from /files/v3/files/{fileId}. For a private file, the URL it returns gives a 404, so you request a signed URL from /files/v3/files/{fileId}/signed-url instead. HubSpot's activity guides do not say outright that attachment IDs are Files API IDs, so test a few before a full run.
What it leaves out. Nothing structural. The cost is requests.
Limits.
- Private apps: 250,000 calls a day on Free and Starter, 625,000 on Professional and 1,000,000 on Enterprise, with 100 to 190 requests per 10 seconds.
- The burst limit applies per app, but the daily limit is shared by every app in the account and resets at midnight in the account's time zone.
- The associations API has its own limit: 500,000 requests a day on Professional and Enterprise.
Use it when the data is going into another platform, or you need tickets with their emails, notes, files and associations.
6. CRM Search API
What it is. Search endpoints that return records matching filters, such as tickets closed in a date range.
What it gets you. Targeted pulls without reading a whole object.
What it leaves out. Archived records never appear in search results, and new or updated records can take a few moments to show.
Limits. Five requests per second per account, 200 records per page and 10,000 total results for any query. Split large pulls by date range to stay under the cap.
Use it when you need a filtered subset, not a complete copy.
7. Conversations API
What it is. The API for HubSpot's conversations inbox and help desk threads: chat, email, forms and other channels.
What it gets you. The message history of each thread, plus internal comments, which HubSpot never sends to the customer. HubSpot's export guide says inbox data has no file export and directs customers to this API.
What it leaves out. HubSpot cuts the reply history section of email messages in the response. The full email needs a second call to the original content endpoint.
Limits. HubSpot's Conversations guide states no separate rate limit, so a run is planned inside the account's daily API limit.
Use it when support conversations matter: help desk history, chat transcripts, email threads on tickets.
8. Knowledge base export
What it is. An export of your knowledge base articles to CSV, XLS or XLSX, on Service Hub Professional or Enterprise, with an assigned Service Hub seat and the Service Access with Knowledge base articles permission.
What it gets you. Article data such as title, language and URL, "and more", per HubSpot's export article.
What it leaves out. Possibly the article bodies. As of November 2026, HubSpot's export article does not list the file's columns or say whether bodies are included. Run a test export and check for a body column before relying on it.
Use it when you are auditing or moving the knowledge base.
9. Workflow export
What it is. A spreadsheet of your workflows.
What it gets you. An inventory to plan a rebuild from.
What it leaves out. HubSpot says workflow exports do not include performance data, the workflow's history or data from emails used in the workflow. It lists workflows; it does not carry what each one does, so document triggers and actions before you leave.
Use it when you need the list of automations to recreate elsewhere.
Which way should you export HubSpot data?
Use the record export or the backup when a spreadsheet or a safety copy is the goal; both are self-serve. Use the APIs when the data is going somewhere, because that is when conversations, emails, notes and files have to be rejoined to their tickets.
The route for each situation:
| Your situation | Use |
|---|---|
| A list for a spreadsheet | Record export |
| The change history of a key property | Property history export |
| A scheduled extract with record links | Exports API |
| A recurring safety copy | CRM data backup |
| Tickets with emails, notes, files and associations | CRM object APIs plus the associations API |
| Chat and email threads from the inbox or help desk | Conversations API, with original content for emails |
| Moving to another platform | API-based migration, tested on a sample |
Moving the CRM? See the HubSpot to Salesforce migration page. Moving only support and keeping the CRM? Our HubSpot to Zendesk guide covers that split. Connecting HubSpot to a help desk instead of leaving it? Run the 7 checks before you connect a CRM and a help desk.
More on what moves is on the HubSpot platform page, and checking a copy against the source is covered in our guide to data migration validation.
Facts checked November 17, 2026 from HubSpot Knowledge Base: Export your records, HubSpot developer docs: Exports API, HubSpot Knowledge Base: Back up CRM data, HubSpot developer docs: API usage guidelines and limits, HubSpot developer docs: Using Object APIs, HubSpot developer docs: Associate records, HubSpot developer docs: Email activities, HubSpot developer docs: Notes, HubSpot developer docs: CRM Search API, HubSpot developer docs: Conversations API, HubSpot Knowledge Base: Export your content and data, HubSpot Knowledge Base: Export web content and data, HubSpot developer docs: Survey responses, HubSpot Knowledge Base: Export property history, HubSpot Knowledge Base: Set up export notifications and view a log of exports in your account and HubSpot developer docs: Files API. No vendor paid for this article. How we research
HubSpot export FAQ
How do I export all data from HubSpot?
No single button does it. Record exports cover records and associations but not activities, and the CRM backup has neither activity data nor associations. For everything, combine the object APIs (records, emails, notes), the associations API (links between records), the Conversations API (inbox threads) and the knowledge base export. Then check the result against record counts in HubSpot.
How do I export HubSpot emails and notes?
Through the API. HubSpot's record export does not include activities. Email activities are read for their body, timestamp and attachment IDs, and notes for their body. For smaller needs, HubSpot also suggests activity reports or a single contact's data export.
How long do HubSpot export files stay available?
Download links to record export files expire after 30 days, and the export log lets you re-download only exports completed in the last 30 days. CRM backups must be downloaded within 14 days. None of these is a long-term archive, so save the files to your own storage on the day they arrive.
Can two HubSpot accounts be merged with an export?
Not directly. HubSpot's export guide says there is no way to merge all the data between accounts: you export and re-import, or recreate. Records can be imported into the second account, but activities, associations and inbox conversations need the APIs, as they do when leaving HubSpot.
Is the CRM Search API a good way to export every ticket?
No. It returns at most 10,000 results for any query and never returns archived records, so a search-based export is incomplete by design. It suits filtered pulls. For a complete copy, read the object through the object APIs and count archived records separately.
Can I export the history of a HubSpot property?
Yes, one property at a time. In Settings > Properties, choose the property and select Export property history; you need CRM Export and [Object] Edit All permissions. The file lists past values and change times. HubSpot keeps up to 45 revisions for contact properties and 20 for other objects, so older changes are gone.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


