Network Mappings
Define source-to-target network mappings that tell the migration engine which target network each source network maps to. Network Mappings ensure VMs land on the correct VLAN, subnet, and IP range when migrated to the target infrastructure.
Overview
When migrating virtual machines from source to target infrastructure, each VM's network adapters must be reassigned to the correct target network. Network Mappings define these relationships — mapping a source network (e.g. VLAN 100 — Production) to a target network (e.g. Target-Prod-Subnet-01).
These mappings are consumed by the Nutanix Move migration engine when creating migration plans. Without correct network mappings, migrated VMs may land on the wrong network — causing connectivity failures post-migration.
How Mappings Are Used
Network Mappings feed directly into the Nutanix Move migration plan creation process. When a migration plan is generated for a move group, Clarity Migrate looks up the network mappings for each VM's source network adapters and pre-populates the correct target network in the Nutanix Move plan.
If a VM in a move group has a network adapter connected to a source network that has no mapping defined, the migration plan creation will fail or require manual network assignment. Define all required mappings before generating migration plans.
The mapping relationship is: Source Network (from CMDB, imported via VMware or Nutanix integration) → Target Network (configured on the target hypervisor). The Provider field identifies which hypervisor cluster owns the target network, allowing correct assignment when migrating to multiple target clusters.
Managing Network Mappings
Navigate to Planning → Source To Target → Network Mappings.
Click New. Select the source network from the dropdown (populated from CMDB network records) and the target network.
Click Create to save. The mapping will be used automatically when migration plans are generated for VMs on the source network.
The Network Mappings table shows all defined source → target relationships. Edit or delete mappings as infrastructure plans evolve.
Key Fields
| Field | Description |
|---|---|
| Source Network | The network in the source environment (e.g. a VLAN or port group from VMware). |
| Target Network | The corresponding network in the target environment. |
| Provider | The infrastructure provider (e.g. Nutanix AHV) that owns the target network. |
Common Scenarios
| Scenario | Approach |
|---|---|
| Same VLAN name on source and target | Still create an explicit mapping even if names match. Nutanix Move requires explicit mappings — it does not auto-match by name. |
| Multiple source VLANs mapping to the same target network | Create a separate mapping record for each source network. Many-to-one mappings are supported (multiple source networks can map to a single target). |
| Cross-site migration (source site A → target site B) | Use the Provider field to specify the target cluster at site B. Ensure target network names match exactly what is configured on that cluster. |
| VMs with multiple network adapters | Each adapter is mapped independently based on its source network. Ensure all VLANs used across all adapters in the move group have mappings defined. |
| Dev/test networks being decommissioned | If dev/test VMs are migrating to a shared target network, map their individual dev/test VLANs to the appropriate target. Do not leave non-production VLANs unmapped. |
Tips
- Define network mappings before creating migration plans. Migration plans reference these mappings — if they don't exist, VMs will need manual network assignment.
- Map all production, UAT, and development VLANs. Don't forget non-production networks. VMs in dev/test environments still need correct network assignments.
- Coordinate with the networking team. Target network names must exactly match what's configured on the target hypervisor. Verify names with the network engineering team before creating mappings.
- Review mappings when target infrastructure changes. If a target cluster is reconfigured or network names change, update mappings immediately to avoid plan generation failures.
- Validate after migration. After executing a move group, verify migrated VMs have the expected network adapters using the Nutanix Move post-migration report and CMDB network data.