On this page
What HubSpot supports natively
HubSpot doesn’t keep assets in step across portals. It offers four ways to copy them, each with a different license requirement.
| Route | License requirement | Permissions | What it copies |
|---|---|---|---|
| Multi-account management | An organization whose main account has an Enterprise subscription; connected accounts on Professional or Enterprise | Super Admin in both accounts | Automated marketing emails, forms, segments, workflows |
| Partner Portability (beta) | Partner Account subscription | Partner Admin in your account and the client’s; not a contractor; same region | Agent templates, workflows, forms, automated emails, segments, custom objects |
| Sandbox deploy | Enterprise subscription | Super Admin | New properties, pipelines, custom objects, forms, segments, automated emails, workflows |
| Design Manager copy | No specific tier stated | Same user email in both accounts | Templates, themes, modules |
How to pick a route for your accounts
| Your situation | Route |
|---|---|
| Your company runs several accounts under one Enterprise organization | Multi-account management |
| You’re a partner copying your own setup to a managed client | Partner Portability |
| You’re testing changes before releasing them to the same account | Sandbox deploy |
| You only need templates, themes or modules | Design Manager copy |
| Two unrelated accounts, or client to client | None natively; rebuild or use a third-party tool |
What to check before relying on a route
- Both sides’ subscriptions. For multi-account management, check the main account and every connected account.
- Asset coverage. Each route copies a short list. Pipelines, reports, CMS pages and regular emails aren’t on most of them.
- Settings that don’t copy. Multi-account copies of marketing emails leave custom subscription types for you to set up in the destination. Form copies leave submissions behind; segment copies leave records behind.
- How updates will flow. Every copy is independent, so plan who copies changes again and how you’ll record which version each account has.
Where Jetstack AI fits
Jetstack AI’s Portal reuse doesn’t depend on HubSpot’s account relationships: it copies between any two portals you connect, whatever their subscriptions, as long as the destination supports the feature. It doesn’t keep portals in sync either; each deployment is a separate, reviewed copy. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. 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. See the supported asset types.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Copy partner assets to client accounts (HubSpot Knowledge Base)
- Deploy sandbox changes to production (HubSpot Knowledge Base)
- Copy a template or theme to another HubSpot account (HubSpot Knowledge Base)
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