- Knowledge Base
- Account & Setup
- Account Management
- Assets eligible to be deployed to production
Assets eligible to be deployed to production
Last updated: October 1, 2025
Available with any of the following subscriptions, except where noted:
-
Marketing Hub Enterprise
-
Sales Hub Enterprise
-
Service Hub Enterprise
-
Data Hub Enterprise
-
Content Hub Enterprise
Once you have created your standard sandbox and tested changes, you can deploy the changes to production. Below, learn which assets can be deployed, and which aren't eligible to be deployed.
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:
|
|
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:
|
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:
|
|
|
New object pipelines, including:
|
|
|
Applicable to new custom objects:
|
Sandbox edits to custom objects that exist in production won't be listed as eligible. |
|
Workflows | Workflows newly created in sandbox and not yet present in production that rely on:
|
The following workflows won’t be listed as eligible to deploy:
|
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:
|
Lists | Active and static lists newly created in sandbox, and not yet present in production if they use filters based on:
|
The following lists won’t be listed as eligible to deploy:
|
Legacy forms | Forms newly created in sandbox with the legacy form editor and not yet present in production. | The following legacy forms won’t be listed as eligible for deployment:
|