A subset of NSX-V features is supported for migration.
Most features have some limitations. When you import your NSX-V configuration for migration, you will get detailed feedback about what features and configurations in your environment are supported or not supported.
See Detailed Feature Support for Migration for detailed information about what is supported for migration.
| NSX-V Feature | Supported | Notes |
|---|---|---|
| VLAN-backed logical switches | Yes | |
| Overlay-backed logical switches | Yes | |
| L2 Bridges | No | |
| Transport Zones | Yes | |
| Routing | Yes | |
| East-West Micro-Segmentation | Yes | |
| Edge Firewall | Yes | |
| NAT | Yes | |
| L2 VPN | Yes | |
| L3 VPN | Yes | |
| Load Balancer | Yes | |
| DHCP and DNS | Yes | |
| Distributed Firewall | Yes | |
| Service Composer | Yes | |
| Grouping objects | Yes | Limitations include number of items, and dynamic expressions making up security groups. |
| Guest Introspection | Yes | Supported for end-to-end migration only. Only Guest Introspection service configuration is migrated. Partner service registration, partner service VMs, and vendor templates are not migrated. Before migration, the partner service must be registered with NSX-T to create the respective service and vendor templates in NSX-T. Consult the VMware partner before proceeding with migration. |
| Network Introspection | Yes | Supported for end-to-end migration only. Only Network Introspection service configuration is migrated. Partner service registration, partner service VMs, and vendor templates are not migrated. Before migration, the partner service, vendor templates, and Partner Management Console/Partner Service Manager must be registered with NSX-T. Consult the VMware partner before proceeding with migration. |
| Cross-vCenter NSX | (NSX-T 3.2.1 and later) Yes (NSX-T 3.2.0) Yes (with no secondary NSX Managers) |
(NSX-T 3.2.1 and later) Only supported if you choose the Migrate NSX for vSphere mode and User Defined Topology. (NSX-T 3.2.0) Migration of a single site NSX-V deployment that contains an NSX Manager in primary mode, no secondary NSX Managers, and with universal objects on the primary site, is supported. The NSX-V deployment is migrated to a single site NSX-T environment (non-federated) with local objects. |
| NSX-V with a Cloud Management Platform, Integrated Stack Solution, or PaaS Solution. | Yes | Migration of NSX-V with vRealize Automation is supported. Contact your VMware representative before proceeding with migration. Scripts and integrations might break if you migrate the integrated environments:
For example:
|
