The migration process gathers data from your source vCloud Automation Center system and migrates that data to the clean vRealize Automation target system. Information about migration is captured in the pre-migration and migration reports and logs. You can use information in the reports to recreate data that was not migrated.
Migration to vRealize Automation 6.2 requires that the source system be at vCloud Automation Center 5.2.3 and the target system be at vRealize Automation 6.2 or a later 6.2.x version.
All instances of vCloud Automation Center 5.2, in reference to migration to vRealize Automation 6.2 represent vCloud Automation Center 5.2.3.
The migration process consists of the following main steps.
Install and configure the target vRealize Automation system.
Download the migration tool and run the pre-migration task.
Review the pre-migration report.
Take corrective action based on information in the report and rerun pre-migration.
(Optional) When you are satisfied with the content of the pre-migration report, take the source system offline and rerun pre-migration a final time.
Perform specified manual tasks after pre-migration is finished and before starting migration.
Run the migration task, including reviewing the migration prerequisite checker report before proceeding with the task.
Review the migration report.
Perform post-migration tasks.
The general migration process is captured in the following flow diagram.
You migrate data to a single tenant configuration in the target vRealize Automation, namely the default vsphere.local tenant. You cannot change the target tenant name or migrate to another tenant or to multiple tenants. You must configure the default tenant identity store for Native Active Directory and assign a tenant administrator before you start the migration tool.
Migrate to a clean vRealize Automation target system. You can recreate branding graphics, approval policies, and some customization files in the target system before you migrate, but other work you do in the target system is overwritten during migration.
The sAMAccountName security format strings for user names and groups are converted to userPrincipalName format, for example from mycompanydomain\joe.user to firstname.lastname@example.org.
The migration process creates a service named Infrastructure in the target system. Enabled blueprints are published to this service during migration. You can add services after migration is finished.
If you encounter problems after migration, or migration did not finish successfully, you can shut down the target vRealize Automation system and restart the source vCloud Automation Center 5.2 system.