Import VMs from VMware ESXi into Proxmox VE

Many teams are moving from VMware to Proxmox. Recent Proxmox VE versions include an ESXi import wizard, and for older versions or exported files you can import VMDK disks by hand. Either way, plan driver and network changes inside the guest.

Before you start

• Proxmox VE 8.2 or newer for the import wizard (check with pveversion).
• Network access from Proxmox to the ESXi host or vCenter, and an account with read access.
• A backup of each VM, and a list of its IPs and services.
• For Windows: the VirtIO driver ISO in Proxmox (VirtIO for Windows).

Method 1: the ESXi import wizard

1. Datacenter → Storage → Add → ESXi: enter the host, username and password. Tick skip certificate verification only for self-signed certificates you trust.
2. Select the new ESXi storage in the tree; it lists the VMs.
3. Shut down the source VM in VMware (importing a running VM gives an inconsistent disk).
4. Select the VM and click Import. Choose the target storage, bridge and, under Advanced, disk bus and network model.
5. Start the import and follow the task log.

Method 2: import a VMDK manually

1. Export or copy the VM's .vmdk files to the Proxmox node.
2. Create an empty VM with matching CPU, RAM and network, but no disk.
3. Import the disk (it is converted automatically):

qm importdisk 130 /root/import/web01.vmdk local-lvm

4. In Hardware, the disk appears as Unused. Double-click it, attach it (SATA first for Windows) and set it as the first boot device in Options → Boot Order.

More on formats: convert VMDK and VHDX to qcow2.

Fix drivers and networking

• Linux: usually boots on VirtIO directly. The network interface name changes (for example from ens192 to ens18), so update Netplan or interface configs from the console.
• Windows: boot first with SATA disk and E1000 NIC, install the VirtIO drivers, then switch the disk to SCSI/VirtIO and the NIC to VirtIO for full speed.
• Set the IP address again if the guest treats the new NIC as a new adapter.

Troubleshooting

• Windows blue screen INACCESSIBLE_BOOT_DEVICE: the disk is on VirtIO before the driver is installed; switch to SATA, boot, install drivers.
• UEFI VM does not boot: set BIOS to OVMF (UEFI) and add an EFI disk.
• No network: fix the interface name in the guest's network config.

Frequently asked questions

Can I import from vCenter?

The wizard can connect to vCenter, but connecting directly to ESXi hosts is often faster.

Is downtime needed?

Yes, shut down each VM for a consistent import, then start it on Proxmox.

Do snapshots carry over?

No. Remove VMware snapshots before importing.

Next steps

• ESXi vs Proxmox vs Hyper-V
• VirtIO drivers explained
• Create a Proxmox VM