How do I perform a brownfield migration

Using the migration assistant tool, you can perform a brownfield migration of your vRealize Automation 7 source instance and
VMware Aria Automation
8.
If you created infrastructure in
VMware Aria Automation
8 and want to align it with your vRealize Automation 7 infrastructure, you must run a migration assessment and then migrate your source environment. The migration assistant tool compares your existing
VMware Aria Automation
8 infrastructure to the infrastructure in your vRealize Automation 7 source environment. After this comparison, the migration tool only migrates the difference between the two environments.
For example: if you created a project named vSphere Users with one cloud template in
VMware Aria Automation
8 and your vRealize Automation 7 environment contains a business group named vSphere Users with four blueprints, the migration assistant tool only migrates the additional three blueprints (as VMware cloud templates) to the
VMware Aria Automation
8 vSphere Users project.
If the migration is rolled back, the existing
VMware Aria Automation
8 infrastructure is rolled back to its original state before the vRealize Automation 7 migration. Only the migrated source environment content is rolled back, leaving the pre-migration
VMware Aria Automation
8 content intact.
Post-migration cloud zone tags are not removed during rollback.
Before performing a brownfield migration, review these considerations:
Cloud Zones
For AWS and Azure, the reservations are merged into one when they use the same region criteria. Similarly, all vSphere reservations are merged into one cloud zone, if they contain the same computes. New tags are added to the cloud zone based on reservation name and reservation policy.
IP Ranges
If your source environment contains overlapping IP ranges, the migration to
VMware Aria Automation
8 fails.
Network Profiles
A new network profile is always created for on-demand networks. During migration, the source environment network profiles are merged into one when they contain the same regionId, isolation type, networks, security groups, and load balancers.
Storage Profiles
For Azure and vSphere, storage profiles are merged into one when they contain the same region and storage description. vRealize Automation 7 does not support storage profiles for AWS.
Projects
New zones are added to existing projects. If the zone exists in the project, the memory limit, instances, and storage limits are set to the maximum of existing project and source projects. Priority is set to the lowest of the two (lower is higher). The user roles of existing projects are also updated if the user already exists.