A HubSpot sandbox account gives your team a safe place to test automation workflows, configure integrations, and train new users without touching your live CRM data. If you have run into the problem of a misconfigured workflow accidentally sending emails to real contacts, or a broken integration corrupting your contact records, a sandbox is the solution.
Sandboxes are available on HubSpot Professional and Enterprise plans. Standard sandboxes come with Professional; developer sandboxes are available on Enterprise. If you are on Starter or Free, you do not have sandbox access — you would need to upgrade or use a separate test portal instead.
In your main HubSpot portal, go to Account Settings → Account Setup → Sandboxes. Click “Create sandbox.” You can name it (for example, “Testing – Do Not Use”) and choose whether to sync your production data or start with an empty portal. An empty sandbox is faster to set up and avoids any risk of syncing sensitive records.
Your sandbox is a separate portal with its own user list. Invite the team members who need access — typically your CRM admin, anyone building automation, and any new hires going through training. Users do not carry over automatically from your live portal.
Create a small set of dummy contacts, companies, and deals to work with. Use clearly fictional names and email addresses that cannot be confused with real customers. This makes it easy to spot whether test emails or workflows fire correctly without the risk of sending anything to real people.
Build your workflows, email templates, or integrations in the sandbox first. Test the full path — enrolment triggers, branch logic, delays, and notifications. When you are confident the setup works as intended, recreate it in your live portal. Some Enterprise accounts can sync changes directly; for Professional, you recreate manually.
What Is a HubSpot Sandbox Account?
A HubSpot sandbox is a separate, isolated version of your portal that mirrors your subscription features but keeps all activity contained. Changes made in the sandbox do not affect your live contacts, deals, or email logs. Think of it as a staging environment for your CRM.
HubSpot offers two types:
- Standard sandbox — Available on Professional and above. Mirrors your production portal’s features. Good for testing workflows, properties, and configurations.
- Developer sandbox — Available on Enterprise. Includes additional tools for custom development, API testing, and app integrations. Updates faster with new HubSpot features.
For most teams in Southeast Asia managing marketing automation or CRM implementations, the standard sandbox covers everything you need.
Who Should Use a HubSpot Sandbox?
A sandbox is most valuable for teams that are actively building or changing their HubSpot setup. Specific use cases include:
- New implementations — Testing your initial workflow setup, property configuration, and pipeline stages before going live with real contacts.
- Integration testing — Connecting a third-party tool (LINE OA, a payment gateway, a booking system) and verifying the data flow before it touches production records.
- Workflow changes — Editing an existing automation that runs on thousands of contacts. A mistake in a live workflow can send emails to the wrong segment or change contact properties at scale.
- Team training — Giving new CRM users or marketing executives a safe space to learn HubSpot features without breaking anything. This is especially useful in Southeast Asian teams where new hires may be unfamiliar with CRM tools.
- Data migrations — Running a trial import to catch field mapping errors or duplicate logic before you migrate your full contact database. See the HubSpot migration guide for migration-specific steps.
What Can You Test in a HubSpot Sandbox?
The standard sandbox replicates your portal’s features. You can test:
- Automation workflows — including branch logic, delays, and actions such as sending emails, updating properties, and creating tasks
- Email templates and sequences
- Forms and landing pages
- Custom properties and property groups
- Pipeline configurations for deals, tickets, and custom objects
- Integration connections via the app marketplace
- Report and dashboard setups
The sandbox respects the same feature limits as your subscription. If your Professional plan includes five automation workflows, that limit applies in the sandbox too.
What Are the Limitations of a HubSpot Sandbox?
Sandboxes are powerful but have limits to be aware of:
- Email sending is restricted — Sandboxes do not send real emails to external addresses. Emails are delivered only to inbox addresses belonging to portal users, so you can verify content and formatting without contacting real people.
- Third-party integrations behave differently — Some integrations require live credentials and may not connect cleanly in a sandbox environment. For payment gateways or custom apps, test in a staging environment for that tool as well.
- No automatic sync to production — Changes you make in the sandbox do not push to your live portal automatically on Professional plans. You rebuild the tested configuration in production yourself.
- Sandboxes are not backups — They are testing environments, not disaster-recovery copies of your live data.
How Does a Sandbox Fit Into a HubSpot Implementation?
If you are setting up HubSpot for the first time or doing a significant rebuild, the recommended pattern is: plan in a document, build in the sandbox, verify with real test data, then implement in production. This avoids the common problem of “building live” — where you test as you go in your main portal and end up with half-finished workflows touching real contacts.
For teams running the HubSpot implementation checklist, the sandbox phase fits between property setup and go-live. Build your core automation workflows in the sandbox first, run them through a few test contacts, confirm the logic, and then recreate them in production with confidence.
The same pattern applies when you are adding new automation to an existing portal. Before editing a workflow that currently runs on your full contact database, clone it, move the clone to the sandbox, test the change, then update the live version.
Can You Sync Production Data Into a Sandbox?
When you create a standard sandbox, HubSpot gives you the option to populate it with a sample of your production data — contacts, companies, deals, and associated records. This is useful when you need realistic data to test against, such as verifying that a workflow segment correctly filters based on your actual property values.
If you choose to sync data, the sandbox receives a copy at the time of creation. Changes in production do not continue syncing into the sandbox; it is a one-time snapshot. You can refresh the sandbox data by resetting and resyncing, though this clears any work you have done in the sandbox at that point.
For most testing scenarios — especially testing automation workflows — a small set of manually created dummy contacts gives you more control and avoids any risk of accidentally working with real customer data.
Frequently Asked Questions
Do I need a separate HubSpot login for the sandbox?
No. You access the sandbox from your main HubSpot account. From the portal switcher in the top navigation, you can toggle between your production portal and your sandbox. Users you invite to the sandbox can do the same.
Does the sandbox cost extra?
Standard sandboxes are included in Professional and Enterprise subscriptions at no additional cost. Developer sandboxes are included in Enterprise plans.
How many sandboxes can I have?
Professional plans include one standard sandbox. Enterprise plans include one developer sandbox and may include additional standard sandboxes depending on the specific plan. Check your contract or the HubSpot Knowledge Base for the limits on your subscription tier.
Will test workflows in the sandbox send emails to my real contacts?
No. Email sending in a sandbox is restricted to portal users only. Real contacts in your database are not affected by workflow actions in the sandbox.
Can I use the sandbox to test a HubSpot API integration?
Yes. You can generate sandbox-specific API credentials and point your integration at the sandbox portal during development and testing. This is the recommended approach before connecting an integration to your live portal.
This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us