To migrate your NSX Data Center environment from NSX for vSphere to NSX-T, you must provide details about your NSX for vSphere environment.

The migration coordinator service runs on one NSX Manager node.

Caution:

Deploy a new NSX-T Data Center environment to be the destination for the NSX Data Center for vSphere migration.

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

Prerequisites

  • Verify that the vCenter Server system associated with the NSX for vSphere environment is registered as a compute manager. See Add a Compute Manager.
  • If your NSX for vSphere environment uses Edge Services Gateways, verify that you have created an IP pool in the NSX-T environment to use for Edge TEPs. See Create an IP Pool for Edge Tunnel End Points.

Procedure

  1. Using SSH, log in as admin to the NSX Manager VM and start the migration coordinator service.
    NSX-Manager1> start service migration-coordinator
  2. From a browser, log in to the NSX Manager node on which you started the migration coordinator service. Log in as admin.
  3. Navigate to System > Migrate.
  4. On the Migrate NSX for vSphere pane, click Get Started.
  5. From the Import Configuration page, click Select NSX and provide the credentials for vCenter and NSX for vSphere.
    Note: The drop-down menu for vCenter displays all vCenter Server systems that are registered as compute managers. Click Add New if you need to add a compute manager.
  6. Click Start to import the configuration.
  7. When the import has finished, click Continue to proceed to the Resolve Configuration page.
    If the import fails due to incorrect edge node configuration translation, click the Failed flag to view information about the number and size of the required NSX Edge resources. After you deploy the correct number and size of edge nodes, click Rollback to roll back this migration attempt and restart the configuration import.