Migrate your 5.5.x and 6.x Orchestrator Windows standalone configuration to the Orchestrator Appliance.


  • Deploy and configure an Orchestrator node on the target version. See Configuring a Standalone Orchestrator Server.

  • If the source Orchestrator uses a SHA1 package-signing certificate, make sure to regenerate the certificate using a stronger signing algorithm. The recommended signing algorithm is SHA2.

  • Stop the Orchestrator server service on both the source and the target Orchestrator instances.

  • Back up the source Orchestrator database, including the database schema.


    If you plan to preserve the source Orchestrator environment after migration, clone the source Orchestrator database to another database. Afterwards, configure the target Orchestrator to use the cloned instance, instead of the instance configured during installation. If you skip this step, the target Orchestrator will upgrade the source Orchestrator database and it will no longer work with the source Orchestrator environment.


  1. Download the migration tool from the target Orchestrator server.
    1. Log in to Control Center as root.
    2. Open the Export/Import Configuration page and click the Import Configuration tab.
    3. Download the migration tool as specified in the description on the page, or download it directly from https://orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/api/server/migration-tool.
  2. Export the Orchestrator configuration from the source Orchestrator server.
    1. Extract the downloaded archive in the Orchestrator install folder.

      The default path to the Orchestrator install folder in a Windows-based installation is C:\Program Files\VMware\Orchestrator.

    2. Set the PATH environment variable by pointing it to the bin folder of the Java JRE installed with Orchestrator.
    3. Use the Windows command prompt to navigate to the bin folder under the Orchestrator install folder.

      By default, the path to the bin folder is C:\Program Files\VMware\Orchestrator\migration-cli\bin.

    4. Run the export command from the command line.
      C:\Program Files\VMware\Orchestrator\migration-cli\bin\vro-migrate.bat export

      This command combines the VMware vRealize Orchestrator configuration files and plug-ins into an export archive.

      An archive with file name orchestrator-config-export-orchestrator_ip_address-date_hour.zip is created in the same folder as the migration-cli folder.

  3. Import the configuration to the target Orchestrator instance.
    1. Log in to Control Center as root.
    2. Open Export/Import Configuration in Control Center and click the Import Configuration tab.
    3. Browse to and select the .ZIP file exported from the source Orchestrator instance.
    4. Enter the password that you used when exporting the configuration.

      Leave blank if you did not export the configuration with a password.

    5. Select the import type.
    6. If you are importing the configuration to an external Orchestrator server, choose whether to import the database settings.

      If the source and target Orchestrator servers are not configured to use the same external database, leave the Migrate database settings check box unselected to avoid upgrading the database schema to the newer version. Otherwise the source Orchestrator environment stops working.

      You must configure the database that the target Orchestrator will use before the migration.

    7. Click IMPORT to finish the migration.

      A message states that the configuration is successfully imported. The Orchestrator server service of the target Orchestrator instance restarts automatically.

  4. If the target vRealize Orchestrator uses an authentication provider server that is different from the one used by the source Orchestrator, import to the trust store of the target Orchestrator the SSL certificate of the authentication provider it is configured to use.
    1. On the Certificates page in Control Center, click Import from URL.
    2. Provide the URL of the vRealize Automation or vSphere instance.


A message indicates that the migration finished successfully. The Orchestrator server service restarts automatically.

What to do next

Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.