To migrate NSX Data Center for vSphere that is integrated and used with vRealize Automation, the migration coordinator must have details about the NSX-v topology, the object configurations, and the resource configurations created in vRealize Automation.

The migration coordinator service runs on one NSX Manager node.


  • Verify that the vCenter Server system associated with the NSX-v environment is registered as a compute manager in NSX-T Data Center. See Add a Compute Manager.
  • Generate a deployment configuration file in a .json format from the vRealize Automation environment. The configuration file must be valid and conform to a predefined JSON schema.
  • If your NSX-v 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.
  • Using SSH, log in as admin to the NSX Manager VM and start the migration coordinator service.
    NSX-Manager1> start service migration-coordinator


  1. From a browser, log in to the NSX Manager node on which you started the migration coordinator service. Log in as admin.
  2. Navigate to System > Migrate.
  3. In the NSX for vSphere with vRealize Automation pane, click Get Started.
  4. From the Import Configuration page, click Select NSX and provide the credentials for vCenter Server and NSX-v.
    Note: The drop-down menu for vCenter Server displays all vCenter Server systems that are registered as compute managers. Click Add New if you need to add a compute manager.
  5. In the Upload Deployment Configuration File section, click Select File. Select the .json configuration file that was generated from the vRealize Automation environment, and click Upload.
    After uploading a file, if necessary, you can click Select File again and upload a different file. The previous file is overwritten. You cannot remove the .json file after it is uploaded in the migration coordinator. The migration coordinator removes this configuration file from the NSX Manager appliance only when you take any of the following actions:
    • Cancel the migration.
    • Roll back the migration on the Import Configuration page or the Migrate Configuration page of the migration coordinator.
    • Finish the migration on the Migrate Hosts page.
  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.
    • If syntax errors are found in the deployment configuration file, import fails during the translate configuration step. Roll back the migration, resolve the syntax errors in the .json file, and import the configuration again.
    • If import configuration fails due to schema mismatch errors, review the error messages, roll back the imported configuration, and upload a valid configuration file to start a new migration. The error message in the migration coordinator UI might not display all the possible reasons for the schema mismatch errors. For a complete information about the schema mismatch errors, see the migration log (cm.log file) on the NSX Manager appliance where the migration coordinator service is running.

      You can find this log file at /var/log/migration-coordinator/v2t, and use it for further troubleshooting purposes.


When the NSX-v with vRealize Automation topology is imported successfully, the View Imported Topology link is enabled. Click this link to view a graph of the imported topology. However, the topology viewer does not work for a scaled NSX-v environment.