---
title: "Does a HubSpot sandbox sync with production? · Jetstack AI"
description: "Whether a HubSpot sandbox syncs with production: what a standard sandbox copies at creation, what never refreshes, and how changes flow back to production."
url: "https://jetstack.ai/answers/hubspot-sandbox-sync-production/"
---

# Does a HubSpot sandbox sync with production?

No. HubSpot's documentation describes no sandbox sync from production after creation. A standard sandbox copies supported production assets once, when you create it, plus up to 5,000 contacts if you choose. Later production changes don't reach it. Changes flow one way only, from sandbox to production, through deploy. Super Admins removed from production are removed from the sandbox; new ones must be added by hand.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

On this page

## What HubSpot does natively

A standard sandbox is a copy taken once. Here’s what HubSpot copies when you create it, and what happens afterwards.

| At creation                                                                                            | Copied?                                            |
| ------------------------------------------------------------------------------------------------------ | -------------------------------------------------- |
| Supported production assets (“Copy production assets” is on by default)                                | Yes                                                |
| Design Manager templates and modules                                                                   | Yes                                                |
| Sequences (steps, templates, delays)                                                                   | Yes, without enrolled contacts or performance data |
| Automated marketing emails, forms, workflows that depend on supported assets                           | Yes                                                |
| Your 5,000 most recently updated contacts, with up to 100 associated deals, companies and tickets each | Optional                                           |
| Super Admins, Partner admins with elevated access, Developer tools users                               | Yes                                                |
| Website, landing and blog pages                                                                        | No                                                 |
| Reports and dashboards                                                                                 | No                                                 |
| Integrations and connected apps                                                                        | No                                                 |
| Surveys, and workflows that use them                                                                   | No                                                 |
| Non-automated marketing emails                                                                         | No                                                 |

HubSpot’s rule: if an asset isn’t on its supported list, it isn’t copied.

**After creation**, HubSpot documents only one direction: deploy from sandbox to production, up to 300 changes at a time. It doesn’t describe pulling later production changes into the sandbox.

## How to keep a sandbox close to production

1. **Note the creation date.** Anything changed in production since then isn’t in the sandbox.
2. **Recreate production changes you need for testing** in the sandbox by hand, or create a fresh standard sandbox when it has drifted too far.
3. **Import test records** when you need more or different data.
4. **Connect integrations to their sandbox versions,** not production, so tests don’t write live data.
5. **Add new Super Admins** to the sandbox yourself.

## Common mistakes

- **Testing a change against an out-of-date setup,** then deploying it into a production account that has moved on.
- **Editing production copies in the sandbox.** Only new assets deploy; see [how to move sandbox workflows and properties to production](https://jetstack.ai/answers/move-sandbox-workflows-properties-to-production).
- **Hard-coding record IDs.** They differ between the two accounts.

## Where Jetstack AI fits

Jetstack AI doesn’t keep a sandbox in sync with production; no deployment is a sync. Its [Portal reuse](https://jetstack.ai/roll-out) can copy selected assets in either direction between any two connected portals, production into a sandbox included, with references remapped and existing assets matched by name. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See [how deployment works](https://jetstack.ai/docs/implementations/deploying/how-it-works).

## Sources

- [Set up a HubSpot standard sandbox account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account/set-up-a-hubspot-standard-sandbox-account)
- [Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/production-assets-eligible-to-copy-to-a-sandbox)
- [Deploy sandbox changes to production (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/deploy-sandbox-changes-to-production)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

Copy & migrate between portals

## Take a proven setup to the next portal.

Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.

[Explore Portal reuse](https://jetstack.ai/roll-out)

On this page

Copy & migrate between portals

## Related questions.

Does a HubSpot sandbox sync with production?

No. HubSpot's documentation describes no sandbox sync from production after creation. A standard sandbox copies supported production assets once, when you create it, plus up to 5,000 contacts if you choose. Later production changes don't reach it. Changes flow one way only, from sandbox to production, through deploy. Super Admins removed from production are removed from the sandbox; new ones must be added by hand.

What happened to legacy sandboxes?

HubSpot says legacy standard sandboxes are no longer supported as of April 30, 2026. Deploy to production only works from a new standard sandbox.

Do record IDs match between sandbox and production?

No. HubSpot notes contact, company, deal, ticket and custom object IDs differ between the two accounts.

Can I add more test records later?

Yes. You can import records into the sandbox manually, up to 200,000 per object type, according to HubSpot.
