You can perform a side-by-side upgrade of your current vRealize Automation environment using migration.

Migration moves all data, except for tenants and identity stores, from your current vRealize Automation source environment to a target deployment of the latest version of vRealize Automation. In addition, migration moves all data from the embedded vRealize Orchestrator 7.x to the target deployment.

Migration does not change your source environment except to stop vRealize Automation services for the time required to collect and copy the data safely to your target environment. Depending on the size of the source vRealize Automation database, migration can take from a few minutes to hours.

You can migrate your source environment to a minimal deployment or a high-availability deployment.

If you plan to put your target environment into production after migration, do not put your source environment back into service. Changes to your source environment after migration are not synchronized with your target environment.

If your source environment is integrated with vCloud Air or vCloud Director or has physical endpoints, you must use migration to perform an upgrade. Migration removes these endpoints and everything associated with them from the target environment. Migration also removes a 6.x VMware vRealize Application Services integration from the target environment.


You must complete additional tasks to prepare your vRealize Automation virtual machines before you migrate. Before you migrate, review Knowledge Base article 51531.

If you migrate from vRealize Automation 6.2.x to the latest version, you might experience these issues.



After you migrate from vRealize Automation 6.2.x to the latest version, catalog items that use these property definitions appear in the service catalog but are not available to request.

  • Control types: Check box or link.

  • Attributes: Relationship, regular expressions, or property layouts.

In vRealize Automation 7.x, the property definitions no longer use these elements.

You must recreate the property definition or configure the property definition to use a vRealize Orchestrator script action rather than the embedded control types or attributes. For more information, see Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request.

Regular expressions used to define the parent-child relationships in a vRealize Automation 6.2.x drop-down menu are not supported in 7.x. In 6.2.x, you can use regular expressions to define one or more child menu items that are only available for a certain parent menu item. Only those child menu items appear when you select the parent menu item.

After migration to 7.x , all the available menu items appear in the child drop-down menu regardless of what you choose in the parent drop-down menu. To show that previously defined dynamic values no longer work, the first menu item in the child drop-down menu reads "Warning! Use vRO workflows to define dynamic values."

After migration, you must recreate the property definition to restore the previous dynamic values. For information about creating a parent-child relationship between the parent drop-down menu and the child drop-down menu, see How to use dynamic property definitions in vRA 7.2.