Once you have created your standard sandbox and tested changes, you can deploy eligible supported assets to production. Learn which assets can be deployed, and which aren't eligible to be deployed. You can also review this information in the Deployment behaviors banner as you're setting up a deploy.
Please note: only new supported assets can be deployed to production. Edits to supported assets that were copied from production to sandbox can't be deployed to production.
Supported assets that can be deployed to production
| Asset type |
What will get deployed |
What won't get deployed |
| Standard and custom objects |
New custom properties including:
- Property details
- Field type
- Rules
|
- For new custom properties, the following settings aren’t copied and must be manually reconfigured in production:
- Manage access
- Sensitive Data settings
- The following properties can’t be deployed, and won’t be listed as eligible:
- Edits to HubSpot-defined properties
- Sandbox edits to custom properties that exist in production won’t be listed as eligible
|
| New property groups, including new custom properties belonging to the group. |
Sandbox edits to property groups that exist in production won't be listed as eligible.
|
| New property conditional logic, including:
- Controlling property
- Dependent properties and required field logic.
|
Sandbox edits to property conditional logic that exist in production won't be listed as eligible. |
| New object associations between two standard objects, a standard object and a custom object, or two custom objects, including:
- Single label logic
- Pair of labels logic
- One-to-many label limit logic.
- Custom association limits and custom association label limits.
|
- Edits to standard object associations copied to the sandbox during the build process.
- Sandbox edits to object associations that exist in production won’t be listed as eligible.
|
| New object pipelines, including:
- Stage name
- Probability
- Conditional stage properties
|
- Pipeline settings:
- Pipeline rules
- Automate tab
- Deal tags tab
- Sandbox edits to object pipelines that exist in production won't be listed as eligible.
|
| Applicable to new custom objects:
- Object name
- Object description
- Primary display property
- Secondary display properties
|
Sandbox edits to custom objects that exist in production won't be listed as eligible. |
| Workflows |
Workflows newly created in the sandbox and not yet present in production that rely on:
- New forms
- New segments
- New automated marketing emails
- Object configurations
Workflows deployed to production accounts will automatically be set to Off. |
The following workflows won’t be listed as eligible to deploy:
- Workflows that are present in both production and sandbox accounts.
- Workflows that have errors, or changes needed in the sandbox.
- Workflows that have a direct or indirect connection with asset types not available to deploy yet (e.g., workflows that rely on feedback surveys)
Settings to organize workflows (e.g., folders, access, brand, and campaign labels) aren't copied and must be manually reconfigured in the production account. |
| Automated marketing emails |
Automated marketing emails newly created in sandbox and not yet present in production. |
The following marketing emails can’t be deployed and won’t be listed as eligible for deployment:
Configurations on the Settings tab aren't copied as part of the deployment and must be reconfigured in the production account.
|
| Segments |
Active and static segments newly created in the sandbox, and not yet present in production if they use filters based on:
- Object properties
- Segment membership
- Workflow enrollment
Any of the following marketing interaction filters:
- Ads interactions
- CTAs
- Marketing campaigns
- Marketing emails
- Media interactions
- Page view
|
The following segments won’t be listed as eligible to deploy:
- Sandbox edits to segments that exist in production
- Segments that use filters based on:
-
- Form submission
- Behavioral events (Legacy)
- CTAs (Legacy)
- Marketing events
Segment settings aren't copied as part of the deployment and must be reconfigured in the production account. |
| Forms |
Forms newly created in sandbox and not yet present in production. |
The following forms won’t be listed as eligible for deployment:
- Sandbox edits to forms that exist in production
Form settings won't be copied as part of the deployment and may need to be reconfigured in the production account. |
Account Management
Marketing Hub
Enterprise
Sales Hub
Enterprise
Service Hub
Enterprise
Data Hub
Enterprise
Content Hub
Enterprise
