Loading
Salesforce now sends email only from verified domains. Read More
Sandboxes: Staging Environments for Customizing and Testing
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Create a Sandbox

            You are here:

            1. Salesforce Help
            2. Docs
            3. Sandboxes: Staging Environments for Customizing and Testing

            Create a Sandbox

            When you create a sandbox, Salesforce copies the metadata from your production org to a sandbox org. What data gets copied depends on the sandbox type.

            Required Editions

            Available in: both Salesforce Classic and Lightning Experience
            Available in: Professional, Enterprise, Performance, Unlimited, and Database.com Editions
            User Permissions Needed
            To view a sandbox: View Setup and Configuration
            To create, refresh, activate, and delete a sandbox: Manage Dev Sandboxes (Developer or Developer Pro only) or Manage Sandboxes (all sandbox types)
            Important
            Important If you’re creating a Full sandbox from a production org hosted on a Hyperforce instance, your sandbox is created using the Quick Create technology by default. The Quick Create method creates your sandbox faster than the legacy method.

            However, because of resource limitations within the shared infrastructure, sandbox creation on Hyperforce instances can sometimes default to the legacy method, rather than the faster Quick Create method. See Best Practices for Salesforce Sandbox Creation and Refresh Times for more information.

            1. From Setup, find and select Sandboxes.
            2. Click New Sandbox.
              Note
              Note If the New Sandbox button is deactivated, confirm with your Salesforce admin that you have the Manage Sandboxes or Manage Dev Sandboxes user permission, or that your org has available sandbox licenses.
            3. Enter a name (10 characters or fewer) and a description for the sandbox.

              We recommend that you choose a name that:

              • Reflects the purpose of this sandbox, such as QA.
              • Has only a few characters, because Salesforce appends the sandbox name to usernames on user records in the sandbox environment. Names with fewer characters make sandbox logins easier to type.
            4. Select the type of sandbox you want.

              If you don’t see a sandbox option or need licenses for more, contact Salesforce to order sandboxes for your org.

              If you reduce the number of sandboxes you purchase, you’re required to match the number of your sandboxes to the number you purchased. For example, if you have two Full sandboxes but purchased only one, you can’t create a Full sandbox. Instead, convert a Full sandbox to a smaller one, such as a Developer Pro or Developer sandbox, depending on which types you have available.

            5. Select the data to include in your Partial Copy or Full sandbox.
              • For a Partial Copy sandbox, click Next, and then select the template you created to specify the data for your sandbox. If you haven’t created a template for this Partial Copy sandbox, see Create or Edit Sandbox Templates.
              • For a Full sandbox click Next, and then decide how much data to include.
                • In the Object Data Included field, select All to include all production data, or select Template-based to choose an existing sandbox template. For more information, see Create or Edit Sandbox Templates.
                • Choose whether to include field tracking history data of the copied objects. If your production org is on Hyperforce, select the checkbox to include 30 days of field tracking history. For non-Hyperforce production orgs, select an option from the dropdown menu.
                • Decide whether to copy Chatter data. Chatter data includes feeds, messages, and topics and is used in many components that affect your sandbox copy.

              Decreasing the amount of data you copy can significantly speed sandbox copy time.

            6. (Developer or Developer Pro only) If you have an available storage upgrade and want to use it, click 400 MB or 2 GB.

              If you don’t upgrade the storage at this time but change your mind post-creation, you can upgrade it by going to the Sandbox Details page, and clicking Edit. If you upgrade the storage now but later want to downgrade it, you can do so when you refresh the sandbox.

            7. (Optional) To run scripts after each create and refresh for this sandbox, specify the name of an Apex class you previously created from the SandboxPostCopy interface.
              Note
              Note See Create an Apex Class and SandboxPostCopy Interface for more information on creating this Apex class.
            8. For Sandbox Access, indicate a public user group that contains the users that require access to the sandbox (required for Developer and Developer Pro sandboxes).

              For Partial Copy and Full sandboxes, you also have the option to select All Active Users. Selecting all users can increase sandbox creation times and impact the login experience.

              How you select the public group depends on how many public groups exist in your production org.

              • If the production org has fewer than 60 public groups, select the group from the Public Groups dropdown.
              • If the production org has 60 or more public groups, enter the group name in the Public Groups field.

              For more information on Selective Sandbox Access, see Determine Who Has Sandbox Access.

            9. Click Create.
              Tip
              Tip Try to limit changes in your production org while the sandbox copy proceeds.

            The process takes from several minutes to several days, depending on the size and type of your org. When the sandbox status is Completed, your sandbox is ready for use. See Sandbox Action and Status Reference to learn about all sandbox statuses.

            You also receive an email notification when your sandbox is ready for use. To access your sandbox, click the link in the notification email. Users can log in to the sandbox at https://test.salesforce.com by appending .sandbox_name to their Salesforce usernames. For example, if a username for a production org is user1@acme.com, and the sandbox is named “test,” the modified username to log in to the sandbox is user1@acme.com.test.

            However, if a sandbox username exists, a 7-digit alphanumeric value is prepended to the username to ensure that the sandbox username is unique. For example: 1a2bc3duser1@acme.com.test.

            A user’s password to a sandbox is the same as their password to log in to the production org. If your production org uses single sign-on (SSO), ask your Salesforce admin to set up SSO for the sandbox environment as well.

            If you prevent user logins from https://login.salesforce.com in production through My Domain settings, the sandbox prevents user logins from https://test.salesforce.com by default. In this case, instruct users to log in to the sandbox using its My Domain login URL in the format https://MyDomainName--SandboxName.sandbox.my.salesforce.com. You can find an org's My Domain login URL on the My Domain Setup page.

            Note
            Note

            Salesforce automatically changes sandbox usernames, but not passwords. New sandboxes have the default email deliverability setting System email only. The System email only setting is especially useful for controlling email sent from sandboxes so that testing and development work doesn’t send test emails to your users.

            See Also

             
            Loading
            Salesforce Help | Article