On this page
What HubSpot supports natively
HubSpot has three copy routes. Each one works only between accounts HubSpot already links together.
| Route | Between | What it copies | Main limits |
|---|---|---|---|
| Partner Portability (beta) | A Solutions Partner’s own account and its managed clients | Agents, workflows, forms, automated marketing emails, segments and custom objects, plus their required connected assets | Beta access, Partner Admin permissions, accounts in the same region |
| Multi-account management | Accounts in one multi-account organization | A short list of supported asset types | Needs the organization’s subscription and Super Admin on both sides |
| Sandbox deploy | A sandbox and its own production account | Supported changes made in the sandbox | Only to that production account |
If the two portals aren’t linked in one of these ways (two different clients, or an old portal and a new one), HubSpot has no built-in way to clone a workflow and its properties.
How to clone workflows and properties between portals
- List the dependencies first. For each workflow, note the properties it reads or sets, the lists or segments it enrolls from, the emails it sends, the owners it assigns and the pipeline stages it moves deals into.
- Create or match the properties in the destination. Keep the same internal names and the same option values for dropdown and checkbox properties, or branches that compare values will stop matching.
- Copy the supporting assets (lists, emails, pipelines) before the workflow that uses them.
- Recreate the workflow and remap every reference to the destination’s IDs: each property, list, email, owner and stage.
- Review it before switching it on. Check enrollment triggers and re-enrollment settings, then test with one record.
Doing this by hand is reliable for one or two workflows. It gets slow and error-prone once a setup has dozens of connected workflows, which is when a dependency-aware tool pays for itself.
What to look for in a tool
- Dependency discovery: it finds the properties, lists, emails and other assets a workflow needs, not just the workflow.
- Reference remapping: it rewrites IDs for the destination portal instead of copying source IDs.
- Property reconciliation: it creates missing properties and adds missing dropdown options rather than duplicating properties that already exist.
- Per-asset results: it tells you exactly what was created, matched or skipped, so you can check before activating anything.
Tools in this space include Supered’s Package Builder, datawarehouse.io’s HubSpot-to-HubSpot Migrator and Jetstack AI. Compare them on these four points for the assets you actually need to move.
Where Jetstack AI fits
Jetstack AI’s Portal reuse imports a workflow together with its supported dependencies into a library, then deploys it to one destination portal or several, reviewing each portal’s mappings. It matches assets that already exist there, rewrites references to destination IDs, and reconciles properties and pipeline stages, then reports the result for every asset. 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.
Sources
- Copy partner assets to client accounts (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Deploy sandbox changes to production (HubSpot Knowledge Base)
- Importing dependencies (Jetstack AI documentation)
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