The vRealize Automation 8 migration assistant has these deployment limitations.

  • Migration of a deployment is final regardless of whether it succeeded or failed. You cannot retry a deployment migration. You can rerun the plan created by the migration service, under Onboarding service.
  • Once migrated, you cannot change the owner of a deployment. Migrated deployments are owned by the user that performed the migration. The original deployment owner is added as a custom property on a machine resource post-migration. To make the deployment accessible to other project members, add the user to the project and enable project share deployments among members.
  • Historical costing information is not migrated with deployments. For more information on pricing and costs, see What are Pricing Cards.
  • If you migrate a deployment that contains an IPAM-managed IP and then delete the migrated deployment from vRealize Automation 8, you must also manually delete the associated IP address from Infoblox.
  • If your source environment includes a load balancer configured to an existing network that is not connected to a machine, the external network is not migrated and the IP is not allocated during migration.
  • Deployment migration migrates the associated blueprints but they are no longer linked to the deployment post-migration. If you run an Update on a migrated deployment, it recreates the machine.
  • vRealize Automation 7 does not collect data from Azure endpoints nor can it identify if an Azure machine was deleted outside of vRealize Automation 7. During Migration Assessment in vRealize Automation 8, any deleted Azure deployments are listed as Ready but are excluded during migration because the migration assistant cannot find the VMs.
  • You cannot migrate a source deployment if it has one or more Nat network components for NSX-T, or one or more network components routed or Nat (or both) to NSX-T.
  • If your source deployment contains more than one NSX Load Balancer component, they are migrated as a single Load Balancer component.
    Note: Not all routes are created on the single component.
  • The IP address configured to the NAT network in your source deployments is not marked as allocated post migration. However, the IP addresses of migrated load balancers and VMs are marked as allocated under Infrastructure > Networks > IP Address post migration.
  • If your source vRealize Automation 7 deployment contains an invalid resource, for example it does not have properties for a resource, then the resource is not migrated. If all the resources are invalid in the deployment, the entire deployment is not migrated.
  • During brownfield migration, both onboarded and migrated machines are not linked to cloud zones. As a result, these machines are not calculated into storage maximum definitions.