You can migrate your cluster of vRealize Orchestrator 6.x instances installed on Windows to a cluster of vRealize Orchestrator 7.4 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 source Orchestrator database, including the database schema.
    Note: 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, 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 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.
      Note: 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. 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. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.
  6. Deploy a new Orchestrator instance on the target version.
  7. Join the instance to the vRealize Orchestrator 7.4 node.
    For more information, see Configuring an Orchestrator Cluster.
  8. (Optional) Repeat Step 6 and Step 7 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.4.

What to do next

  • 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.