---
title: "Move HubSpot sandbox workflows and properties to production"
description: "How to move sandbox workflows and properties to production in HubSpot: what a standard sandbox deploy includes, what it leaves out, and the order to follow."
url: "https://jetstack.ai/answers/move-sandbox-workflows-properties-to-production/"
---

# How do I move sandbox workflows and properties to production in HubSpot?

To move sandbox workflows and properties to production, use HubSpot's deploy to production from a new standard sandbox (Enterprise, Super Admin). Select the workflows, include the connected properties, forms, segments and emails they need, resolve conflicts, and deploy up to 300 changes at a time. Only new assets deploy: edits to existing properties or workflows must be repeated in production by hand.

![](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’s deploy to production works from a **standard sandbox** to its own production account. It needs an Enterprise subscription and Super Admin permissions. Legacy standard sandboxes are no longer supported as of April 30, 2026, and deploy never worked from them, so you need a new standard sandbox.

| Asset                 | Deployable to production                                  | Not deployable                                                                                       |
| --------------------- | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Properties and groups | New custom properties, property groups, conditional logic | Edits to existing custom properties; edits to HubSpot-defined properties                             |
| Pipelines and objects | New pipelines, new custom objects, new associations       | Pipeline rules, the Automate tab, deal tags                                                          |
| Workflows             | New workflows that rely on new or supported assets        | Workflows already in both accounts, workflows with errors, workflows tied to unsupported assets      |
| Forms and segments    | New forms; new segments with supported filters            | Edits to existing ones; segments using import membership, form submission or marketing event filters |
| Emails                | New automated marketing emails                            | Regular marketing emails, blog/RSS emails, emails tied to sandbox-only subscriptions                 |

Other limits: up to 300 changes per deploy, no canceling once it starts, and integration-specific configuration isn’t included.

## How to move sandbox workflows and properties to production

1. **Build new, don’t edit.** In the sandbox, create new properties and workflows rather than editing ones that came from production. Edits won’t deploy.
2. **Start the deploy** from the sandbox and select the workflows.
3. **Include the connected assets.** HubSpot shows the properties, forms, segments and emails each workflow uses. Include them, or the workflow can’t deploy.
4. **Resolve conflicts** HubSpot flags, then review the full list.
5. **Deploy.** Keep each deploy under 300 changes.
6. **Redo the settings that don’t carry over.** Workflow folders and access, form and segment settings, email Settings tab values, and property access or sensitive-data settings all need setting again in production.
7. **Turn workflows on** after you check enrollment triggers and test with one record.

## Common mistakes

- **Editing a production copy in the sandbox** and expecting the change to deploy. It won’t.
- **Relying on surveys.** Surveys don’t copy into a standard sandbox, so workflows that use them don’t copy either.
- **Assuming the sandbox matches production.** It was copied at creation; production has moved on since. See [whether a HubSpot sandbox syncs with production](https://jetstack.ai/answers/hubspot-sandbox-sync-production).

## Where Jetstack AI fits

Jetstack AI’s [Portal reuse](https://jetstack.ai/roll-out) copies between any two portals you connect, so it also covers the cases sandbox deploy doesn’t: a test portal that isn’t a sandbox, or regular emails, pipeline automation and CMS assets. It deploys dependencies first, rewrites references to production IDs, and leaves workflows 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](https://jetstack.ai/docs/implementations/deploying/how-it-works).

## Sources

- [Deploy sandbox changes to production (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/deploy-sandbox-changes-to-production)
- [Assets eligible to be deployed to production (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/assets-eligible-to-be-deployed-to-production)
- [Set up a HubSpot standard sandbox account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account/set-up-a-hubspot-standard-sandbox-account)

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.

How do I move sandbox workflows and properties to production in HubSpot?

To move sandbox workflows and properties to production, use HubSpot's deploy to production from a new standard sandbox (Enterprise, Super Admin). Select the workflows, include the connected properties, forms, segments and emails they need, resolve conflicts, and deploy up to 300 changes at a time. Only new assets deploy: edits to existing properties or workflows must be repeated in production by hand.

Are deployed workflows switched on in production?

No. HubSpot sets workflows deployed from a sandbox to Off. Review them in production and turn them on yourself.

Can I deploy a change to a property that already exists in production?

No. HubSpot deploys only new supported assets. Edits to existing custom properties, groups, pipelines and HubSpot-defined properties aren't eligible, so make those changes in production directly.

Can I cancel a deployment once it starts?

No. HubSpot says a deployment can't be canceled after it starts, so review the connected assets and conflicts on the review screen first.
