Most data is migrated from your source system to your target vRealize Automation system. Use the pre-migration and migration reports to help recreate data that is not migrated.

The pre-migration and migration reports are located in the reports subdirectory of the directory in which the downloaded migration tool is extracted.

Table 1. Understanding What Data is Migrated

vCloud Automation Center Item

Migrates Yes or No

Details and Related Information

Administrator and user roles

Yes

See Migrating Administrator and User Roles.

User and group identities

Yes

See Migrating Users and Groups.

User security settings

Yes

See Migrating User Security Settings.

Endpoints

Yes

Endpoint information is migrated. Associated machine and compute resource information is also migrated. Endpoint information is captured in reports. You can update your endpoints before or after migration. See the support matrix invRealize Automation product documentation for a list of supported endpoints.

Blueprints

Yes

See Migrating Blueprints and Migrating Entitlements.

Reservations and reservation policies

Yes

Machine and compute resource information is also migrated. Reservations retain their settings, including capacity alerts, memory, priority, storage, and so on. Each reservation is configured for a named business group. Business group users can request machines on a specified compute resource.

Storage reservation policies and storage cost profiles

Yes

Compute resources

Yes

Compute resource information is migrated, including cost profile, storage cost profile, storage reservation policy, custom properties, and so on. The associated machine and reservation information for each business group is also migrated.

Distributed Execution Managers, DEM skills, and agents

Yes

See Migrating DEM and Agent Information.

Network profiles

Yes

Cost profiles

Yes

Supplied custom properties

Yes

See Migrating Custom Properties.

Supplied workflows

Yes

Standard workflows are migrated. Custom workflows are not migrated.

Machines, including lease, linked clone, and machine limit settings

Yes

Machine and compute resource information is migrated. See Migrating Machines.

Global properties

Yes

Global properties that are supported in the target system are migrated.

Snapshots

Yes

Deployment customizations, including custom workflows, events, built-in stubs, plug-ins, email customizations, and so on

No

Record all customization information before migrating. Consider uninstalling customizations before starting the migration process. If you received customization packages from VMware or from a third party, and you still want to use the customizations after migration, check with the contact who authored the customizations to request updated versions.

Branding graphics

No

You can recreate branding graphics in the target system before or after you run the migration task.

Blueprint icons

No

See Migrating Blueprints.

Licenses

No

Local machine users and built-in users

No

Approval policies

No

Approval policies are not migrated but a generic approval policy is created in the target system. See Migrating Approval Policies.

You can recreate approval policies in the target system before or after you run the migration task. See Recreating Approval Policies.

Guest agent ISO settings or Guest agent vRealize Automation management addresses

No

See Migrating DEM and Agent Information and Recreating ISOs and Templates That Contain a Guest Agent.

Email settings, including email customizations

No

Email configuration settings do not migrate. Recreate email configuration and settings when migration finishes. For information, see Recreating Email Notifications.

Notifications

No

Notification settings do not migrate. Recreate notification settings when migration finishes. For information, see Recreating Email Notifications.

Active or pending requests and approvals including reconfiguration, leasing, and reclamation

No

Allow all workflows and pending actions to complete before you start the migration task.