HubSpot exports are straightforward for records and awkward for history. Contacts, companies, deals, tickets and custom objects come out of any list view in a few clicks. Notes, emails, calls and meetings don’t come out of that export at all. This guide covers both, with HubSpot’s documented limits, and what you need if the export is the first step of a migration.
How do I export records from HubSpot?
Record exports are available on all HubSpot products and plans to users with Export permissions.
- Go to the object under CRM (Contacts, Companies, Deals, Tickets, or a custom object).
- Open the view you want. To export every record, open the All [records] view.
- In list view, click Export at the top right. In board view, open Board options and choose Export view.
- Choose the file format (CSV, XLS or XLSX), name the export and choose the header language.
- Click Customize to choose what is included: the view’s properties only, all properties without associations, or all properties with associations. Contacts can include every email address, companies every domain.
- Click Export. HubSpot emails a download link.
What are HubSpot’s export limits?
| Limit | Value |
|---|---|
| Exports per rolling 24 hours | 300, with 3 running at once (others queue) |
| Rows before splitting | 1,000,000 for CSV or XLSX; 65,535 for XLS (larger exports may arrive as a zip of several files) |
| Columns | XLS 256, XLSX 16,384; extra columns are dropped, so use CSV for wide exports |
| Associations | Up to 1,000 associated record IDs per association column |
| Compression | CSV files over 2 MB are zipped |
| Link expiry | 30 days |
| Export log | 3 years |
HubSpot notes that large exports can take a few hours.
How do associations come out of a HubSpot export?
When you include associations, HubSpot adds columns at the end of the file with the associated record IDs and names. Each column holds up to 1,000 associated record IDs. The All associated records option is CSV-only.
For a migration, the IDs are what matter. Export the associated object too (for example companies alongside contacts), so you can resolve each HubSpot ID to a record in the new system. Association labels, such as “billing contact”, need checking separately, because the destination CRM may model them differently or not at all.
How do I export notes, emails and calls from HubSpot?
This is the question HubSpot Community threads ask most. The record export doesn’t include activities. HubSpot’s export article lists three routes:
- Export an individual contact’s data from the contact record. Fine for one person, not for a database.
- Export certain activity reports from the reports tool. Useful for counts and some fields, but not a complete, re-loadable history.
- Use the engagements API. The only complete route for notes, emails, calls, meetings and tasks with their timestamps and associations.
If you need the timeline in the next system, plan for the API route from the start. A partial history is often worse than none, because users assume it is complete.
What should I export before leaving HubSpot?
| Data | Native route | Notes |
|---|---|---|
| Contacts, companies, deals, tickets | Record export, all properties and associations | Repeat per object |
| Custom objects | Record export from the object’s view | Export the schema definitions too |
| Pipelines and stages | Manual list from settings | Needed to map deal stages |
| Owners and teams | User list from settings | Map by email in the destination |
| Notes, emails, calls, meetings, tasks | Engagements API | Not in record exports |
| Files and attachments | Files tool or API | Keep links to their records |
| Lists, workflows, sequences, forms | Rebuild in the destination | Logic doesn’t export as data |
| Marketing email content and stats | Manual, per asset | Usually archived, not migrated |
How do I get a HubSpot export ready for another CRM?
- Export every object with all properties and associations, as CSV.
- Pull activities through the API, with their associated record IDs and timestamps.
- Map HubSpot properties to destination fields, including dropdown values. Lifecycle stage and lead status often split into separate fields elsewhere.
- Map owners by email to users in the destination.
- Load parents first: companies (accounts), then contacts, then deals (opportunities), then activities.
- Translate IDs at each step so contacts land on the right accounts and activities on the right records.
- Re-export the changes. Users keep working after the first export. Pull records modified since, before go-live.
How do I move data from one HubSpot portal to another?
Moving between portals (after an acquisition, a rebrand, or a move to the EU data centre) uses the same tools on both sides: export from the old portal, import into the new one. The catches are the ones above, doubled:
- Record IDs change. Every association has to be rebuilt from the old IDs to the new records.
- Create dates reset. Contacts imported into the new portal get the import date as their Create date, so carry the original into a custom property.
- Activities need the API out and the importer in, with each one mapped to its new parent record.
- Settings don’t move as data. Properties, pipelines, workflows, lists and forms must be recreated before the records arrive.
Plan the property and pipeline build first, then the records, then activities.
Where does a HubSpot export fall short for a migration?
- History lives outside the export. Without the API, the timeline stays behind.
- IDs don’t travel. Every relationship has to be rebuilt in the destination’s terms.
- Exports are snapshots. There’s no built-in way to capture changes during cutover.
- Nothing checks the result. Row counts don’t tell you whether a note landed on the wrong contact.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It extracts every HubSpot object, association and activity through the API, proposes field-level mappings with AI for you to review, keeps timestamps and owners, validates every record, and offers one-click rollback. Delta migration keeps both systems aligned during cutover.
Leaving HubSpot? See HubSpot to Salesforce, HubSpot to Zoho CRM and HubSpot to Dynamics 365. Moving between HubSpot portals or into HubSpot, start at the HubSpot migration hub or read what the HubSpot importer keeps. For a quote, book a free scoping call.