Sandbox cloning versus creating from production
Key Takeaway
A clone starts with its source sandbox's data and metadata, so you don't rebuild that setup from production. It also inherits that sandbox's license type and access.
A sandbox is an isolated copy of an org where you build and test, so your work doesn't affect production. You can create a new sandbox from your production org, or you can clone an existing sandbox, called the source sandbox. Cloning saves setup time and lets teams work in parallel, but a clone inherits much more from its source than a new sandbox does.
What each source copies
When you create a sandbox from production, Salesforce copies production's metadata, and the sandbox type decides what data comes along.
| Sandbox type | What it gets from production |
|---|---|
| Developer and Developer Pro | A copy of the configuration (metadata) |
| Partial Copy | The metadata, plus a sample of production data defined by a sandbox template |
| Full | A replica that includes all data, or a template-based subset if you choose one |
Cloning copies both the data and the metadata of the source sandbox to the new sandbox.
Entity history and Chatter are copied to a clone only for Full sandboxes, and only if the source sandbox includes them. When you create a Full sandbox from production, you decide whether to include field tracking history and Chatter. Field tracking history is omitted by default. Chatter data can add a lot of time to the copy.