contents
Documentation Version
Summer '15 (API version 34.0)
Language
English
  • Summer '15 (API version 34.0) 34.0
  • Spring '15 (API version 33.0) 33.0
  • Winter '15 (API version 32.0) 32.0
  • Summer '14 (API version 31.0) 31.0
  • Spring '14 (API version 30.0) 30.0
  • Winter '14 (API version 29.0) 29.0
  • English
  • Japanese

Install the Force.com Migration Tool

Follow these steps to download and install the Force.com Migration Tool.
  1. Log in to a Salesforce organization on your deployment machine.
  2. From Setup, click Develop | Tools, and then click Force.com Migration Tool.
  3. Save the ZIP file locally and extract the contents to the directory of your choice.
Note

Note

  • If you don’t have Ant installed, see Prerequisites for Using the Force.com Migration Tool.
  • If you installed a previous version of the Force.com Migration Tool and copied the ant-salesforce.jar file to the Ant lib directory, delete the jar file in the lib directory. The lib directory is located in the root folder of your Ant installation. The Force.com Migration Tool uses the ant-salesforce.jar file that’s in the distribution ZIP file. You don’t need to copy this file to the Ant lib directory.

When you extract the Force.com Migration Tool ZIP files, the following folders and files are written to the location you specified:

  • A Readme.html file that explains how to use the tools
  • A Jar file containing the ant task: ant-salesforce.jar
  • A sample folder containing:
    • A codepkg\classes folder that contains SampleDeployClass.cls and SampleFailingTestClass.cls
    • A codepkg\triggers folder that contains SampleAccountTrigger.trigger
    • A mypkg\objects folder that contains the custom objects used in the examples
    • A removecodepkg folder that contains XML files for removing the examples from your organization
    • A sample build.properties file that you must edit, specifying your credentials, in order to run the sample ant tasks in build.xml
    • A sample build.xml file, that exercises the deploy and retrieve API calls