Target side

• NSX Manager installed and configured in the target Virtual Center. Minimum supported versions:
  • NSX-T 3.0 or higher
• NSX Manager should be registered in HCX Cloud Manager's Appliance-Management(9443) UI. NSX admin credentials are required.
• NSX-V at cloud is officially unsupported for HCX cloud manager running 4.4.x or later.
• The cluster where HCX appliances will be deployed should be NSX host prepared. 
• An NSX Transport Zone capable of creating Overlay networks in the cluster where HCX appliances will be deployed. 

• For HCX Cloud version running 4.3.x and below, NSX-V at cloud should have an NSX Edge or DLR to connect the extended network.
• NSX-V at Cloud is unsupported with Network Extension HA feature. Only Standalone NE appliance should be used for extension.
• For NSX-V at cloud, the Proximity Routing feature is already deprecated with HCX cloud.
• NSX-T should have a Tier-1 router to connect the extended network.
• If using Mobility Optimize Networking (MON) feature, a Tier-0 router must be configured.

• The cluster where the VMs are being migrated into should be NSX host prepared. 
• An NSX Transport Zone capable of creating Overlay networks in the cluster where the VMs are being migrated into.

• No other requirements.

Source side 

• NSX-V installed and configured in the source vCenter should have a minimum supported versions 6.4.0 or higher. Refer to Interop Matrix.
• NSX registration with HCX is required on the source side only for the following use cases:
  • Extend NSX logical networks
  • Migrate NSX Tags
• If registered, the same NSX requirements listed for the target side are applicable to the source side.
• NSX-V can be registered with HCX at source/connector side for DC evacuation and V2T migration projects.