On this page
What HubSpot supports natively
The right route depends on what your UAT account is.
| UAT account is… | Native route | Limits |
|---|---|---|
| A standard sandbox of production | Deploy to production | Enterprise, Super Admin; only new workflows; up to 300 changes per deploy; workflows arrive Off |
| A legacy sandbox | None | Legacy standard sandboxes are no longer supported as of April 30, 2026; create a new standard sandbox |
| A separate account in the same multi-account organization | Multi-account asset copying | Enterprise main account; Super Admin in both accounts |
| A separate, unlinked account | None | Rebuild, use the beta workflows API, or a third-party tool |
How to promote a workflow from UAT to production
- Build it as new in UAT. Sandbox deploy ignores edits to workflows that already exist in both accounts.
- 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.
- 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.
- Deploy or copy with the route that fits your account type, including the connected assets HubSpot lists.
- Redo the settings that don’t carry over: folders, access, brand and campaign labels for sandbox deploys.
- 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
- Deploy sandbox changes to production (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
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