What HubSpot gives you natively
HubSpot’s own words: “there is no way to merge all the data between HubSpot accounts,” and “the best way to move assets between accounts is to export your data from a HubSpot account” and import it into the other one.
| What | Native route | Where it stops |
|---|---|---|
| Automated marketing emails, forms, segments, workflows | Copy to another account (multi-account management) | Needs an Enterprise main account, Pro or Enterprise connected accounts and Super Admin in both; CRM records and form submissions aren’t copied |
| Templates and themes | Design Manager copy | Content only |
| Contacts, companies, deals, tickets | Export, then import | Exports include properties and associations (up to 1,000 associated IDs per column) |
| Calls, emails, notes, meetings, tasks | Not in record exports | HubSpot points to per-record exports, activity reports or the engagements API |
| Files | Files tool ZIP export | Links to records must be rebuilt |
| Custom objects | Export, then import | Schema must be recreated first (Enterprise) |
Steps
- Freeze the schema in the source: properties, pipelines, association labels, custom objects.
- Recreate the schema in the destination. Copy workflows and forms with multi-account management if you qualify, which also creates missing properties as dependencies.
- Add a “Source record ID” property on every object in the destination.
- Export records with associations. HubSpot allows 300 exports per 24 hours, and download links expire after 30 days.
- Import companies, then contacts, then deals and tickets, then custom objects, resolving associations through the source IDs.
- Move activities through the API. Record exports don’t include them.
- Rebuild owners, teams and permissions, then switch workflows on.
The part HubSpot’s docs skip
Activity history is the hard part of a portal-to-portal move. Exports carry records and associations, not timelines. So a CSV-only approach gets you every contact with an empty timeline. If sales relies on call notes and email history, the move needs the engagements API.
Where FlitStack AI fits
FlitStack AI runs HubSpot-to-HubSpot migrations through the API: records, associations, activities and files, with original timestamps, hash-based validation and rollback. See HubSpot migrations or talk to us.