6.2

The migration process creates one principal extension for each UPN and adds the extensions to the
target default tenant.
For related information, see Prerequisites for vRealize Automation Migration. For details about
establishing domain trust during vRealize Automation installation and configuration, and about configuring
the Identity Appliance see Installation and Configuration in the vRealize Automation documentation.
Migrating Blueprints
Blueprints are migrated to the target system and published to the vRealize Automation catalog as catalog
items, with some exceptions.
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.
Blueprint management, including approval and entitlement management, has changed. For more
information, see Changes from vCloud Automation Center 5.2 and Foundations and Concepts in
vRealize Automation documentation. The Changes from vCloud Automation Center 5.2 PDF is available
online with the 6.0 documentation.
Note Consider reducing the number of provisioning groups and special case blueprints before migration
to keep the number of migrated entitlements to a minimum. In addition to the two standard entitlements,
an entitlement is also created for each blueprint for which restricted access is configured.
The following considerations are helpful in understanding how blueprints are migrated.
n
Migration creates a single, default policy that is configured to require only the approval of the
business group manager. The migration process adds the approval policy to each catalog item
entitlement for each blueprint that had an approval configured in the source system.
n
Blueprint approval settings such as machine resource settings for CPU, memory, and storage are not
migrated. However, approval information is captured in the pre-migration report. Reference the pre-
migration report when you recreate approvals in the target vRealize Automation system.
n
ISO location information in the build profiles and blueprints and template information in the blueprints
is migrated. However, you must reconfigure the ISOs and templates after migration to point to the
system on which the manager service is running, for example a virtual machine or a load balancer.
After migration is finished, recreate ISOs and templates that contain a guest agent.
n
Blueprints that are disabled are migrated but are not published to the catalog or listed as an entitled
catalog item on the Entitlements page.
n
vCloud Networking and Security configurations are not migrated for multi-machine blueprints.
n
vCloud Director vApps and vApp components are migrated but only the vCloud Director vApp
components are published.
n
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.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 14