Skip to content
Book a build

Can you copy or move a workflow to another HubSpot portal?

Yes, but HubSpot only copies a workflow to another portal when the two accounts are linked: a partner account and its managed client, accounts in one multi-account organization, or a sandbox and its production account. HubSpot has no move: the original stays in the source. Between unrelated portals, rebuild the workflow by hand, script it with the beta workflows API, or use a third-party tool.

On this page

What HubSpot supports natively

HubSpot copies workflows between accounts in three cases. Each one depends on how the accounts are related.

RouteBetweenWorkflow-specific limits
Partner Portability (beta)Your partner account → a managed clientWorkflows built in Agent Hub are excluded; dependencies such as the enrolling form must copy too
Multi-account managementAccounts in one organizationSuper Admin in both accounts; missing custom properties are created in the destination
Sandbox deployStandard sandbox → its production accountOnly 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.

OptionGood forWatch out for
Rebuild by handOne or two simple workflowsSettings hidden inside actions and branches are easy to miss
Script it with the workflows API (v4, beta)Teams with a developerThe definition contains source IDs for lists, emails, users and stages that you must replace
Third-party toolMany workflows, or workflows with many dependenciesCheck how it handles references and existing assets

Whichever you pick, the order is the same:

  1. List what the workflow uses: properties, lists or segments, forms, emails, owners, pipeline stages and other workflows it enrolls into.
  2. Create or match those in the destination first. Keep property internal names and dropdown option values identical.
  3. Recreate the workflow and point every reference at the destination’s version.
  4. Review custom code and webhook actions. They often contain hard-coded portal IDs or tokens.
  5. 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

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

Copy & migrate between portals

Related questions.

Can you copy or move a workflow to another HubSpot portal?

Yes, but HubSpot only copies a workflow to another portal when the two accounts are linked: a partner account and its managed client, accounts in one multi-account organization, or a sandbox and its production account. HubSpot has no move: the original stays in the source. Between unrelated portals, rebuild the workflow by hand, script it with the beta workflows API, or use a third-party tool.

Does the copied workflow stay linked to the original?

No. HubSpot says an asset copied to a client account becomes independent from the original. Changes to the source workflow don't reach the copy; you copy it again.

Do enrolled records move with the workflow?

No. Only the definition is copied. Enrollment history and currently enrolled records stay in the source portal.

Is the copied workflow switched on?

Treat it as off until you review it. HubSpot sets workflows deployed from a sandbox to Off, and checking enrollment triggers before activation is good practice on every route.