Starting November 20, the site will be set to read-only.
On December 4, 2023,
Apex Code Development (90768)
General Development (55146)
Visualforce Development (37251)
Lightning (18265)
APIs and Integration (17146)
Trailhead (11680)
Formulas & Validation Rules Discussion (11337)
Other Salesforce Applications (8116)
Jobs Board (6655)
Force.com Sites & Site.com (4842)
Mobile (2694)
You need to sign in to do that
Don't have an account?
Bhushan Mahajan 5 
Salesforce organization. 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.
• Multistage release processes — A typical development process requires iterative building, testing, and staging before releasing to
a production environment. Scripted retrieval and deployment of components can make this process much more efficient.
• Repetitive deployment using the same parameters — You can retrieve all the metadata in your organization, make changes, and
deploy a subset of components. If you need to repeat this process, it's as simple as calling the same deployment target again.
• When migrating from stage to production is done by IT — Anyone that prefers deploying in a scripting environment will find the
Force.com Migration Tool a familiar process
Refer the following link for more info: http://www.salesforce.com/us/developer/docs/daas/salesforce_migration_guide.pdf
All Answers
Salesforce organization. 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.
• Multistage release processes — A typical development process requires iterative building, testing, and staging before releasing to
a production environment. Scripted retrieval and deployment of components can make this process much more efficient.
• Repetitive deployment using the same parameters — You can retrieve all the metadata in your organization, make changes, and
deploy a subset of components. If you need to repeat this process, it's as simple as calling the same deployment target again.
• When migrating from stage to production is done by IT — Anyone that prefers deploying in a scripting environment will find the
Force.com Migration Tool a familiar process
Refer the following link for more info: http://www.salesforce.com/us/developer/docs/daas/salesforce_migration_guide.pdf