Skip to content
Book a build

How can I clone a HubSpot workflow from a UAT account to production?

To clone a HubSpot workflow from a UAT account to production, first check what the UAT account is. If it's a standard sandbox of production, use deploy to production: it handles new workflows and sets them to Off. If it's a separate account, HubSpot only copies between them inside a multi-account organization. Otherwise rebuild the workflow, script it with the workflows API, or use a tool.

On this page

What HubSpot supports natively

The right route depends on what your UAT account is.

UAT account is…Native routeLimits
A standard sandbox of productionDeploy to productionEnterprise, Super Admin; only new workflows; up to 300 changes per deploy; workflows arrive Off
A legacy sandboxNoneLegacy standard sandboxes are no longer supported as of April 30, 2026; create a new standard sandbox
A separate account in the same multi-account organizationMulti-account asset copyingEnterprise main account; Super Admin in both accounts
A separate, unlinked accountNoneRebuild, use the beta workflows API, or a third-party tool

How to promote a workflow from UAT to production

  1. Build it as new in UAT. Sandbox deploy ignores edits to workflows that already exist in both accounts.
  2. Keep the dependencies portable. Use properties, lists and emails that either deploy with the workflow or already exist in production with the same internal names and option values.
  3. Avoid record IDs. Owners, stages and lists have different IDs in production. Reference them through the workflow’s own pickers, not hard-coded values in custom code.
  4. Deploy or copy with the route that fits your account type, including the connected assets HubSpot lists.
  5. Redo the settings that don’t carry over: folders, access, brand and campaign labels for sandbox deploys.
  6. Check enrollment and re-enrollment, then test with one production record before switching it on.

Common mistakes

  • Testing on stale data. A sandbox is copied at creation and doesn’t keep up with production; see whether a HubSpot sandbox syncs with production.
  • Forgetting suppression lists. They’re easy to leave behind and they stop the wrong records enrolling.
  • Turning it on during business hours without a test record. A workflow enrolls everyone who already meets its trigger.

Where Jetstack AI fits

Jetstack AI’s Portal reuse copies workflows from any connected UAT, test or sandbox portal to production, with their dependencies deployed first and references rewritten to production IDs. Workflows arrive inactive for review. 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. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See how deployment works.

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.

How can I clone a HubSpot workflow from a UAT account to production?

To clone a HubSpot workflow from a UAT account to production, first check what the UAT account is. If it's a standard sandbox of production, use deploy to production: it handles new workflows and sets them to Off. If it's a separate account, HubSpot only copies between them inside a multi-account organization. Otherwise rebuild the workflow, script it with the workflows API, or use a tool.

Can I update an existing production workflow from UAT?

Not with sandbox deploy, which only deploys new workflows. Make the change in production by hand, or replace the workflow with a new version and retire the old one.

Can a sandbox be part of a multi-account organization?

No. HubSpot says multi-account management can't be set up in sandbox or trial accounts.

Will record IDs match between UAT and production?

No. HubSpot notes contact, company, deal, ticket and custom object IDs differ between sandbox and production. Don't hard-code record IDs in workflow actions or custom code.