What HubSpot exports, and what it doesn’t
| Data | Native export | Note |
|---|---|---|
| Contacts, companies, deals, tickets, custom objects | Record export (CSV, XLSX) with “current property values and associations” | Up to 1,000 associated record IDs per association column; “All associated records” is CSV only |
| Property history | Current values only | History isn’t in record exports |
| Calls, emails, notes, meetings, tasks | Not in record exports | HubSpot points to per-record exports, activity reports or the engagements API |
| Files and attachments | Files tool: Export (ZIP) | Links to records aren’t in the ZIP |
| Workflows | Spreadsheet or image export | Description only, not logic |
HubSpot allows 300 exports per 24 hours and 3 at a time, and export links expire after 30 days.
Steps
- Export each object with all properties and associations, including Record ID.
- Pull activities from the API (calls, emails, meetings, notes, tasks), with their associated contact, company and deal IDs and timestamps.
- Pull files and their record links through the API if you need them attached to records. The ZIP alone won’t tell you where each file belongs.
- Prepare Salesforce: add a
HubSpot_ID__cexternal ID field on every object, create users, enable Set Audit Fields upon Record Creation to keep dates, and map pipelines to opportunity record types. - Load with Data Loader in order: Accounts, Contacts and Leads, Opportunities, contact roles, Tasks and Events, EmailMessage, then files. Upsert on
HubSpot_ID__c. - Reconcile: counts per object and a sample of timelines.
What the native tools do / where they stop
HubSpot’s exports cover records, and Salesforce’s Data Loader loads them. Neither one handles the middle step: turning HubSpot’s contact-company-deal associations into Salesforce lookups and junction records (AccountContactRelation, OpportunityContactRole), and turning engagements into Tasks, Events and EmailMessage. That middle step is why the original thread asked for a developer.
Where FlitStack AI fits
FlitStack AI pulls HubSpot records, associations, engagements and files through the API and loads them into Salesforce with audit fields and external IDs. See HubSpot to Salesforce or Salesforce migrations.