Table of Contents

What is Salesforce Sandbox? Your Safe Space for Innovation

Quick answer

This page answers What is Salesforce sandbox? quickly.

Fast answer first. Then use the tabs or video for more detail.

Watch the video explanation below for a faster overview.
Game mechanics may change with updates or patches.
Use this block to get the short answer without scrolling the whole page.

Read the FAQ section if the article has one.
Use the table of contents to jump straight to the detailed section you need.
Watch the video first, then skim the article for specifics.

▶

A Salesforce Sandbox is a copy of your Salesforce production organization used for development, testing, and training purposes. It’s a completely isolated environment, meaning that anything you do within the sandbox will not impact your live production data or users. Think of it as a safe playground where you can experiment with new features, customize existing functionalities, and deploy code without the fear of breaking anything in your real, customer-facing Salesforce instance.

Why Use a Salesforce Sandbox?

Imagine you’re building a magnificent sandcastle. Would you build it right on the beach where the tide could wash it away in seconds? Of course not! You’d build it in a protected area, a sandbox, where you can experiment with different designs and techniques without risk.

Salesforce sandboxes offer the same protection and flexibility for your CRM system. They are invaluable tools for several reasons:

Safe Testing Environment: Test new configurations, code, and integrations without impacting live data or users.
Development Playground: Developers can build and modify applications in a safe and controlled environment.
Training Ground: Train new users on the Salesforce platform without the risk of them accidentally altering live data.
Risk Mitigation: Implement changes with confidence, knowing they’ve been thoroughly tested in a sandbox.
Innovation Hub: Explore new Salesforce features and functionalities without pressure or risk to your production org.
Performance and Load Testing: Simulate real-world user loads to identify potential performance bottlenecks before deployment.

Types of Salesforce Sandboxes

Salesforce offers different types of sandboxes, each suited for specific purposes and offering varying amounts of storage and refresh frequency:

Developer Sandbox: The smallest and most basic type, designed for individual developers to work on isolated customizations and code development. It’s ideal for developing and testing small features or bug fixes. It includes a limited amount of storage (200 MB for data and file storage) and is typically refreshed daily.
Developer Pro Sandbox: A step up from the Developer sandbox, offering more storage (1 GB for data and file storage) and the ability to support larger development projects or team collaboration. It’s still primarily for development, but can accommodate more complex customizations. It is also typically refreshed daily.
Partial Data Copy Sandbox: Includes a subset of your production data, along with all of your metadata. This allows you to test code and customizations with realistic data volumes and scenarios, which can be crucial for identifying performance issues. This type includes 5 GB of data storage and can be refreshed every 5 days.
Full Sandbox: A complete replica of your production org, including all data, metadata, and settings. This is the gold standard for comprehensive testing, staging, performance testing, and user training. It can be refreshed every 29 days, making it suitable for projects that require thorough validation. It includes the same amount of storage as your production org.

Choosing the Right Sandbox

Selecting the right type of sandbox depends on your specific needs and budget:

Developer: Small projects, individual developers, and basic customizations.
Developer Pro: Larger development projects, team collaboration, and more complex customizations.
Partial Data Copy: Testing with realistic data volumes, performance testing, and user acceptance testing.
Full: Comprehensive testing, staging, performance testing, user training, and critical deployments.

How to Create a Sandbox

Navigate to Setup: In your Salesforce production org, go to Setup.
Search for Sandboxes: Use the Quick Find box to search for “Sandboxes.”
Click New Sandbox: If you have available licenses, click the “New Sandbox” button.
Name Your Sandbox: Provide a descriptive name and description for your sandbox.
Choose a Sandbox Type: Select the appropriate sandbox type based on your needs.
Create or Refresh: If creating a new sandbox, click “Create.” If refreshing an existing one, select the sandbox and click “Refresh.”
Wait for Completion: The sandbox creation or refresh process can take anywhere from a few hours to several days, depending on the size and complexity of your org.

Best Practices for Using Sandboxes

Regularly Refresh Your Sandboxes: Keep your sandboxes synchronized with your production org to ensure that testing and development are based on the latest data and metadata.
Use a Sandbox Management Strategy: Implement a clear strategy for managing your sandboxes, including naming conventions, refresh schedules, and data masking policies.
Document Changes: Keep track of all changes made in your sandboxes to ensure that they can be easily deployed to production.
Involve Stakeholders: Engage stakeholders in the testing process to gather feedback and ensure that customizations meet their needs.
Automate Deployments: Use tools like change sets, Salesforce CLI, or DevOps solutions to automate the deployment of changes from your sandboxes to production.

Are You Ready to Play?

Salesforce sandboxes are an essential part of a successful Salesforce implementation. They allow you to innovate, experiment, and mitigate risks without jeopardizing your live data or users. By understanding the different types of sandboxes and following best practices, you can leverage these powerful tools to enhance your Salesforce experience and drive business value.

Frequently Asked Questions (FAQs)

H3 1. What is the difference between a Salesforce sandbox and a production org?

Your production org is your live, customer-facing Salesforce environment where your business operations are carried out. A sandbox is a copy of that production org, isolated from the live environment, used for development, testing, and training. Changes in the sandbox don’t affect production until explicitly deployed.

H3 2. How do I know if I’m in a sandbox or production org?

The easiest way is to check the URL. Production orgs typically use login.salesforce.com and resolve to naX.salesforce.com (where X is a number). Sandboxes use test.salesforce.com and resolve to csX.salesforce.com. Also, many companies will implement visual cues, like a banner or color change, in the sandbox environment to clearly differentiate it.

H3 3. How often should I refresh my Salesforce sandbox?

The refresh frequency depends on the type of sandbox and the nature of your projects. Developer sandboxes may be refreshed more frequently (daily) than Full sandboxes (every 29 days). Refreshing regularly ensures that your sandboxes are up-to-date with the latest production data and metadata.

H3 4. Will my sandbox automatically update when Salesforce releases a new version?

Yes, sandboxes are typically upgraded to the latest Salesforce release shortly before your production org. This allows you to test your customizations and applications with the new release before it goes live in production.

H3 5. Does data in a sandbox count against my Salesforce storage limits?

No, data in a sandbox does not count against your production Salesforce storage limits. Sandboxes have their own separate storage allocation, which varies depending on the sandbox type.

H3 6. Can I customize the data that is copied into a partial data copy sandbox?

Yes, you can use sandbox templates to define which objects and data are copied into a Partial Data Copy sandbox. This allows you to select only the relevant data for your testing needs, reducing the refresh time and storage requirements.

H3 7. How do I deploy changes from a sandbox to my production org?

You can use change sets, the Salesforce CLI, or DevOps solutions to deploy changes from a sandbox to your production org. Change sets are a built-in tool for migrating metadata, while the Salesforce CLI and DevOps solutions offer more advanced automation and version control capabilities.

H3 8. How do I grant access to users in a sandbox?

Users in a sandbox need separate credentials. User accounts are copied during the sandbox creation/refresh process. Passwords, however, are not copied for security reasons. You will need to reset the passwords for your users in the sandbox environment. You may also need to update email addresses to prevent test emails from being sent to real users.

H3 9. What are the limitations of a Developer sandbox?

Developer sandboxes have limited storage (200MB data and file storage), and they don’t support performance or load testing. They’re primarily for individual developers working on isolated customizations.

H3 10. How much does a Salesforce sandbox cost?

Developer and Developer Pro sandboxes are typically included with your Salesforce license. Partial Data Copy and Full sandboxes may incur additional costs, depending on your Salesforce contract. Contact your Salesforce account executive for details.

H3 11. What is data masking, and why is it important in sandboxes?

Data masking is the process of obfuscating sensitive data in a sandbox to protect privacy and comply with data security regulations. It replaces real data with fictional data while maintaining the data’s format and structure.

H3 12. Can I use a custom domain in a Salesforce sandbox?

Yes, you can use a custom domain in a sandbox, but the domain must first be created in production and the sandbox selected as the associated org. Management of custom domains for sandboxes is done in the production environment.

H3 13. What happens to integrations when a sandbox is refreshed?

When a sandbox is refreshed, integrations may need to be reconfigured to point to the new sandbox environment. API endpoints, authentication settings, and other integration parameters may need to be updated.

H3 14. Can I roll back changes made in a sandbox?

While you can’t directly “roll back” a sandbox to a previous state, you can revert specific changes by using version control systems, deploying previous versions of metadata, or manually undoing configurations. This reinforces the importance of tracking and documenting all changes.

H3 15. Where can I learn more about Salesforce development and testing best practices?

Salesforce Trailhead offers numerous modules and trails on development, testing, and sandbox management best practices. Online communities like the Salesforce Stack Exchange and the Games Learning Society, found at https://www.gameslearningsociety.org/, offer valuable resources and support.

We hope this article has provided you with a solid understanding of Salesforce sandboxes and how to use them effectively. Happy developing!