Make HubSpot Sandboxes Real Sandboxes

HubSpot Ideas

Status: Idea Submitted

1

Hi HubSpot team and Community,

We love having sandboxes. We use them constantly for safe testing and change control. When teams are able to start sandbox-first and deploy to production from the beginning, HubSpot’s current model works well and should absolutely be the goal.

The challenge is that many customers do not start with HubSpot enterprise from day one.

As organizations grow with HubSpot, portals evolve organically over months or years. By the time sandboxing becomes a reality, teams are no longer starting from a clean slate. They are working with mature, complex production portals that need to be mirrored safely in order to improve them.

Today, HubSpot sandboxes often feel less like a true replica and more like a fresh portal with a few key assets copied over. At the moment, our “sandbox” sometimes feels like a sandbox at the park… with half the toys missing. Still fun, but not what you want before a big release.

What’s missing for real-world testing

A few examples that create a major gap for enterprise teams:

  • Record layouts and sidebar configurations do not sync, so UI and process testing is incomplete out of the gate.
  • Teams do not copy over, which breaks routing, ownership models, and team-based views.
  • User permissions, permission presets, and role-based access do not fully carry over, making it impossible to validate what non-admin users actually see.
  • Brands / Business Units do not copy, limiting the ability to test multi-brand, multi-region, or multi-entity setups.
  • Custom object names and labels do not always carry over cleanly, which introduces confusion and increases rebuild effort during testing.

These gaps make it difficult to validate how production actually behaves, especially for non-admin users.

Why this matters

The community has been asking for “copy the environment” capabilities for years, because the current level of parity requires too much manual reconstruction.

Key points rasied over the years:

  • Saves significant admin and QA time (fewer rebuilds, fewer surprises)
  • Enables true UAT (what users actually see and do every day)
  • Reduces production risk (fewer hotfixes and rollback reminders that we all pretend never happened)

What we are asking HubSpot to add

At minimum, please support syncing and deploying more of the operational layer that makes a portal “feel like production,” including:

  • Record layouts and sidebar configurations HubSpot Community
  • Broader portal configuration parity that impacts testing outcomes (governance, settings dependencies, and other non-asset configuration)

This becomes especially important for organizations that are modernizing or refactoring an existing production portal, not building one from scratch.

Request to HubSpot

Can the HubSpot team consolidate the related Community requests into a single tracked initiative so the true demand is visible in one place? Right now, the need is spread across multiple posts, and the signal is getting diluted.

If you agree, please upvote and add your use case. The more real-world examples we share, the easier this is to prioritize.

Thank you.

P.S. I wasn’t sure what category this belonged in so I selected HubSpto Support.

-----

Links to the relevant Community posts