VMware to Proxmox Migration: The 2026 Playbook

As of October 2026, the documented route for a VMware to Proxmox migration is the import wizard built into Proxmox VE, added in version 8.2 (April 2024), which pulls VMs straight from an ESXi host with most settings mapped; OVF import and qm disk import are the manual fallbacks. Its documented limits: testing covers ESXi 6.5 through 8.0, vSAN-backed and encrypted disks can’t be imported directly, and Windows guests need VirtIO drivers for Proxmox’s recommended disk and network devices.

For other exit routes, see the VMware alternatives shortlist.

In this guide

Key facts
Step 1: Assess what you have
Step 2: Design the Proxmox target
Step 3: Migrate with the import wizard
Manual fallbacks: OVF and disk import
Windows guests: VirtIO drivers before cutover
Linux guests
Networking mapping
Testing, cutover and rollback
Support options
Migration checklist
Bottom line
Frequently asked questions
Sources

Key facts

Item	What the official docs say
Import wizard	Since Proxmox VE 8.2 (April 24, 2024); still a technology preview
Current Proxmox VE	9.2 (May 21, 2026); version 8 reached end of life in August 2026
ESXi versions tested	6.5 through 8.0
Not importable as is	vSAN-backed disks, encrypted disks, vTPM state
Slower imports	VMs with snapshots; importing through vCenter (5 to 10 times slower)
Parallel imports	Advised maximum of four VM disks at once
Support	EUR 120 to 1,100 per CPU socket per year, plus VAT where applicable

Step 1: Assess what you have

Inventory every VM against the factors the Migrate to Proxmox VE wiki covers: guest OS, BIOS or UEFI boot, each disk’s datastore (flag vSAN), encryption, vTPM, snapshots, VLANs, static IPs and MAC-based DHCP reservations.

What doesn’t move 1:1

vSAN: disks must move to another datastore first, for example with Storage vMotion.
NSX: the Proxmox migration docs describe no NSX import, so rebuild segments and rules with Proxmox SDN and the Proxmox VE firewall.
DRS-style balancing: Proxmox VE 9.2 added dynamic load balancing for HA-managed guests. It requires the static-load or dynamic-load scheduler mode; the default mode is basic.
Fault tolerance: the wiki says Proxmox VE offers no lockstep fault tolerance (as of 2025).
VMware Tools: remove it before migrating, since it might be hard to remove afterward.
vTPM: its state currently can’t be migrated; consider disabling encryption keyed to it, and keep the recovery keys.

Support timeline

vSphere 7 general support ended October 2, 2025, and VMware says vSphere 8 is supported until October 2027, with an optional, paid two-year Extended Support period. See VMware licensing changes in 2026, the vSphere 8 end-of-support guide and the Broadcom renewal negotiation playbook.

Step 2: Design the Proxmox target

Build on Proxmox VE 9: version 9.2 shipped May 21, 2026, and version 8 reached end of life in August 2026. Settle clustering before the first import; Proxmox recommends at least three nodes for stable quorum.

The storage documentation lists these common choices:

Storage	Shared	Snapshots	Note
ZFS (local)	No	Yes	Replication is asynchronous
Ceph RBD	Yes	Yes	Hyper-converged setups need at least three servers
NFS or CIFS	Yes	With qcow2	qcow2 snapshots can be slow
LVM on an iSCSI or FC LUN	Yes	Technology preview	Reuses an existing SAN

Proxmox generally recommends Ceph for shared storage. On an existing SAN, LVM snapshots need the “Snapshots as Volume-Chain” option, a technology preview since Proxmox VE 9.0, or a storage-vendor plugin that supports them.

The wiki’s VM best practices: CPU type host on identical CPUs (otherwise a generic x86-64-v<X> model), VirtIO SCSI single with Discard and IO thread, VirtIO NICs, the ballooning device and the guest agent.

Step 3: Migrate with the import wizard

Proxmox announced the wizard on March 27, 2024 and made it a headline feature of Proxmox VE 8.2 on April 24, 2024. The admin guide still calls it a technology preview under active development.

Step by step, as documented

Run Proxmox VE 8 or later with the latest updates applied.
Add an ESXi import source under Datacenter > Storage > Add, using an admin account. For a self-signed certificate, trust its CA or tick Skip Certificate Verification. Connect to the ESXi host rather than vCenter, which is 5 to 10 times slower.
Select the new storage and confirm every VM appears.
Select a VM, click Import, and pick at least the target storage and network bridge; the Advanced tab handles per-disk storage, NIC settings and skipped devices.
Optionally review the Resulting Config tab.
Prepare the guest, then power off the source VM so its state is consistent.
Start the import, boot the VM and make the post-migration changes.

Live import boots the VM while the remaining data copies in the background, which reduces downtime. If the import fails, everything written since it started is lost, so Proxmox advises testing it first and avoiding low-bandwidth or error-prone networks.

Documented limitations

vSAN-backed disks don’t import, and encrypted disks need their encryption policy removed first.
Datastore names with special characters such as “+” might fail; rename the datastore.
VMs with snapshots import significantly slower.
The ESXi API blocks clients for roughly 30 seconds once its connection limit is hit, and each disk takes a read-ahead cache of 8 blocks of 128 MiB, so the wiki advises at most four VM disks at once.

Manual fallbacks: OVF and disk import

Each manual route in the wiki starts from a powered-down source VM.

OVF export and import

Export with Export OVF Template in the vSphere Client, which can’t export encrypted VMs, or with Broadcom’s OVF Tool, whose 9.1.1 build is backward compatible with earlier vSphere releases. The wiki’s export command for an ESXi host:

./ovftool vi://root@{IP or FQDN of ESXi host}/{VM name} /path/to/export/location

Then import from the export folder:

qm importovf {vmid} {VM name}.ovf {target storage}

qm importovf 100 Server.ovf local-zfs

Add a network card, which the import doesn’t create, then apply the best practices, for example:

qm set {vmid} --cpu x86-64-v2-AES --scsihw virtio-scsi-single

Since Proxmox VE 8.3, the web interface can also import OVF and OVA files from file-based storage.

Disk import

qm disk import, also available under the alias qm importdisk, converts a VMware disk into an existing VM. Proxmox VE needs both the .vmdk and -flat.vmdk files, most easily on a network share both sides can reach. Create the VM, remove its default disk, then run:

qm disk import {target VMID} {vmdk file} {target storage}

qm disk import 104 Server.vmdk local-zfs

Attach the resulting unused disk to a bus (IDE or SATA for Windows) and set the boot order. For large disks, the wiki also documents booting directly from the VMware -flat.vmdk on a share and moving the disk while the VM runs; the VM must never run on both platforms at once.

Windows guests: VirtIO drivers before cutover

Windows has no built-in VirtIO drivers; they come from the virtio-win project. Proxmox’s Windows VirtIO Drivers page lists no known issues with 0.1.271 and documents reported read errors with 0.1.285 on IO-heavy Windows Server 2025 VMs.

On VMware, record network settings and consider removing static IPs and disabling vTPM-based encryption such as BitLocker.
Install the drivers with virtio-win-gt-x64 from the ISO, or the downloadable MSI; the virtio-win-guest-tools wizard adds the QEMU guest agent.
Uninstall VMware Tools last, from the console. Broadcom notes this removes the VMXNET3 driver and, without an earlier one, the network configuration.
Import, booting from IDE or SATA if needed.
Move the boot disk to VirtIO SCSI with the dummy-disk method: add a 1 GB SCSI disk, let Windows load its driver, shut down, remove it, then reattach the boot disk as SCSI and check the boot order. Skipping the dummy disk causes an “INACCESSIBLE BOOT DEVICE” blue screen.
Set the NIC model to VirtIO and enable the guest agent option.

Linux guests

Linux has had VirtIO support since kernel 2.6.x, but the drivers may be modules missing from the initramfs. Check before cutover:

grep VIRTIO /boot/config-$(uname -r)

m means the module has to be in the initramfs. On dracut systems such as RHEL, add any that are missing:

dracut -f /boot/initramfs-$(uname -r).img $(uname -r) --add-drivers "virtio virtio_pci virtio_blk virtio_net virtio_ring virtio_scsi"

On initramfs-tools systems such as Debian, list the modules in /etc/initramfs-tools/modules, then run:

update-initramfs -u -k $(uname -r)

Remove VMware guest tools first, and expect a new network interface name afterward. Install the QEMU guest agent and enable it with qm set VMID --agent 1. Use SeaBIOS for legacy BIOS guests and OVMF for UEFI.

Networking mapping

Proxmox VE’s virtual switches are Linux bridges named vmbrX. The network documentation and wiki map the rest:

VMware	Closest Proxmox VE construct
Port group with a VLAN ID	VLAN tag on the VM’s NIC, on a VLAN-aware bridge
NIC teaming	A bond used as the bridge port
The same VLANs on every host	SDN VLAN zone
NSX segments	SDN VXLAN or EVPN zones, rebuilt by hand
NSX firewall rules	Proxmox VE firewall rules, security groups and IP sets
VMXNET3 adapter	VirtIO (a vmxnet3 model is offered for imported VMs)

Proxmox VE generates a random MAC for each NIC it creates, so adapt DHCP reservations or set the MAC manually, as the wiki advises.

Testing, cutover and rollback

The wiki “highly” recommends test migrations before production. A pilot passes when the VM boots, its network is correct, qm agent <vmid> ping returns without an error, and the application owner signs off.

At cutover: remove VMware Tools, power off the source, import no more than four disks at a time, then rerun the pilot checks.

The documented methods power the source VM off rather than delete it. To roll back, shut down the Proxmox VM, start the VMware VM and reinstall VMware Tools (re-entering network settings on Windows). Writes made on Proxmox after an import won’t exist on the source, so set a rollback deadline. Never run both copies at once.

Support options

Proxmox VE is free under the GNU AGPLv3, with every feature included. As of October 2026, subscriptions per occupied CPU socket per year, net of VAT on a one-year term, are:

Community, EUR 120: Enterprise Repository, no tickets; positioned for non-production use.
Basic, EUR 370: 3 tickets a year, 1 business day response.
Standard, EUR 550: 10 tickets a year, 4-hour response; 24/7 coverage by the end of 2026.
Premium, EUR 1,100: unlimited tickets, 2-hour response, 24/7 from October 19, 2026.

Response times are guaranteed first responses to Severity 1 tickets during coverage hours, and all nodes in a cluster need the same level. Compare costs in the Proxmox vs VMware analysis. For implementation help, Proxmox lists reseller and training partners in its partner ecosystem; the Proxmox enterprise-readiness scorecard covers operations.

Migration checklist

Phase	Task	Done when
Assess	Inventory VMs; flag vSAN, encryption, vTPM, Fault Tolerance	Each VM has a method
Design	Proxmox VE 9, storage, bridges, VLANs, SDN zones	Every network has a target
Design	Subscription level or partner	Support live before cutover
Pilot	Migrate test VMs	Pilot checks pass
Prepare	VirtIO drivers (Windows), initramfs (Linux), network settings recorded	Confirmed before cutover day
Cutover	Remove VMware Tools, power off, import up to four disks at once	Imports complete
Cutover	Windows boot disk to VirtIO SCSI; guest agent on	Agent ping succeeds
Close	Keep source VMs off until the rollback deadline	Decommissioned on schedule

Bottom line

Use the wizard, connected to ESXi hosts directly, for VMs on ESXi 6.5 to 8.0, after moving vSAN disks and removing encryption.
Budget time to rebuild NSX networking and firewall policy by hand.
For other targets, compare XCP-ng vs Proxmox and OpenShift Virtualization and the alternatives.

Frequently asked questions

Can Proxmox import VMs directly from VMware ESXi?

Yes. Since Proxmox VE 8.2 (April 2024), the import wizard connects to an ESXi host and imports VMs with most settings mapped. Proxmox has tested it with ESXi 6.5 through 8.0.

Does the Proxmox import wizard work with vSAN?

Not directly. VMs with disks on vSAN can’t be imported. Move the disks to another datastore first, for example with Storage vMotion.

Do Windows VMs need VirtIO drivers on Proxmox?

Only IDE and SATA disks work in Windows out of the box. Proxmox’s recommended VirtIO devices need the virtio-win drivers, so install them before cutover.

How long does a VMware to Proxmox migration take?

Proxmox doesn’t publish a duration. Its docs say snapshots, importing through vCenter and too many parallel imports slow it down, while live import reduces downtime.

Do you need a Proxmox subscription for production?

No license is required. Ticket support starts with Basic at EUR 370 per socket per year.

Sources

Last checked: October 2026. Prices and plans change; check the vendor’s page before you buy.

Buying? Start from RFPhub’s free Virtualization Platform RFP template.