Skip to content
Book a build

Which HubSpot assets can't be migrated between portals?

No native HubSpot route migrates regular marketing emails, website and landing pages, reports, dashboards, pipelines between unrelated portals, or integrations. Purchased Marketplace themes and modules can only be transferred through HubSpot Support. History never migrates as configuration: form submissions, segment membership, workflow enrollment and email analytics stay behind. Some settings, like deal rotation, can't be recreated through the API at all.

On this page

What HubSpot supports natively

HubSpot’s cross-account copy features each cover a short list. Anything outside these lists has no native route.

Native routeCovers
Multi-account managementAutomated marketing emails, forms, segments, workflows
Partner Portability (beta)Agent templates, workflows, forms, automated marketing emails, segments, custom objects
Sandbox deploy (to its production only)New properties, pipelines, custom objects, forms, segments, automated emails, workflows
Design Manager copyTemplates, themes, modules (files only)

HubSpot’s own export guide says plainly that you can’t merge all data between HubSpot accounts.

Assets with no native migration route

AssetWhat happens natively
Regular (non-automated) marketing emailsNot covered by multi-account copy or sandbox deploy
Website pages, landing pages, blog postsHTML export exists, but HubSpot describes it as for moving content to another platform
Reports and dashboardsNo cross-account copy; clone works within one account only
Pipelines between unrelated accountsOnly sandbox deploy, and only to its own production
Purchased Marketplace themes and modulesCan exist in one account at a time; transfer goes through HubSpot Support
@hubspot and @marketplace theme foldersCan’t be copied between accounts
Integrations and connected appsReauthorize in each account

What never migrates as configuration

Copying a definition doesn’t copy its history. HubSpot notes form copies don’t include submissions and segment copies don’t include their records. The same applies to workflow enrollment history, email performance and page analytics. Records themselves move only through export and import or a records migration tool.

Settings even tools struggle with

These are the limits Jetstack AI has hit when recreating assets through HubSpot’s APIs:

  • Deal rotation on pipeline stages can’t be created through the API.
  • Calculated and rollup properties read other properties by internal name, so they must be created after everything they reference, in the right order. Jetstack handles that ordering for you (see below).
  • Score properties depend on the source portal’s scoring rules, so map them to a score property in the destination.
  • Behavioral event definitions used as workflow triggers must exist in the destination first.
  • Custom code and webhook actions copy as written, including any hard-coded portal IDs or tokens.

Before a full move, see whether you can clone an entire HubSpot portal.

Where Jetstack AI fits

Jetstack AI’s Portal reuse covers many of the assets HubSpot doesn’t, including regular emails, pages, templates, blog posts, HubDB tables, pipelines, reports and dashboards. It copies calculated properties with their formulas remapped to the destination, and copies rollup properties too: it reads each supported rollup definition (count, sum, min, max, average, earliest or latest date) with the Chrome extension, creates the properties and association labels it depends on first, and checks the result by reading it back. A rollup shape it can’t copy fails with an explicit reason, it’s never copied as an ordinary property, and every asset that reads it is held back rather than deployed broken. Themes aren’t supported, some types need the Chrome extension, and it doesn’t move CRM records. 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. Pages and HubDB tables must be unpublished before they can be rolled back. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. Where Portal reuse doesn’t cover an asset, such as a score property or an unsupported rollup, build it in the destination with Jetstack AI Projects instead: you describe it in a brief, approve Jetty’s plan and then the deployment, and get a receipt read back from HubSpot. Projects doesn’t build themes, CMS pages or custom-code actions, and it’s currently in limited release. See the known limitations and what Projects can build.

Sources

Checked October 30, 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

Copy & migrate between portals

Related questions.

Which HubSpot assets can't be migrated between portals?

No native HubSpot route migrates regular marketing emails, website and landing pages, reports, dashboards, pipelines between unrelated portals, or integrations. Purchased Marketplace themes and modules can only be transferred through HubSpot Support. History never migrates as configuration: form submissions, segment membership, workflow enrollment and email analytics stay behind. Some settings, like deal rotation, can't be recreated through the API at all.

Can HubSpot merge two accounts?

No. HubSpot's export documentation says you can't merge all data between HubSpot accounts. You export from one account and import or recreate in the other.

Do integrations move with a migration?

No. Connected apps are authorized per account. Reinstall and reconnect each integration in the destination and check its field mappings.

Why can't deal rotation be copied?

HubSpot's API doesn't support creating deal rotation settings, so no tool can recreate them through the API. Set them up again in the destination.