---
title: "Move a workflow to another HubSpot portal"
description: "Whether you can move a workflow to another HubSpot portal: the native routes, the accounts they work between, and what to do when the portals aren't linked."
url: "https://jetstack.ai/answers/move-workflow-to-another-hubspot-portal/"
---

# 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.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

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:

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](https://jetstack.ai/answers/referenced-property-missing-target-portal).

## Where Jetstack AI fits

Jetstack AI’s [Portal reuse](https://jetstack.ai/roll-out) 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](https://jetstack.ai/docs/implementations/asset-types/workflows).

## Sources

- [Copy partner assets to client accounts (HubSpot Knowledge Base)](https://knowledge.hubspot.com/partner-tools/copy-partner-assets-to-client-accounts)
- [Copy assets to another HubSpot account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/copy-assets-to-another-hubspot-account)
- [Assets eligible to be deployed to production (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/assets-eligible-to-be-deployed-to-production)
- [Workflows (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/workflows)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

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](https://jetstack.ai/roll-out)

On this page

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.
