What changed in HubSpot sandboxes, and why it matters for builders
A sandbox is supposed to be the safe place. The copy of your account where you can rip out a workflow, rewire a property, or test a risky change without anyone in production ever feeling it. Sounds pretty amazing, right?
But here's the catch nobody mentions: a sandbox is only as useful as it is accurate. If the copy is missing half the wiring, you're not testing against production anymore. You're testing against a grainy pixelated version of it. And without the high def 8k version, all of those missing pixels are going to bite you when it is time to deploy.
So the team has spent this release closing that gap. The theme tying all of it together is simple: your sandbox should reflect how your account actually works, before you ever touch the live one. You bought the high definition television, you deserve the high definition content.
Here's everything that changed.
Your assets come along, no matter which brand they belong to
Live
If you run more than one brand in HubSpot, your assets already know which brand they belong to. Your emails, forms, workflows, and properties are sorted and assigned by brand. That's the system working as designed.
The problem was that sandboxes only ever copied assets tied to your default brand. Anything assigned to one of your other brands got left on the shelf. And it wasn't just those assets that went missing: the workflows, emails, and forms that depended on them broke too, because the thing they were pointing at simply wasn't there. You'd open a fresh sandbox and find a lopsided version of your account that didn't match the one your team actually runs.
Now HubSpot copies the assets assigned to all of your brands, with their brand assignments preserved. When you create a sandbox, it identifies everything tied to any brand in your account, copies it over with the brand context intact, and brings along the workflows, emails, and forms that lean on it. That covers automated marketing emails, workflows, forms, custom properties, appearance and branding settings, and subscriptions. Each asset shows up in the right brand context, exactly the way it looks in production.
For multi-brand admins, this is the difference between testing against your real setup and testing against a guess.
Transactional emails finally make the trip
Live
Automated transactional emails are now copied into your sandbox, and you can deploy them back to production when you're ready. Any workflows or segments that reference them come along at creation time too.
If your team leans on transactional email, order confirmations, account notifications…those system-generated sends that quietly keep operations running, you know how much sits on top of them. Workflows rely on these emails to orchestrate customer communication efforts Your team might build segments to plan targeted plays for recipients of transactional emails sent through workflows.
And until now, none of it copied over.
You'd spin up a sandbox and have to rebuild every automated transactional email by hand, then rebuild everything that depended on them, every single time. For teams whose day-to-day runs on these workflows, it was real, recurring overhead.
Death by a thousand paper cuts.
Now your sandbox starts with those emails and the workflows and segments that rely on them already in place. When you're ready to push back to production, HubSpot surfaces any new automated transactional emails that are eligible to deploy, alongside the supported assets that depend on them, so you can review and ship them together instead of chasing the pieces one at a time. You can now put away the bandaids.
Email footers and subscription types stop being homework
Live
When you create a sandbox, your email footers and subscription types now copy over from production. Anything new you build in the sandbox can be deployed back to production too, so there's no rebuilding it after the fact.
Testing an automated marketing email end-to-end means seeing what your contact actually receives. That includes the footer at the bottom of the message and the subscription type that determines whether the email reaches them at all. Both used to be missing from sandboxes, which left you in an awkward spot: you'd rebuild footers by hand in the sandbox, then rebuild them again after deploying back to production, and you couldn't properly test whether a contact with a given subscription would even get the email. Two gaps, both adding manual rework to every sandbox and every deploy. Cue the paper cuts.
Now HubSpot copies all your email footer addresses from production settings, plus all your subscription types, including language variants. One thing to flag: visibility rules on subscription types aren't copied in this release. On the way back, if you create new footers in the sandbox and want to promote them with your marketing emails, they'll ride along when you deploy, so nothing needs recreating afterward. Deploying subscription types from the sandbox back to production is coming in a later release.
See exactly what copied, and what didn't
Live
The view that shows what was copied into your sandbox at creation, and what was deployed to production, has been rebuilt as a full-screen experience, replacing the old side panel.
After a sandbox spins up or a deploy finishes, the question you care about is direct: what worked, and what didn't? That matters most when you're troubleshooting a gap or confirming a deploy went the way you expected. The old side panel was cramped, and reading through it was a chore, especially for portals with a lot of assets. Now when creation or a deploy completes, you click into the details and get a full-screen breakdown with room to actually read it: what succeeded, what failed, no squinting at a sliver of the screen.
The roadmap is right there in the product
Live
The single most common question from sandbox users has always been some version of “when will this asset type be supported?” Until now, answering it meant filing a support ticket or digging through all of the docs. And now you have about 3,000 tabs in your browser (in addition to the tabs that you refuse to ever close. Don’t lie). Your browser has exhausted all memory on your machine you still don't have the answer, and you are about to enter into an existential crisis.
Do you quit your browser?
Fortunately for you roadmap visibility is now part of the product itself. On the sandboxes listing page you'll see a megaphone icon that opens a module showing which asset types are in beta, which are coming soon, and which are already fully supported. You get a clear read on the current state and what's next, which helps you plan the lifecycle of your sandboxes and time its creation to take advantage of new asset types as they land. You can also share feedback right there on which unsupported asset types matter most to you, which feeds directly into what the team prioritizes next.
But we really should talk about those other tabs.
Copy Sequences
Public Beta
Sequences will copy from production when you create a sandbox, which means you'll finally have a safe place to test and refine sales and service outreach before it goes live.
If you use sequences, you know they're not a small thing to get wrong. They pair timed email templates with automated task reminders to help reps follow up at the right moment and actually move someone toward booking a meeting or closing out a ticket. They're highly customized and tightly wired to how your team works, so testing changes in production carries real risk. And there was no way to copy them to a sandbox, which left you two bad options: test live and hope, or rebuild the sequence by hand in the sandbox and burn the time. Proper user acceptance testing wasn't really on the table.
When sequences sync to your sandbox, HubSpot copies all of them: every step, its email template, and the delay logic between steps. It brings the sequence settings (campaigns are the one exception, not yet supported), any automation configured on the sequence, all your message templates including their folder structure, and the referenced assets used inside sequences like documents, Vidyard videos, and property references. Two things it doesn't copy: performance data and enrolled contacts.. This first version handles copy from production-to-sandbox; deploying sequences back to production is coming in a later release.
Coming soon: Your CRM views show up the way your team set them up
Private Beta
When you create a sandbox, your CRM saved views now copy over from production. That includes shared views and team-scoped views across Contacts, Companies, Deals, Tickets, and Custom Objects, each one carrying its columns, filters, and access settings.
Think about how much of your team's actual work lives in those views. They decide what a rep sees the moment they land on the records page. They surface the right deals to the right person. They're how a manager turns a playbook into something the whole team runs the same way. A sandbox without them gives you the database with the steering wheel removed. That made it genuinely hard to test CRM changes in a realistic way, onboard a new hire, or validate a workflow before it went live. Admins coming over from legacy sandboxes felt this most: they were rebuilding team views from scratch every time they stood up a new environment. Here come those papercuts again.
Now the sandbox copies every view shared with everyone or with specific teams across supported objects, preserves each view's columns, filters, and access settings, and even copies the teams those team-scoped views point to, so the views actually work once they land. You start with the same setup your team relies on every day and can easily get started with User Acceptance Testing or new hire onboarding.
The bigger picture
Put all of these pieces together and the image quality you will see on that nice new tv will be looking pretty sharp. Every one of these changes is allowing you to have what you always have wanted: a sandbox that looks and behaves like the account you actually run, so the testing you do there means something. Fewer surprises on deploy. Less rebuilding the same footer for the third time. Less leaving the sandbox to figure out how the sandbox works.
And you are going to save a ton of money on bandages!
If you've been holding off on sandboxes because the copy never quite matched reality, this is a good moment to take another run at it. Spin one up, open the roadmap, and see how close to home it feels now.