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
- Note the creation date. Anything changed in production since then isn’t in the sandbox.
- Recreate production changes you need for testing in the sandbox by hand, or create a fresh standard sandbox when it has drifted too far.
- Import test records when you need more or different data.
- Connect integrations to their sandbox versions, not production, so tests don’t write live data.
- 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.
- 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 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.
Sources
- Set up a HubSpot standard sandbox account (HubSpot Knowledge Base)
- Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)
- Deploy sandbox changes to production (HubSpot Knowledge Base)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
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