Definition
Full Sandbox is a configuration tool or concept within Salesforce administration that governs platform behavior. Administrators use it to manage access, enforce data quality, and customize the user experience without writing code.
Real-World Example
a Salesforce administrator at Coastal Health uses Full Sandbox to maintain data quality and enforce organizational policies across the platform. By properly setting up Full Sandbox, they prevent common data entry errors and ensure that users follow established business processes, which saves the support team hours of cleanup work each week.
Why Full Sandbox Matters
A Full Sandbox is a testing environment that replicates your entire Salesforce production org, including all metadata (configuration, code, customizations) and all data (every record across every object). Unlike Developer or Partial sandboxes that only copy metadata or a subset of data, a Full Sandbox provides a complete mirror of production. This is essential for performance testing, user acceptance testing (UAT), data migration rehearsals, and training scenarios where realistic data volumes are needed. Full Sandboxes solve the problem of test environments that do not accurately represent production conditions, which can mask performance issues and integration failures.
Full Sandboxes are the most resource-intensive sandbox type — most editions allow only one, and refreshing it is limited to once every 29 days. Because of these constraints, organizations must plan their use carefully. Best practices include scheduling Full Sandbox refreshes to align with major release cycles, using it primarily for UAT and performance testing rather than daily development, and maintaining a separate Developer Sandbox for coding work. Organizations that use their Full Sandbox as a development environment often find it becomes stale or cluttered, reducing its effectiveness for the critical testing scenarios it was designed for.
How Organizations Use Full Sandbox
- Coastal Health Systems — Before a major Salesforce upgrade affecting 2,000 users, the admin refreshes the Full Sandbox with all 5 million patient records. The QA team runs regression tests against realistic data volumes, uncovering a performance bottleneck in a custom trigger that only appears with more than 1 million records — an issue that would have caused a production outage.
- NexGen Financial — The data migration team uses the Full Sandbox to rehearse a migration from a legacy CRM. They import 800,000 records across 12 objects, validate foreign key relationships, and test all 45 active flows against the migrated data. Two critical mapping errors are caught and fixed before the production migration weekend.
- Pinnacle Retail — The training team refreshes the Full Sandbox before a quarterly onboarding session for 30 new sales reps. Trainees practice with realistic data — real account names, opportunity values, and case histories — giving them hands-on experience that prepares them for production. This approach reduced the ramp-up time for new reps from 6 weeks to 4 weeks.