On this page
What HubSpot supports natively
HubSpot copies workflows between accounts in three cases. Each one depends on how the accounts are related.
| Route | Between | Workflow-specific limits |
|---|---|---|
| Partner Portability (beta) | Your partner account → a managed client | Workflows built in Agent Hub are excluded; dependencies such as the enrolling form must copy too |
| Multi-account management | Accounts in one organization | Super Admin in both accounts; missing custom properties are created in the destination |
| Sandbox deploy | Standard sandbox → its production account | Only new workflows; workflows already in both accounts, or with errors, are excluded; deployed workflows are set to Off |
Within one portal, you can clone a workflow. That’s a different job: the clone points at the same lists, emails and properties as the original.
How to move a workflow between unrelated portals
If the portals aren’t linked, you have three options.
| Option | Good for | Watch out for |
|---|---|---|
| Rebuild by hand | One or two simple workflows | Settings hidden inside actions and branches are easy to miss |
| Script it with the workflows API (v4, beta) | Teams with a developer | The definition contains source IDs for lists, emails, users and stages that you must replace |
| Third-party tool | Many workflows, or workflows with many dependencies | Check how it handles references and existing assets |
Whichever you pick, the order is the same:
- List what the workflow uses: properties, lists or segments, forms, emails, owners, pipeline stages and other workflows it enrolls into.
- Create or match those in the destination first. Keep property internal names and dropdown option values identical.
- Recreate the workflow and point every reference at the destination’s version.
- Review custom code and webhook actions. They often contain hard-coded portal IDs or tokens.
- Test with one record, then switch it on.
If a property the workflow uses isn’t in the destination, see what happens when a referenced property doesn’t exist.
Where Jetstack AI fits
Jetstack AI’s Portal reuse imports a workflow with its supported dependencies, deploys them in dependency order, and rewrites list, email, owner, stage and property references for the destination. Workflows arrive inactive so you can review them first. 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 workflow reference.
Sources
- Copy partner assets to client accounts (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Workflows (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