Cloning Sandboxes

Dan Fowlie

A new feature goes into pilot in Summer 16 which is very useful for working with multiple salesforce orgs as we’ve talked about in the past. Sandbox-to-sandbox cloning allows you to create a new sandbox from an existing sandbox rather than from production.

So why is this useful?

In the pattern we’ve shown before, each developer and admin has their own sandbox.

Diagram explaining the process for cloning sandboxes from production

As it works today, if a new developer starts they will get a new sandbox cloned from production. The problem is that if you’re mid development in a new stream of work, production won’t be the latest and greatest code and configuration that the other team members have been working with. You’ll need to perform manual steps to get the latest metadata into the new sandbox.

Diagram explaining the process for cloning sandboxes from production
Tip: Figuring out what to copy can be tricky, but an org comparison tool can help.

With sandbox-to-sandbox cloning, life gets a lot easier. Now a new sandbox can be cloned from your integration environment. It’s that simple! Now any new developer or admin can be up and running quickly and easily and start contributing to the changes.

Diagram explaining the process for cloning integration

Another use case for this feature could be cloning a partial copy sandbox which has been configured with appropriate data for testing or training.

We hope to see this feature go Generally Available in the Winter 16 release.

Salesforce Advice Best Practices Development
Photo of Dan Fowlie
Dan Fowlie is the Principal of Salesforce Solutions at .