organization's metadata into a Force.com project, and then deploying the project to a Developer Edition organization. However, not all metadata types can be retrieved and deployed, and not all features in your production organization may be enabled in a Developer Edition organization, so your development environment will not be as complete of a replica as a sandbox.
Describe how to manage Sandbox environments. Given a scenario, determine whether to use package or metadata deployment A Force Platform IDE deployment is quite simple, but the deployment is done by a single administrator who must have access to both the source and target organizations. With the IDE, each individual deployment is a separate process.The Force Platform Migration Tool allows you to automate this process with scripts, so you can deploy to multiple organizations without having to do each one by hand. If you have access to both sides of the deployment, and you are only deploying to a small number of targets, using the Force Platform IDE is probably the best method. If you have access to both organizations and are deploying to a larger number of servers, or if you are repeatedly deploying to a set of organizations, the Force Platform Migration Tool is probably your best choice. Packaging separates the publishing of an application from the installation of the application in another organization, so you can perform a single publishing operation and have many other organizations install the result.The most crucial difference between this one-to-many deployment method and the use of the Force Platform IDE is the publish and subscribe model, which separates the task of making an application (or a set of components) available and the task of installing them in a target organization.The packaging method is required if you do not have access to the target organization—the typical scenario for an independent software vendor (ISV) who is selling a product to a wider audience. The Force.com Migration Tool is especially useful in the following scenarios: • Development projects - where you need to populate a test environment with large amounts of setup changes - Making these changes using a Web interface could take a long time.