6.2

7 Run the migration task, including reviewing the migration prerequisite checker report before
proceeding with the task.
8 Review the migration report.
9 Perform post-migration tasks.
The general migration process is captured in the following flow diagram.
No
Yes
No
Yes
Complete all workflows
Stop 5.2.3 services
vCAC
version?
Migration
5.2.3
Upgrade
Install new 6.2
environment
Outage
Window
Stop 6.1 services, shut
down and back up 6.2
Back Up 5.2.3 database
Disable access to 5.2.3
Replace 6.2 database
with 5.2.3 database
copy
Run migration tool
with migration
Run migration
tool with
pre-migration check
Recreate advanced
approvals in 6.2
environment
(optional)
Test and perform
post-migration
tasks
Bring up rest of
6.2 system
Issues
found?
Direct traffic to
6.2 system
Address
issues
Migration
failure?
6.1
Bring up 5.2.3
environment
Back up
5.2.3 system
Run data
collection on
5.2.3 endpoints
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.
Caution 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.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 8