Salesforce Sandbox Strategy: The 4 Types Explained (and How Many You Actually Need)
Salesforce ships four sandbox types. Most teams use them wrong. Here is the strategy that gets you a clean release pipeline without paying for sandboxes you never open.
Salesforce ships four sandbox types, and most teams pick the wrong mix, either paying for capacity they never use, or trying to squeeze every environment into a Developer sandbox that cannot hold real data. Here is the sandbox strategy that gets you a clean release pipeline without the overspend.
The Four Sandbox Types
- Developer, metadata only, 200 MB data limit. Refresh every day. Free with most editions.
- Developer Pro, same as Developer with 1 GB data limit. Refresh daily. Free-to-cheap.
- Partial Copy, metadata + up to 5 GB of sample data. Refresh every 5 days.
- Full, metadata + all data. Refresh every 29 days. Paid, and priced by data volume.
The Environment Model That Actually Works
| Environment | Sandbox type | Purpose |
|---|---|---|
| Dev sandboxes (one per developer) | Developer | Individual work |
| Integration / QA | Developer Pro | Team-level merge testing |
| UAT | Partial Copy | Business testing with realistic data |
| Staging / Preprod | Full | Full-scale testing, load testing |
The Refresh Cadence
- Dev sandboxes: refresh at the start of each sprint.
- QA: refresh after each release deploy.
- UAT: refresh at the start of each major project.
- Full: refresh once a month, always before a major release. See our release freeze guide.
The Data Question
Anything above Partial Copy contains customer data. Anonymize before opening to developers. See our sandbox anonymization guide.
Cost Optimization
- Delete unused developer sandboxes, every one takes storage and slows refresh time.
- Partial Copy templates: define once, reuse across refreshes.
- Full sandbox: one is usually enough. Two only if you have parallel major projects.
Common Mistakes
- Testing in Production. Never acceptable in 2026.
- UAT on a Developer sandbox with fake data, business does not test realistic scenarios.
- Never refreshing the Full sandbox, you regression-test against stale data.
- Not versioning sandbox setup, new environments take days to bootstrap.
Regional Notes
- EU: data residency of sandbox copies matters, Full sandboxes must respect the same region rules as Production. See our GDPR guide.
- Regulated industries: some auditors require documented sandbox refresh and anonymization schedules.
Frequently Asked Questions
How much does a Full sandbox cost?
Priced as a percentage of your Salesforce license value; typically several thousand USD per year.
Can we share one sandbox across teams?
Yes for QA/UAT. Never for developer work.
How often should we refresh Full?
Monthly, plus before major releases.
Do we need Partial Copy?
Not always. Skip if UAT can be done on a Full sandbox instead.
Get a Sandbox Strategy Assessment
Our Salesforce audit includes a sandbox topology review with cost optimization. Book a 30-minute call.
If this sounds like your CRM, let's look at it together.
Thirty minutes, no deck, no pitch. You leave with a diagnosis either way.