What is Sandbox in Salesforce?
Updated · By the Clientell AI team · How we write
A Salesforce sandbox is a copy of your production org in a separate environment, used for development, testing and training. Changes in a sandbox do not affect production. The four Salesforce sandbox types are Developer, Developer Pro, Partial Copy and Full. They differ in how much data they hold and how often you can refresh them.
Key facts
- What it is
- An isolated copy of your org for testing and training (Salesforce Help)
- Four types
- Developer, Developer Pro, Partial Copy and Full
- Refresh intervals
- Developer and Developer Pro 1 day, Partial Copy 5 days, Full 29 days (Salesforce Help)
- Data included
- Developer and Developer Pro: metadata only. Partial Copy: a sample. Full: all or most data.
- Effect on production
- None. Sandboxes are isolated from your production org.
- Editions
- Professional, Enterprise, Performance, Unlimited and Database.com (Salesforce sandbox guide)
Clientell AI, the AI Salesforce admin, compares your sandbox to production and deploys from a chat, with a pre-flight check and rollback, so Sandbox stops being a manual step. See AI Salesforce deployments
Try it in Clientell AI
“Compare my sandbox to production, list what a Sandbox would move, and show the risks before anything deploys.”
Clientell AI reads your org first. Platform deployments include rollback. How security works.
What is a Salesforce sandbox?
A sandbox is a copy of your Salesforce org in a separate environment. You can use it for testing and training. Sandboxes are isolated from production, so what you do in one does not affect your live org (Salesforce Help).
The normal flow is simple. Build a change in a sandbox, test it, then move it to production, often with a change set. Changing automation straight in production risks breaking live work.
The search term CRM sandbox means the same thing.
What are the Salesforce sandbox types and limits?
Every sandbox gets your production metadata, meaning your configuration: objects, fields, flows and code. Only Partial Copy and Full sandboxes include data. The storage and refresh figures below come from Salesforce's own pages (Salesforce Help).
| Type | Data | Storage | Refresh interval |
|---|---|---|---|
| Developer | None | 200 MB data (sandbox guide) | 1 day (Help) |
| Developer Pro | None | 1 GB data, 1 GB files (sandbox guide) | 1 day (Help) |
| Partial Copy | A sample, defined by a sandbox template | 5 GB data, 5 GB files (sandbox guide) | 5 days (Help) |
| Full | All or most production data | Same as production (sandbox guide) | 29 days (Help) |
Which sandbox type should you use?
Match the type to the job. When you upgrade the edition of your org, the sandbox keeps its earlier edition. The Help article says to choose Match Production Licenses instead of refreshing (Salesforce Help).
- Use Developer for individual development and unit testing. It starts with empty records.
- Choose Developer Pro for the same work with room for larger data sets.
- Take Partial Copy for acceptance testing, integration testing and training, since it holds a sample of real data.
- Go with Full for the closest match to production, such as staging before a release.
Example: create a Developer sandbox
Create one before you build a new field or flow.
- 1. Setup > Sandboxes > New Sandbox. You need the Manage Sandboxes permission.
- 2. Name it, for example dev1. Choose Developer as the type.
- 3. Pick Match Production Licenses if offered, then click Create.
- 4. Wait for the status to show Completed. You get an email, and the status appears in Setup > Sandboxes.
- 5. Click Login next to the sandbox. Check that Account and Opportunity exist but hold no records.
- Undo: delete the sandbox from the same list when you are done.
What happens when you refresh a sandbox?
A refresh replaces a sandbox with a new copy of production. It updates the metadata. If the sandbox is a clone or uses a sandbox template, it updates data too. The org ID of the sandbox changes each time it is refreshed (Salesforce Help).
Refresh requests cannot be canceled. Your existing copy stays available while you wait, and the new copy is inactive until you activate it.
Activating a refreshed sandbox permanently deletes the older version and all data in it. Production is not affected. New sandboxes that are not activated within 30 days are deleted (Salesforce Help).
What are common sandbox mistakes?
Each has a simple fix.
- Activating a refresh before saving work. Fix: move what you need out first (Salesforce Help).
- Using a Developer sandbox for data-heavy testing. Fix: use Partial Copy or Full (Salesforce Help).
- Testing in production because the sandbox is stale. Fix: refresh on a schedule that fits the refresh interval.
- Missing licenses or features after an edition upgrade. Fix: refresh with Match Production Licenses.
FAQ: Sandbox in Salesforce
What is a Salesforce sandbox?
A copy of your production org in a separate environment, used for development, testing and training. Changes in it do not affect production.
What are the types of Salesforce sandboxes?
There are four: Developer, Developer Pro, Partial Copy and Full. The first two hold metadata only. Partial Copy adds a data sample. Full copies all or most data.
How often can I refresh a sandbox?
Once a day for Developer and Developer Pro, every 5 days for Partial Copy, and Full every 29 days (Salesforce Help).
What are the Salesforce sandbox storage limits?
Storage is 200 MB of data for Developer. Developer Pro has 1 GB data and 1 GB files. Partial Copy has 5 GB each. Full matches production (sandbox guide).
Does a sandbox copy my production data?
Only Partial Copy and Full sandboxes include data. Developer and Developer Pro copy metadata only, so records start empty.
What happens to a refreshed sandbox I do not activate?
New sandboxes that are not activated within 30 days are deleted (Salesforce Help).
Sources: Salesforce: What Is a Salesforce Sandbox?, Salesforce Help: Sandbox Types and Management, Salesforce Help: When to Use a Sandbox, Salesforce Help: Create, Clone, or Refresh a Sandbox, Salesforce Help: Activate Your Refreshed Sandbox, Salesforce Help: Sandbox Action and Status Reference. Last reviewed .
Related Salesforce Terms
3 termsChange Set
PlatformA Change Set is a native Salesforce deployment tool that migrates metadata components (such as custom objects, fields, Flows, and Apex classes) between related orgs.
Permission Set
AdministrationA Permission Set is a collection of permissions that can be assigned to users on top of their profile to grant additional access without changing the profile itself.
Profile
AdministrationA Profile in Salesforce defines the baseline set of permissions, page layout assignments, and system settings that apply to every user assigned to it.
What should I read next?
More in Administration
View all →Salesforce Admin
A Salesforce Admin is the person responsible for configuring, maintaining, and optimizing a Salesforce org to meet an organization's business needs.
Profile
A Profile in Salesforce defines the baseline set of permissions, page layout assignments, and system settings that apply to every user assigned to it.
Permission Set
A Permission Set is a collection of permissions that can be assigned to users on top of their profile to grant additional access without changing the profile itself.
Role Hierarchy
The Role Hierarchy in Salesforce controls record-level visibility by granting users access to records owned by anyone below them in the hierarchy tree.
Try this on your own org
Start the 14-day free trial, no card. Clientell AI asks before it changes anything in production.
14-day free trial · No credit card required