Assets Eligible for HubSpot Production Deployment

Understanding which assets are eligible to be deployed to production in Hubspot is essential when you rely on sandboxes, QA environments, or complex approval workflows. This guide explains exactly which asset types can move between environments, and how deployment eligibility works across key tools.

How HubSpot Deployment Eligibility Works

Not every change you make in your account can be deployed from a sandbox or testing environment. The deployment feature in the HubSpot platform supports a specific list of asset types, each with clear rules around what is included or excluded.

At a high level, keep in mind:

• Only supported assets can be deployed to production.
• Certain related settings or linked items may be excluded.
• Some tools require manual configuration in the production account after deployment.

If you work in an agency or manage multiple portals, you may also want a broader operational strategy. A consulting partner such as Consultevo can help design scalable deployment and governance processes around your HubSpot setup.

HubSpot CRM & Data Assets Eligible for Deployment

Several core CRM and data assets in HubSpot can be deployed from a sandbox or testing portal into a live environment.

Properties

Custom properties are frequently part of a deployment plan. When deploying properties, eligible items typically include:

• Object properties (for contacts, companies, deals, tickets, and custom objects).
• Property groups that organize your fields.
• Field definitions such as label, description, and field type.

However, you may need to reconfigure certain object-specific settings manually in production if they are not part of the deployment scope.

CRM Pipelines and Stages

Sales and service processes depend heavily on pipelines. Deployment typically supports:

• Deal pipelines and their stages.
• Ticket pipelines and their statuses.
• Basic configuration such as stage names and order.

Automation tied to these pipelines, such as workflows, is handled separately and should be validated after deployment inside your HubSpot production account.

Custom Objects

For advanced setups, custom objects can be included as deployable assets. In general, you can move:

• Custom object definitions.
• Associated properties for custom objects.
• Basic association configurations.

Any data records for these objects are not part of the configuration deployment and must be created or migrated using imports or integrations.

HubSpot Marketing Assets Eligible for Deployment

Marketing teams often test and refine assets in sandboxes before going live. The following HubSpot marketing items are usually eligible for deployment.

Forms and CTAs

Lead capture components are central to many accounts. Deployment typically includes:

• Form structures, including fields, labels, and options.
• Simple form styling and basic options.
• Call-to-action (CTA) configurations, where supported.

Form submission data, historical analytics, and advanced styling tied to external themes may require additional setup post-deployment.

Emails and Templates

Email tools in HubSpot benefit from test environments for layout and logic. Assets that may be deployable include:

• Marketing email templates.
• Reusable email modules and layouts.
• Certain configuration settings for email assets.

Sending settings, subscription types, and live audience targeting rules must be reviewed in production before sending any message.

Landing Pages and Website Assets

Content creation often starts in a sandbox. Deployment support can include:

• Landing page templates and cloned layouts.
• Website page templates used for new content.
• Modules and theme elements where designated as deployable.

Existing live pages and SEO settings such as canonical URLs, domain assignments, and redirects should always be confirmed directly in the production HubSpot portal.

HubSpot Automation Assets Eligible for Deployment

Automation is powerful but risky if not tested. That is why deployment eligibility rules are important for workflows and related automation assets in HubSpot.

Workflows

Workflows are prime candidates for moving from a testing to a production environment. When supported, deployment may include:

• Enrollment triggers and lists configured as criteria.
• Workflow actions such as property updates, task creation, or internal notifications.
• Delays and branching logic such as if/then branches.

After deploying workflows, you should:

1. Review enrollment triggers in the production portal.
2. Confirm referenced lists, properties, and pipelines exist.
3. Turn workflows on only after validation.

Sequences and Sales Automation

Sales teams using sequences in HubSpot can sometimes deploy configuration-based assets such as sequence steps and templates. Post-deployment, align user permissions, inbox connections, and from-address settings in the live account.

HubSpot Content & Knowledge Management Assets

Some content and knowledge tools support deployment to maintain consistent experiences across environments.

Knowledge Base Assets

Where enabled, deployment can support certain configuration or template elements for the knowledge base, such as layouts or modules. Article content itself may need manual migration or review to ensure accurate URLs, categories, and access control in production.

Blog and Content Settings

For blogs, parts of the structural setup may be eligible:

• Blog templates and some theme modules.
• Basic layout and design elements used across posts.

Individual blog posts, SEO metadata, and schedules generally require direct creation or publishing in the live HubSpot environment to avoid accidental releases.

Assets Not Eligible for HubSpot Deployment

While many items can move between environments, certain elements are usually excluded from deployment in HubSpot and must be configured directly in the production portal.

• User accounts, teams, and permission sets.
• Connected inboxes, domains, and external integrations.
• Billing settings, subscription levels, and payment configuration.
• Actual CRM records such as contacts, companies, deals, and tickets.

These limitations protect sensitive data and account-level access, ensuring that only configurations and structures move across environments.

Best Practices for Managing HubSpot Deployments

To get predictable results when moving assets eligible for deployment, follow these practices:

1. Maintain clean naming conventions. Use consistent names for pipelines, properties, and workflows to avoid confusion between environments.
2. Create a deployment checklist. Document which HubSpot assets are deployable and which require manual configuration.
3. Test thoroughly. In your sandbox, validate forms, workflows, and email templates before any deployment process.
4. Review dependencies. Make sure referenced lists, properties, and pipelines exist in the destination account and match expectations.
5. Keep stakeholders aligned. Coordinate with operations, marketing, and sales teams before enabling new assets in production.

Where to Learn More About HubSpot Asset Eligibility

For the most precise and current list of assets eligible for deployment in HubSpot, always consult the official documentation on the HubSpot Knowledge Base. You can review full details here: HubSpot assets eligible to be deployed to production.

Because the platform evolves frequently, new tools and asset types may be added to the deployment system over time. Revisit the official page before planning any large rollout or restructuring project.

By understanding exactly which assets can move between environments, and by pairing this with careful governance, you can maintain a stable, scalable, and predictable HubSpot implementation from sandbox to production.

Need Help With Hubspot?

If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.

Scale Hubspot

“`