The migration process includes setting up a new NSX-T environment and running the migration coordinator. You also might need to change your existing NSX-V environment to ensure that it can migrate to NSX-T.


Deploy a new NSX-T environment to be the destination for the NSX-V migration.

During the Import Configuration step, all NSX Edge node interfaces in the destination NSX-T environment are shut down. If the destination NSX-T environment is already configured and is in use, starting the configuration import will interrupt traffic.

During the migration, you will complete the following steps:
  1. Create a new NSX-T environment.
    • Deploy a single NSX Manager appliance to create the NSX-T environment.
    • If you plan to use Maintenance Mode migration for hosts, configure a shared storage on the cluster to be migrated from NSX-V to NSX-T. This enables automated vMotion for the migration process. Any VMs that do not meet this criterion must be manually powered off prior to migration or manually vMotioned.
    • Configure a compute manager in the NSX-T environment. Add the vCenter Server as a compute resource.
      Important: Use the exact IP or hostname specified in NSX-V vCenter Server registration.
    • Start the migration coordinator service.
    • If you want to import users from NSX-V, set up VMware Identity Manager.
    • If your NSX-V topology uses Edge Services Gateways, create an NSX-T IP pool to use for the NSX-T Edge TEPs. These IPs must be able to communicate with all the existing NSX-V VTEPs.
    • Deploy NSX Edge nodes.
      • Deploy the correct number of appropriately sized NSX-T Edge appliances.
      • Join the Edge nodes to the management plane from the command line.
    • If Security Policies in your NSX-V environment use third-party Guest Introspection or Network Introspection services provided by partners, the partner services must be registered with NSX-T.
  2. Import configuration from NSX-V.
    • Enter the details of your NSX-V environment.
    • Upload a vRealize Automation deployment configuration file in .json format as an input to the migration coordinator.
    • The configuration is retrieved and pre-checks are run.
  3. Resolve issues with the configuration.
    • Review messages and the reported configuration issues to identify any blocking issues or other issues that require a change to the NSX-V environment.
      • If you make any changes to the NSX-V environment while a migration is in progress, you must restart the migration and import the configuration again.
    • Provide inputs to configuration issues that must be resolved before you can migrate your NSX-V environment to NSX-T. Resolving issues can be done in multiple passes by multiple people.
  4. Migrate configuration.
    • After all configuration issues are resolved, you can migrate the configuration to NSX-T. Configuration changes are made on NSX-T, but no changes are made to the NSX-V environment yet.
  5. Check realization of migrated configurations in NSX-T.
    • Check whether the migration coordinator shows any unrealized configuration errors.
    • Download an intermediate output mapping file and share it with the vRealize Automation cloud administrator for an initial review.
    • Take appropriate actions to resolve any missing configurations in NSX-T before proceeding to Edge migration.
  6. Migrate Edges.
    • Routing and Edge services are migrated from NSX-V to NSX-T.
      Caution: North-South traffic is interrupted during the Migrate Edges step. All traffic that was previously traversing through the Edge Services Gateways (North-South traffic) moves to the NSX-T Edges.
  7. Migrate Hosts.
    • NSX-V software is removed from the hosts, and NSX-T software is installed. VM interfaces are connected to the new NSX-T segments.
      Caution: If you select In-Place migration mode, there is a traffic interruption for a few seconds during the Migrate Hosts step. However, if you select Maintenance migration mode, traffic interruption does not occur.
    • Download the final output mapping file after the hosts in all the clusters are migrated to NSX-T.
  8. Finish Migration.
    • After you have verified that the new NSX-T environment is working correctly, you can finish the migration, which clears the migration state.
  9. Perform post-migration tasks.
    • Deploy two additional NSX Manager appliances before you use your NSX-T environment in a production environment.
    • Uninstall NSX-V environment.

Note: Logical ports and switches that are created during migration are not deleted when the workload VMs are deleted. You must delete these ports and switches via the NSX Manager UI or the API.