When you create a sandbox, HubSpot copies supported assets and account configurations from your production account to provide a starting point for testing, training, and validating changes without affecting your live environment.
Not all assets and settings are copied to a sandbox. This article explains which assets are fully supported, partially supported, or unsupported during sandbox creation, along with any limitations or manual steps that may be required after the sandbox is created.
Learn more about sandbox assets eligible to be deployed to production and which sandbox assets are newly released, in beta, or in development.
Supported assets that can be copied to a sandbox
The assets listed in the tables below are copied to a sandbox when it's created.
CRM data and schema
| Asset type |
What's copied |
Please note: |
| Object records |
During sandbox creation, it's optional to copy up to 5,000 of the most recently updated contact records, along with up to 100 associated deals, 100 associated companies, and 100 associated tickets per contact. After sandbox creation, import up to 200,000 records for each record type. |
Event data on records is not copied. |
| Standard and custom object schemas |
Fully supported. |
- Record creation forms aren't copied.
- Custom object IDs and standard and custom object association IDs don't match between the production and sandbox accounts.
- If your account has integtrations that rely on object IDs, manually resolve ID mismatches.
|
| Object associations and labels |
Fully supported. |
- Standard and custom object association IDs don't match between the production and sandbox accounts.
- If your account has integtaions that rely on standard and custom object association IDs, manually resolve ID mismatches.
|
| Properties |
Most properties are copied, including calculated properties and rollup properties. |
The following properties aren't copied:
View and edit access settings aren't copied. |
| Property groups |
Default and custom property groups are copied. |
Property groups created by connected integrations aren't copied. |
| Property validation rules |
Fully supported. |
|
| Conditional property logic |
Fully supported. |
|
| Object pipeline and pipeline stages |
Pipelines, conditional logic rules, pipeline rules, and pipeline stages are fully supported. |
The following pipeline assets aren't copied:
|
| Record customization |
The following record customization assets are copied:
- Default team record customizations for standard objects and custom objects.
- Default cards from the card library.
|
The following record customization assets aren't copied:
-
Preview customization.
- Some custom cards and third-party app cards.
If a custom card depends on an unsupported asset type, for example it references a report which isn't supported, the customization will copy without this custom card containing the report. It will need to be recreated in the sandbox. |
| Index page customizations |
Views shared with everyone and team-based CRM views (BETA) are copied. |
If a view references a column or filter that is unsupported, that view will be skipped and flagged in your sandbox creation log with details. |
Automations
Please note: workflows and segments have cascading dependencies.
- If a supported workflow depends on an unsupported asset, even indirectly, it'll fail to copy. For example, a workflow that uses a segment that uses a lead scoring filter won't be copied, because lead scoring is not supported.
- To understand why an asset and any of its direct or indirect dependent assets failed to copy, review Failed assets in the sandbox creation activity log.
| Asset type |
What's copied |
Please note: |
| Workflows |
Workflows that depend on supported assets are copied. This includes workflows that use automated marketing emails, segments, object definitions, and forms. |
Workflows that depend on unsupported assets aren't copied. For example, a workflow that uses a segment containing a lead scoring filter, won't be copied. |
| Workflows with custom coded actions (Data Hub Professional and Enterprise only) |
Workflows that use custom coded actions are copied. |
If a workflows uses secrets, the secrets aren't copied. Manually set up secrets in the sandbox after creation. |
| Workflows with webhooks (Data Hub Professional and Enterprise only) |
Workflows that use webhooks are copied. |
Update webhook URLs pointing to production endpoints in the sandbox to avoid unintended production triggers during testing. |
Marketing
| Asset type |
What's copied |
Please note: |
| Automated marketing emails |
Automated (including those that use drag-and-drop and custom templates and modules), A/B test automated, and automated transactional emails are copied. |
Non-automated marketing emails and single send API emails aren't copied. |
| Branded assets |
Automated marketing emails, forms, segments, and workflows assigned to any brand, including non-default brands, are copied.
Brand assignments are preserved in the sandbox. |
|
| Email footer addresses |
Fully supported. |
|
| Email subscription types |
Partially supported. |
Visibility rules on subscription types aren't copied. |
| Forms |
Fully supported (including legacy forms). |
|
| Segments |
Partially supported.
|
- Some filters that depend on unsupported assets, such as lead scoring, feedback surveys, will cause the segment to fail to copy.
- Segments that fail to copy may also cause dependent workflows to fail.
- Review Failed assets in the sandbox creation activity log to understand why your segment failed to copy.
|
Sales
| Asset type |
What's copied |
Please note: |
| Playbooks |
Fully supported. |
If a playbook references an unsupported asset, manually add the missing dependency once the playbook is copied to the sandbox. |
| Sequences |
Steps, associated email templates, delay logic, automation settings, and referenced assets such as documents are copied. |
Enrolled contacts and performance data aren't copied. |
Unsupported assets that can't be copied to a sanbox
If an asset or configuration isn't listed above, it isn't copied to your sandbox at creation. This includes:
To get these assets in a sandbox account:
-
Manually recreate it: set up unsupported assets directly in your sandbox. Because sandboxes are isolated from production, anything created there won't affect the live account.
-
Review assets in beta and coming soon: review which asset types are in beta or coming soon.
Account Management
Marketing Hub
Enterprise
Sales Hub
Enterprise
Service Hub
Enterprise
Data Hub
Enterprise
Content Hub
Enterprise
