After you have resolved all configuration issues, you can migrate the configuration. When the configuration is migrated, configuration changes are made in the NSX-T Data Center environment to replicate the NSX-v configuration.
Verify that you have completed the Resolve Configuration step.
- From the Migrate Configuration page, click Start.
- The configurations of the pre-created NSX-v objects are migrated to NSX-T.
- The configurations of the vRealize Automation created resources are migrated to NSX-T.
- Verify that all the migrated configurations are displayed in your NSX-T environment.
You can verify the migrated configurations either in the NSX-T NSX Manager interface or by running the NSX-T APIs.Note:
- During the Migrate Configuration step, Security Tags from NSX-v are not migrated to NSX-T. Therefore, the Security Tag-based migrated dynamic Groups and Groups with static memberships in NSX-T are empty after this step is finished. The reason is that in NSX-v, a Security Tag is an object, whereas in NSX-T, a tag is an attribute of a VM. The tags are applied to the workload VMs only after the workloads are migrated to NSX-T during the Migrate Hosts step.
- When the configurations are migrated to NSX-T, the configuration changes are made in the NSX-T NSX Manager database, but it might take some time for the configurations to take effect.
- Click Continue to proceed to the Check Realization page.
If needed, you can roll back the migrated configurations. Rolling back does the following:
- Remove the migrated configuration from NSX-T.
- Roll back all the resolved issues in the previous step.
- Remove the vRealize Automation deployment configuration file.