Skip to content

Assets eligible to be deployed to production (BETA)

Last updated: June 5, 2025

Available with any of the following subscriptions, except where noted:

Marketing Hub   Enterprise
Sales Hub   Enterprise
Service Hub   Enterprise
Operations Hub   Enterprise
Content Hub   Enterprise

Once you have set up your standard sandbox, learn what objects and assets will 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 object

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.
  • Pipeline settings:
    • Conditional stage properties.
    • 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 sandbox and not yet present in production that rely on:
  • New legacy forms.
  • New lists.
  • New automated marketing emails.
  • Properties.
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 in the Settings tab aren't copied as part of the deployment and must be reconfigured in the production account.

Lists Active and static lists newly created in sandbox, and not yet present in production if they use filters based on:
  • Object properties.
  • List membership.
  • Workflow enrollment.
Any of the following marketing interaction filters:
  • Ads interactions.
  • CTAs.
  • Marketing campaigns.
  • Marketing emails.
  • Media interactions.
  • Page view.
The following lists won’t be listed as eligible to deploy:
  • Sandbox edits to lists that exist in production.
  • Lists that use filters based on:
    • Import membership.
    • Form submission.
    • Behavioral events (Legacy).
    • CTAs (Legacy).
    • Marketing events.
List settings aren't copied as part of the deployment and must be reconfigured in the production account.
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:
Configurations in the Options tab aren't copied as part of the deployment and must be reconfigured in the production account.

Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.
OSZAR »