We have an requirement where we to create copy our existing sandbox as new team would be using that soon.

We don't want to give them current production refresh copy (Which would have been easier, as it would just need to create copy from production).

I did some research and found that sales force don't allow copy one sandbox to another.

Another solution which we could find, is that eclipse meta data migration from once sandbox to another.

Could you please help us in best approach.

  • You could use ANT migration tool too. It is quite efficient, reusable ..
    – Prajith
    Commented May 4, 2016 at 20:15
  • Thanks Stygon. Could you please guide us as how by Using ANT Migration tool can we able to create full copy of current sandbox. Commented May 4, 2016 at 20:17
  • You could find the ANT guide in here - resources.docs.salesforce.com/sfdc/pdf/….
    – Prajith
    Commented May 4, 2016 at 20:19
  • ANT can be used to migrate metadata NOT DATA, from one environment to another. It works based on the components you specify on your package.xml . First you will ned to retrieve the components from the source org( the components present on your package.xml) . Then you will have to deploy the components to your target org. Thus metadata will be migrated from one org to another. Dependency issues are bound to crop up like any other migration tool ex - deploying some code that references a field,object etc that hasn't been migrated to the target org will cause deployments to fail.
    – Prajith
    Commented May 4, 2016 at 20:22

3 Answers 3


I'm not sure how urgent is your request. But checkout Summer 16 Release, and the new feature of Salesforce, Sandbox-toSandbox cloning. You will be able to select from which org you want to create your sandbox from.

enter image description here

Sandbox-to-Sandbox Cloning

Recent releases have provided some interesting enhancements in the sandbox area (post refresh scripts, increased edition allowances etc.), Summer ’16 build on such improvements with a new function that allows a sandbox to be created as a clone of another sandbox (as opposed to a production org). Superficially this sounds like a useful capability; on further thought however this could have a significant impact on development process, allowing QA sandboxes to be cloned as copies of development at the end of sprint (as just one example). Any uni-lateral sandbox-to-sandbox deployments could theoretically be replaced with a clone. Multiple development sandboxes converging into a single upstream org would be the exception. Cloning is also supported by the Tooling API, enabling full automation of environment management. I’ve been unable test this feature as sandbox copy doesn’t appear to be enabled in pre-release orgs, however it would appear that data can be included in the clone. How data copy works between the different sandbox types is yet to be seen.

  • Thanks Brovasi. This is great news. But how can i check whether this feature has been available in our sales-force org or not. Has salesforce launched it already or this in pipeline. Commented May 5, 2016 at 17:43
  • It's not released yet, and they won't have any pre-release. Also how it will work exactly is to be confirmed But very exciting news. I was just thinking it would be good to mention it ;-) I would go for sure with ANT script as the other people proposed, it's free and quite easy, but might be a bit of works and some limitation with the API. There is also some good managed package on Appexchange if you are not a dev such as Copado, DreamFactory, Flosum.
    – brovasi
    Commented May 5, 2016 at 22:18
  • ANT is the only way as August 31, 2016 Save Time by Cloning Sandboxes (Pilot) Removed the release note for this feature, which won’t be available in the Summer ’16 timeframe. Need to wait!!
    – user7601
    Commented Sep 18, 2017 at 7:41
  • This is available as Beta Feature of Spring 18 release Click here for link
    – Vipul Goel
    Commented Feb 20, 2018 at 4:53

ANT migration tool if a good alternative to eclipse migration. This involves migrating metadata using package.xml and components specified in it. It is highly efficient and reusable.


David, There are various products out there that can help with migrating metadata and data between sandboxes (and other Orgs). My own company, DreamFactory Software, makes a tool called SnapShot to migrate metadata and another called Monarch to migrate data (retaining relationships) between Orgs. Let me know if you want to see a demo and I am glad to give you a 15 min demo if you have the time.

Good luck! Sridhar

  • Thanks Sridhar..Management is in process of getting licence of Dream Factory already..Till that in this release we have to do it another way. :) Commented May 5, 2016 at 17:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .