A Sandbox Environment in Business Central is a safe copy (or clean instance) where you can test changes, train users, and trial apps without damaging your live Production system.
A new Business Central installation comes with one Production Environment and you can configure up to three Sandbox Environments.
Sandbox Environment in Business Central
Version 1: The deliberately terrible explanation
A Business Central Sandbox is like giving your ERP a crash-test dummy and a fenced-off car park. You can drive it into a lamp post, reverse it through a hedge, and try “one tiny change” that would absolutely set fire to month-end in live.
It looks like your real Business Central. It feels like your real Business Central. Sometimes it even contains a full copy of your real data — invoices, customers, the lot — like a clone that’s been told, “You’re not allowed near the real world.”
It’s the place you send risky ideas so they can fail quietly, without your finance team forming a pitchfork committee.
And if you use it as a second live system? That’s not “clever”. That’s just building a second problem to manage.
Previous Glossary Term: Profiles in Business Central
Take advantage of our 15% discount on your Business Central license renewal. Enter your details at the end of this blog for a personalised quote.
Version 2: The proper explanation
A Sandbox Environment in Microsoft Dynamics 365 Business Central is a non-production environment designed for testing, training, development, troubleshooting, and safe experimentation.
It’s isolated from Production so you can explore changes without affecting live operations, data integrity, or day-to-day processing.
What you actually use a sandbox for
-
Testing configuration changes: posting setups, VAT settings, approval workflows, dimensions, number series — the “small tweaks” that can create big reporting headaches.
-
Validating extensions and updates: install apps, confirm behaviour, and test update impacts before touching Production.
-
Training users properly: practise posting routines and role-based processes without corrupting live ledgers.
-
Integration testing: verify APIs and connected services (e.g., Power Platform) with controlled risk.
How sandboxes are created (and why copying matters)
In Business Central online, environments are managed via the Business Central admin centre. You can create a fresh sandbox or copy an existing environment (often Production) into a sandbox to get realistic data and setup for testing.
Copying is powerful — and dangerous — because you’ll be testing against “real-looking” data. Treat it carefully (especially for GDPR and confidential information).
The differences vs Production that catch people out
-
Sandbox can contain Production data, but it’s still not Production. It’s for safe testing, not running the business.
-
Preview apps have restrictions. Preview versions of AppSource apps can be installed on sandboxes, but if a sandbox has a preview app installed, you can’t copy that sandbox into Production until you update to public versions or uninstall the preview apps.
-
Database exports aren’t symmetric. In the admin centre, requesting a database export is typically limited to Production environments. Plan your test data strategy accordingly.
-
Power Platform links can affect lifecycle actions. Business Central environments can be linked to Power Platform environments of the same type, and links can block certain operations — important if you’re building automations or integrations.
FAQs: Business Central Sandbox Environment
What is a sandbox environment in Business Central?
A sandbox is a non-production Business Central environment used for testing, training, development, and troubleshooting without impacting Production.
Can a sandbox include a copy of Production data?
Yes. You can copy an existing environment (often Production) into a sandbox so you can test with realistic setup and data.
Can I copy a sandbox back into Production?
Environment copy/restore has constraints. For example, if the sandbox has Preview AppSource apps installed, you must remove or update them before copying to Production.
Can I export a sandbox database from the admin centre?
Database export requests in the admin centre are generally available for Production environments. For sandbox data, use alternative export approaches depending on your need.
How many sandboxes should an SME keep?
At least one for safe testing and training. If you do frequent change (apps, integrations, reporting), keep a dedicated UAT sandbox as well.
Best-practice sandbox habits (boringly effective)
- Name with intent (e.g.,
TEST-APPS-Q1,TRAINING-FINANCE,UAT-WMS). - Control access: only people testing should be in there.
- Assume copied data is sensitive: minimise exposure and keep it tidy.
- Test like you mean it: use a checklist, record outcomes, and only promote changes that are proven.
- Refresh when needed: don’t “live” in a sandbox; recreate/copy when you need a clean baseline.
If you want Business Central to improve without chaos, sandboxes are non-negotiable. Testing in Production isn’t bravery — it’s just expensive theatre.
Can We Help?
Want to get more from Business Central? Time to get in touch!
Enter your details below or call us on +44 (0) 1782 976577