Review these prerequisites before you perform migration.

You have two options for migrating tenants and identity stores. The option you choose depends on whether you enable or disable Enable SSO2 migration on the Migration tab of the vRealize Automation management console.

  • If Enable SSO2 migration is selected, migration automatically moves vRealize Automation 6.2.x tenants and identity stores to Horizon .

    If you choose this option, you must first perform one of the following procedures before running migration: Prepare to Migrate Tenants and Identity Stores for Linux or Prepare to Migrate Tenants and Identity Stores for Windows.


    The selected Enable SSO2 migration option does not support vSphere SSO. If you plan to migrate from vSphere SSO, use the deselected Enable SSO2 migration option.

  • If Enable SSO2 migration is deselected, you manually migrate tenants and identity stores using the procedures for an in-place upgrade before you run migration. See "Migrate Identity Stores to the VMware Identity Manager" in Upgrading from vRealize Automation 6.2 to 7.1.


  • Verify that you have a new target installation of vRealize Automation 7.1 whose components reflect the source 6.2.x environment.

  • Verify that endpoint names configured for agents, such as vSphere agents, running on the target system match the endpoint names used by the source installation.

  • Verify that installed agent names are be the same on both source and target systems for Hyper-V Hypervisor proxy agents, Citrix Xen Servers and Test agents.

  • To migrate to a cluster deployment, do the following when you deploy your vRealize Automation 7.1 target environment:

    1. Deploy a master and one or more secondary nodes.

    2. Configure the master node in the load balancer.

    3. Install vRealize Automation 7.1 in distributed mode on master but do not add any secondary nodes during the installation.

  • Verify that the target Microsoft SQL Server version for the vRealize Automation 7.1 IaaS database is either 2012 or 2014.

  • Verify that target Model Manager node has connectivity with the source and target Microsoft SQL Servers.

  • Verify that SSH is enabled on both the source and target vRealize Automation virtual appliances.

  • Verify that no VMware vCloud Application Director is configured.

  • Verify that each IaaS server node in the target environment has at least Java SE Runtime Environment (JRE) 8, Update 91 (64 bit) installed. After you install the JRE, make sure the JAVA_HOME system variable points to the Java version you installed on each IaaS node, and adjust the path if necessary.

  • Verify that each IaaS node has at least PowerShell 3.0 installed.


    PowerShell 3.0 is integrated with Windows Server 2012.

  • Verify that the source and target vRealize Automation environments are running.

  • Migrate tenants and identity stores.