Before you can use the migration assistant tool to migrate your vRealize Automation 7 source environment to vRealize Automation 8, ensure that these prerequisites are met.
Migration Prerequisites
- Backup your vRealize Automation 7 source environment.
- If your source vRealize Automation 7 content has dependencies on an external vRealize Orchestrator, you must first migrate vRealize Orchestrator. See Migrating vRealize Orchestrator.
- Create or migrate tenants using vRealize Suite Lifecycle Manager.
- You must first import and install the IPAM plugin in Cloud Assembly to migrate an IPAM endpoint. For more information, see Download and deploy an external IPAM provider package for use in vRealize Automation.
- After running a migration assessment, the vRO Azure endpoint configuration is populated on the Configuration tab. Before running a migration, you must manually enter the key by editing the configuration with the https://FQDN/migration-ui/#/global-config link. If you attempt to migrate without providing the endpoint key, the migration fails.
-
For subscriptions, the input type 'payload' is not supported in vRealize Automation 8. Before migrating your vRealize Automation 7 subscriptions, you must update the input type to 'Properties'.
- vRealize Automation 8.1 did not require you to accept a source certificate during migration assessment. As a result, you must reassess your source environment. To reassess your source environment and accept the source certificate: delete the source environment, re-add it, accept the certificate, and reassess the source environment using the migration assistant service.
- Ensure your vRA license is up-to-date and active before proceeding with migration.
Note: The vRealize Automation 7.x advanced license supports public cloud, however the vRealize Automation 8 advanced license does not. During the migration assessment, any public cloud items are flagged.
- In preparation for migration, ensure you exclude virtual machine memory from snapshots on the target environment.
