You can migrate your cluster of vRealize Orchestrator 6.x instances installed on Windows to a cluster of vRealize Orchestrator 7.3 Virtual Appliances.


  • Set up a load balancer to distribute traffic among multiple instances of vRealize Orchestrator. For more information, see vRealize Orchestrator Load Balancing.

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

  • 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 of the source Orchestrator instances.

  • Back up the database, including the database schema, of the external Orchestrator.


    If you plan to use the source Orchestrator environment until the new one is fully configured, create a copy of the source database. Otherwise, you can configure the target Orchestrator to use the same database but in that case the source Orchestrator environment will no longer work because the database schema is upgraded to the version of the target Orchestrator.


  1. Download the migration tool from the target Orchestrator server.
    1. Log in to Control Center as an administrator.
    2. Open the Export/Import Configuration page and click the Migrate Configuration tab.
    3. Download the migration tool as specified in the description, 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 one of the source Orchestrator server nodes.
    1. Set the PATH environment variable by pointing it to the bin folder of the Java JRE installed with Orchestrator.
    2. Upload the migration tool to the Windows server, on which the source Orchestrator is installed.
    3. 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.

    4. Run the Windows command prompt as administrator and 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.

    5. 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 is created in the same folder as the migration-cli folder.

  3. Import the configuration to the target Orchestrator server.
    1. Open Export/Import Configuration in Control Center and click the Migrate Configuration tab.
    2. Browse to the exported configuration file and click Import.
    3. Select the type of files that you want to import.



      Migrate database settings

      Uses the database of the vRealize Orchestrator 6.x cluster.


      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.

      Migrate plug-ins

      Migrates all plug-ins that are not included in the Orchestrator platform.

      Migrate legacy plug-in configurations

      Migrates the configuration of plug-ins that is stored in the Orchestrator_install_folder\app-server\conf\plugins folder.

      Migrate trusted certificates

      Migrates all certificates from the trust store of the vRealize Orchestrator 6.x cluster.

    4. Click Finish Migration.

      A message indicates that the migration completed successfully.

    The Orchestrator server service restarts automatically.

  4. Reconfigure the Orchestrator cluster.
    1. Open the advanced Orchestrator Cluster Management page, at https://your_orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/#/control-app/ha?remove-nodes.
    2. Select the check boxes next to the Orchestrator 6.x nodes and click Remove.

      Refresh the browser page by clicking the F5 button on the keyboard.

  5. On the Startup Options page, make sure that the Active Configuration Fingerprint and the Pending Configuration Fingerprint strings match.

    You might need to refresh the page several times until the two strings match.

  6. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.
  7. Deploy a new Orchestrator instance on the target version.
  8. Join the instance to the vRealize Orchestrator 7.3 node.

    For more information, see Configuring an Orchestrator Cluster.

  9. (Optional) Repeat Step 7 and Step 8 for each additional node you are adding to the cluster.


You successfully migrated a vRealize Orchestrator 6.x cluster to a cluster of Orchestrator Virtual Appliances on version 7.3.

What to do next

  • On the Orchestrator Cluster Management page, make sure that the Active Configuration Fingerprint and the Pending Configuration Fingerprint strings on all nodes in the cluster match.


    You might need to refresh the page several times until the two strings match.

  • Verify that the vRealize Orchestrator cluster is configured properly by opening the Validate Configuration page in Control Center.

  • Log in to the Orchestrator client and verify whether the configurations of all installed plug-ins are correct.