{"title":"Get a StoreConnect sandbox from a Salesforce sandbox","slug":"get-a-storeconnect-sandbox","url":"https://support.storeconnect.com/articles/get-a-storeconnect-sandbox","url_markdown":"https://support.storeconnect.com/articles/get-a-storeconnect-sandbox.md","subtitle":null,"summary":"Provision a StoreConnect sandbox store (its own website environment) inside a Developer, Partial Copy, or Full Copy Salesforce sandbox using the Get sandbox action in the StoreConnect Console.","type":"Help_Documentation","video_url":"","keywords":"sandbox, get sandbox, sandbox setup, provision sandbox, full sandbox, partial sandbox, developer sandbox, partial copy, full copy, sandbox store, sandbox website, sandbox provisioning, console setup, 90-day trial, sandbox storage, storage limit, initial sync, sync opt-in","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Use this process to provision a StoreConnect sandbox store, a separate website environment for a Salesforce sandbox org, so you can test changes without touching your live store.\n\nWhen you create or refresh a Salesforce sandbox org, it copies your StoreConnect configuration from production, but it does not automatically get its own website. Your sandbox org's records still point at your production store's website and media until you provision a sandbox store from the **StoreConnect Console**.\n\nThe steps below apply to **Developer**, **Partial Copy**, and **Full Copy** Salesforce sandboxes. The flow is the same for every sandbox type; the only difference is how much data Salesforce copies into the sandbox. A full copy sandbox brings all records; a partial copy sandbox only brings data for the objects included in its sandbox template.\n\nIf you are evaluating StoreConnect and do not yet have a production store, use a Salesforce trial org instead. See [explore StoreConnect in a Salesforce trial org](install-storeconnect-to-a-salesforce-trial-org).\n\n:::warning\nPartial copy sandboxes only copy the objects in your sandbox template. Before you create or refresh a partial copy sandbox, make sure its template includes all StoreConnect objects (the `s_c__*` objects: Store, Page, Content Block, Media, Products, Setup Configuration, and the rest). If they aren't in the template, their records won't be copied and your sandbox store will have no data or configuration to set up from. Full copy sandboxes copy all data, so this doesn't apply to them.\n:::\n\n## Before you begin\n\n- Run this in the Salesforce sandbox, not production. The **Get sandbox** action only appears when you are logged into a Salesforce sandbox org.\n- You must be a Salesforce System Administrator and hold the StoreConnect Administrator permission.\n- The parent production org's StoreConnect setup must be complete — the sandbox inherits that configuration when it is created.\n- Sandbox type doesn't matter for the setup flow. Developer, Partial Copy, and Full Copy sandboxes all use the same **Get sandbox** flow.\n- A sandbox store is free for 90 days. No license or install key is required to start one. To keep it running longer than 90 days you need a 'Persistent Copy sandbox license', see [Sandbox license costs](sandbox-license-costs).\n- Sandboxes have far less storage than production, and Salesforce will not let a sandbox exceed 100% of its storage limit. Plan to reduce the initial sync load before you set up the sync user.\n\n## Manage sandbox storage and the initial sync\n\nSandboxes, especially developer and partial copy sandboxes, have much less data storage than your production org, and Salesforce does not allow a sandbox to exceed 100% of its storage limit. The StoreConnect initial sync can push storage usage up sharply, so plan for it before you set up the sync user.\n\nWhen you first configure the [sync user](how-to-create-a-storeconnect-sync-user), StoreConnect performs an initial bulk pull of every record it monitors on the standard objects (Account, Contact, Order, Order Item, and more) into its sync database. In an org with large volumes of accounts, contacts, or orders, this pull can spike storage usage and, in a smaller sandbox, take it over the 100% limit. See [Initial sync when setting up the sync user](initial-sync) for what the initial sync includes.\n\nTo mitigate the spike, you can [manage the standard object sync](per-record-sync-opt-in) (per-record sync opt-in) to sync only the records you actually need for testing. Any accounts, contacts, orders, or other standard-object records that aren't needed for your testing can be suppressed from syncing, which reduces both the storage spike and the time the initial sync takes.\n\n:::tip\nConfigure sync opt-in before you run setup and choose a sync user, so the filtering applies to the first sync; only the records you have marked will be pulled in. Configuring it afterward means the full initial sync has already run, and you would need to carefully prepare your existing records before enabling it. See [Manage standard object sync](per-record-sync-opt-in) for the full sequence.\n:::\n\n## Provision the sandbox store\n\n:::warning\nThe **Get sandbox** action resets the installer and clears the website and media settings the sandbox inherited from production, so the sandbox can be given its own. Run it only in a sandbox org. There is no undo.\n:::\n\n1. Create or refresh your Salesforce sandbox in **Setup** \u003e **Sandboxes**, then log into the sandbox org.\n2. Open the **StoreConnect Console**.\n3. In the header, select **Setup**, then under **Tools** select **Get sandbox**.\n4. When the confirmation *\"Are you sure you want to start a new sandbox?\"* appears, select **Yes, let's create a sandbox**.\n5. On the **Sandbox setup** welcome screen, select **Let's get started**.\n6. Review the sandbox availability information (your sandbox is free for 90 days), then select **Start sandbox**.\n7. Follow the remaining setup steps (permissions and choosing a sync user) to finish.\n8. Confirm the sandbox store is running: open the store URL shown in the **StoreConnect Console** and check that it is different from your production store URL and that the storefront loads.\n\n## What happens next\n\nWhen you start the sandbox, StoreConnect:\n\n- provisions a new website environment for the sandbox store, separate from your production store, with its own store URL.\n- sets up separate media storage for the sandbox store so it does not share images with production.\n- re-imports your media into the sandbox store's own storage. Media records that pointed at your production images are queued to import fresh copies, so the sandbox store displays its own media. This runs in the background — allow some time after setup for images to finish importing.\n\n## After setup\n\n- Your sandbox store has its own website URL, separate from production. You can test changes freely without affecting your live store.\n- When you have finished testing and want to move changes into production, see [Move data from sandbox to production](migrating-from-sandbox).\n\n:::tip\nA sandbox store is the right place to try changes driven by an AI agent, since nothing you do there touches your live store. See [build on StoreConnect using AI agents](use-ai-agents-with-storeconnect).\n:::\n\nFor more information about StoreConnect Console actions, see [About the StoreConnect console](about-the-storeconnect-console)."}