Prerequisites and Access Configuration

Proxmox VE now includes a dedicated import wizard specifically for migrating VMware ESXi-based virtual machines. This feature targets operators moving existing workloads to a new hypervisor without manual disk extraction or re-creation. The migration process involves converting disk formats from VMware standards to Proxmox-native formats, a step that is automated within the wizard but requires specific preconditions to succeed.

Before initiating the import, you must establish a stable network connection between the Proxmox host and the ESXi host. The ESXi host must be running and accessible via its management IP. You cannot migrate from a vCenter server directly through this wizard; the wizard connects to the ESXi host itself. Ensure that the Proxmox host has outbound network access to the ESXi host on ports 443 (HTTPS) and 902 (NBD, if applicable for disk streaming, though the wizard typically handles this via vSphere API).

• ESXi Host: Must be running ESXi 6.5 or later. Verify the host is not in maintenance mode.
• Proxmox Host: Must have sufficient local storage space for the target VMs. The import wizard does not support streaming directly to remote Ceph or ZFS pools during the initial import phase in most configurations; it typically stages to local disk or requires the target storage to be mounted and accessible. Check your storage configuration in the Proxmox web interface.
• Credentials: You need an ESXi user account with sufficient privileges to read VM configurations and access virtual disks. A dedicated service account is recommended over using root.

Operators must ensure proper access credentials are configured to the ESXi host before starting the import. Test this connectivity from the Proxmox command line to rule out network or firewall issues before relying on the web interface. Use curl to verify the ESXi API is reachable:

curl -k https://<ESXI_HOST_IP>/api/vpxd/server.html

If this command fails, the import wizard will fail. Do not proceed until this endpoint responds. The import wizard is accessible via the Proxmox VE web interface for existing ESXi workloads, but it relies on this underlying API connectivity.

Initiating the Import Wizard in Proxmox VE

Log in to the Proxmox VE web interface. Navigate to the Datacenter node, then select the specific Proxmox node where you want the VM to reside. In the main panel, click the VM tab, then select Create VM. This opens the standard VM creation dialog, but you will see a new option or tab labeled Import from VMware (or similar, depending on the exact Proxmox version). Select this option.

1. Source Configuration: Enter the ESXi host IP address or hostname. Input the username and password for the ESXi service account. Click Connect. The wizard will fetch the list of available VMs on that host.
2. VM Selection: From the dropdown, select the specific VM you wish to migrate. The wizard will display basic metadata such as the VM name, vCPU count, and RAM allocation.
3. Target Configuration: Specify the target storage location (e.g., local-lvm, zfs-pool). Choose the target bridge for the network interfaces (more on this in the next section). Set the VM ID if you want a specific ID; otherwise, Proxmox will assign the next available one.
4. Start Import: Click Import. The wizard will begin the process. This is not instantaneous. For large disks, this can take hours. Monitor the progress bar in the web interface. You can also check the task log by clicking the task ID in the top right menu of the Proxmox interface.

The import wizard handles the heavy lifting of pulling the VMX configuration and copying the virtual disks. It does not, however, guarantee that the VM will boot on the first try. The conversion of disk formats from VMware (VMDK) to Proxmox standards (RAW, QCOW2, or VMDK on Ceph) is the core of this process. The wizard uses the vSphere API to read the disk data and write it to the Proxmox storage backend. This is a network-bound operation. Ensure your network link between the hosts is not a bottleneck.

Handling Disk Conversion Pitfalls

The migration process involves converting disk formats from VMware to Proxmox standards. This is where most failures occur. The wizard attempts to handle this automatically, but there are known pitfalls.

• Thin Provisioning Mismatch: If the source VMDK is thin-provisioned, the wizard will attempt to preserve this. However, if the target storage does not support thin provisioning (e.g., some LVM configurations without proper setup), the import may fail or result in a full allocation. Check your target storage type. ZFS and Ceph handle thin provisioning natively. LVM requires careful configuration.
• Snapshot Handling: The import wizard typically does not handle ESXi snapshots well. If the source VM has snapshots, the wizard may fail or import only the base disk, losing the snapshot chain. Before starting the import, consolidate all snapshots on the ESXi host. This is a critical prerequisite. If you do not consolidate, the import will likely fail with a disk format error.
• Disk Size Limits: Ensure the target storage has enough space for the used space of the VMDK, not just the provisioned size. The wizard copies actual data blocks. If the target pool is full, the import will abort mid-process, leaving a corrupted VM entry. Clean up failed imports manually via the Proxmox GUI or command line if this happens.

If the import fails during disk conversion, check the task log for specific errors. Common errors include “No space left on device” or “Invalid disk format.” In the latter case, verify that the source VMDK is not corrupted on the ESXi host. You can test this by attempting to mount the VMDK on a temporary Linux VM on ESXi. If it is corrupted, you must repair it on the source before migrating.

Network Re-mapping and Interface Configuration

Network interfaces must be re-mapped during the import process to align with Proxmox bridge configurations. VMware ESXi uses virtual switches (vSwitch) and port groups. Proxmox uses Linux bridges (e.g., vmbr0). The import wizard will detect the network interfaces of the source VM and attempt to map them to the target bridge you selected.

However, this mapping is not always perfect. VMware VMs often have multiple network interfaces with specific MAC addresses. The wizard will create corresponding interfaces in Proxmox, but you may need to adjust the order or type (e.g., bridged vs. routed).

• MAC Address Preservation: The wizard typically preserves the MAC addresses of the source VM. This is good for maintaining static IP configurations. However, if you are using DHCP, the new MAC addresses may cause issues if your DHCP server has reservations tied to the old MACs. Update your DHCP reservations if necessary.
• Bridge Selection: Ensure the bridge you select in the wizard is the correct one for your network topology. If you are migrating a VM that was on a private vSwitch, you must create a corresponding bridge on Proxmox before importing. The wizard cannot create bridges for you.
• Post-Import Adjustment: After the import, go to the VM’s Hardware tab in Proxmox. Verify the network interfaces. If the order is wrong, drag them to the correct position. If the type is wrong (e.g., it was set to “Bridged” but you need “Routed”), change it. Save the configuration.

Do not assume the network configuration is correct until you have verified it in the Proxmox GUI. A misconfigured bridge will result in a VM that boots but has no network connectivity. This is a common post-import issue.

Post-Import Verification and Boot Checks

Once the import wizard completes, the VM will be in a “Stopped” state. Do not start it immediately. Perform the following checks:

1. Verify Hardware Configuration: Check the CPU, RAM, and disk sizes. Compare them to the source VM’s configuration on ESXi. The wizard should have copied these accurately, but verify. If the CPU type is wrong, change it to host or a compatible model in the VM’s Options tab.
2. Check Disk Health: If you are using ZFS or Ceph, run a scrub or health check on the target storage. The import process writes a large amount of data. Ensure no I/O errors were logged.
3. First Boot: Start the VM. Monitor the console output. If the VM fails to boot, check the BIOS/UEFI settings. VMware VMs often use UEFI, while Proxmox defaults to SeaBIOS. If the source VM was UEFI-booted, you must enable UEFI in the Proxmox VM configuration. Go to Options → BIOS and select OVMF (UEFI). Save and restart the VM.
4. Network Verification: Once the OS has booted, verify network connectivity. Ping the gateway. If it fails, check the network interfaces inside the VM. The OS may have cached the old network configuration. You may need to re-run dhclient or update the network configuration files.

The import wizard is a powerful tool for migrating VMware ESXi workloads, but it is not a magic bullet. It handles the disk conversion and basic configuration, but you are responsible for ensuring the target environment is ready and for verifying the result. Test the migrated VM thoroughly before decommissioning the source VM on ESXi. Keep the source VM running for at least one full business cycle to ensure no hidden dependencies or configurations have been missed.

For more details on the import wizard and community experiences, refer to the [Proxmox forum thread](https://forum.proxmox.com/threads/new-import-wizard-available-for-migrating-vmware-esxi-based-virtual-machines.144023/). This article does not cover advanced vSphere networking or migrating to other hypervisors directly without Proxmox. If you need to migrate to KVM directly, consult the KVM documentation. If you need to build a new ESXi cluster, that is a separate topic.