On this page
What HubSpot supports natively
HubSpot doesn’t migrate one portal into another. Its export guide says you can’t merge all data between HubSpot accounts; you export from one account, then import objects or recreate data in the other.
| Native tool | Moves | Doesn’t move |
|---|---|---|
| Import | Records and activities (calls, meetings, notes, tasks, emails) with associations; association labels on Professional or Enterprise | Updates to existing emails, meetings, notes or tasks |
| Multi-account management, Partner Portability | Workflows, forms, segments, automated emails between linked accounts | Records |
| Design Manager copy | Templates, themes, modules | Page content |
What a portal migrator adds
A migrator connects to both portals and moves data through HubSpot’s APIs, instead of you shuttling spreadsheets. The best-known is datawarehouse.io’s HubSpot to HubSpot Migrator, part of its Portal Migration Suite. According to the vendor, it:
- Moves contacts, companies, leads, deals, tickets, custom objects and line items.
- Moves engagements (meetings, tasks, notes, calls, emails) and files.
- Preserves associations, including custom association labels.
- Moves pipelines, custom properties, segments and owners, plus forms, workflows (beta) and marketing emails at higher tiers.
- Requires a Super Admin connection on both portals and only reads the source.
The same suite has a Schema Replicator that copies configuration without records.
How to decide whether you need one
| Situation | Route |
|---|---|
| A few thousand contacts and companies, no activity history needed | HubSpot export and import |
| Records, activities and associations must all survive | A portal migrator |
| Only configuration moves (a new client, a new region) | A configuration copy tool or HubSpot’s native copy routes |
| Two portals merging into one | A migrator for records, plus design decisions no tool makes for you |
Whatever you choose, run a test migration first and reconcile counts. The steps are in how to avoid losing data in a HubSpot-to-HubSpot migration.
Where Jetstack AI fits
Jetstack AI isn’t a records migrator: it doesn’t move contacts, deals or activities. Its Portal reuse copies configuration, including workflows, lists, forms, emails, pipelines, properties, custom objects and CMS assets, with dependencies and references remapped, so it pairs with a records tool in a full migration. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See the supported asset types.
Sources
- Export your content and data (HubSpot Knowledge Base)
- Import objects (HubSpot Knowledge Base)
- HubSpot to HubSpot Migrator (datawarehouse.io)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Copy & migrate between portals
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse