Toil-Less

Guide · VMware → Proxmox VE

VMware to Proxmox VE: what to check before you migrate

Moving from vSphere to Proxmox VE is mostly straightforward. Most VMs import cleanly and boot on the first try. The trouble comes from the few that don't, and you usually find them on migration night. This checklist covers what to look at before you move anything: what blocks a VM outright, what needs preparation, and what you will have to rebuild around the VMs.


1. Start with an inventory

Before you plan any migration windows, know what you are actually moving:

  • How many VMs, and which of them are VMware's own infrastructure (vCenter, vCLS, other appliances). Those are retired together with vSphere, not migrated.
  • Used storage, not provisioned storage. Copy time depends on the data that actually exists. A thin-provisioned 2 TB disk holding 300 GB copies as 300 GB with most tools.
  • Guest operating systems and their support status. A VM running an operating system that is already out of vendor support is a candidate for replacement, not for migration. Moving it only moves the problem.
  • What you will need on the target: total vCPUs, RAM and storage, plus some headroom.

2. Blockers: VMs that need their own plan

These VMs will not simply import. Find them first, because each one needs a decision.

Blocker Why it matters
Physical-mode RDMs The guest talks to a LUN directly. There is no virtual disk to import, and image-based backups don't include it either. You need to re-present the storage or copy the data at file level.
Shared multi-writer disks Typical of guest clusters (for example Windows failover clusters or Oracle RAC). The shared storage design has to be rebuilt for the target.
PCI or GPU passthrough Passthrough works on Proxmox too, but it is tied to the physical host and its hardware. Plan the target host first.
vSphere VM Encryption Encrypted VMs must be decrypted in vSphere before their disks can be read by any import tool.
Fault Tolerance Proxmox VE has no lock-step equivalent. Proxmox HA restarts a VM on another node after a failure, which means a short outage. Decide whether that is acceptable or the application needs its own redundancy.

3. Preparation: fix these before migration night

None of these stop a migration, but each one causes trouble if you forget it.

  • Snapshots. Consolidate or delete them first. Old snapshots also tend to be much larger than anyone remembers, which ruins your copy-time estimate.
  • Independent disks. They are excluded from snapshots, so snapshot-based tools and backups skip them. Check where their data is supposed to go.
  • vTPM. The contents of the virtual TPM do not migrate. If the guest uses BitLocker, have the recovery keys ready, or suspend BitLocker before the move.
  • USB devices, typically licence dongles. USB passthrough works on Proxmox, but it is bound to one host. A network USB server is often the more robust choice.
  • Mounted ISO images. Disconnect them. The datastore path won't exist on the target.
  • Serial and parallel ports. Find out what is attached and whether it is still needed.
  • Memory limits below the configured RAM. Usually an old misconfiguration. Don't carry it over.
  • VMware Tools not installed or not running. Without Tools you have no reliable hostname, IP address or exact OS version for that VM, so check it by hand.

4. Windows guests

Windows needs the most care, because it only boots from storage controllers it has drivers for.

  1. Install the VirtIO drivers before the move. The virtio-win package contains the storage (vioscsi/viostor) and network (NetKVM) drivers plus the QEMU guest agent. If you skip this, the VM may fail to boot on a VirtIO SCSI controller. The workaround is to boot it once with a SATA disk, install the drivers and then switch, but doing it beforehand is much easier.
  2. Document static IP settings. The new virtual NIC is a new adapter for Windows. The old configuration stays attached to the old, now hidden adapter, so the VM comes up without its IP address.
  3. Uninstall VMware Tools before migrating. Removing it afterwards, on a host that is no longer VMware, is often difficult.
  4. Expect re-activation for some Windows and application licences that are bound to hardware IDs.

5. Linux guests

Linux usually migrates with fewer surprises:

  • Most current distributions include the VirtIO drivers in the initramfs. Older or minimal installations may not, so check before the move.
  • Network interface names change (for example from ens192 to ens18). Static configurations in netplan, ifcfg files or /etc/network/interfaces then point at an interface that no longer exists. Plan to fix this on first boot, or use console access.
  • Replace open-vm-tools with qemu-guest-agent after the move.

6. Firmware: BIOS or UEFI

Match the firmware on the target, or the VM won't boot:

  • BIOS VMs use SeaBIOS on Proxmox.
  • UEFI VMs use OVMF and need an EFI disk. If Secure Boot is enabled on the source, decide whether you keep it and with which keys.

7. Networks you have to rebuild

Every port group your VMs use needs an equivalent on Proxmox, usually a VLAN-aware Linux bridge or an SDN VNet. Before you build them, list:

  • every port group that is actually in use, its VLAN ID, and which VMs depend on it
  • port groups with different VLAN IDs on different hosts. This happens more often than expected in standard-switch environments, and it means a VM's network depends on which host it runs on. Clear it up before you rebuild it.

8. Placement rules you have to rebuild

DRS rules don't come along. Write them down before you shut vCenter off:

  • Keep together and keep apart rules (for example two domain controllers that must never run on the same host)
  • VM-to-host rules (for example licensing tied to specific hosts)

Proxmox VE 9 has HA rules for this: node affinity rules for VM-to-host placement and resource affinity rules for keeping VMs together or apart. Earlier versions use HA groups. Either way, the rules have to be created again by hand.

9. Backups

If you use Veeam, check two things:

  • Independent disks are not included in Veeam's image-based VMware backups. If you plan a backup-and-restore migration, those disks need separate handling.
  • VMware Tools status matters for application-aware processing. Outdated or missing Tools can make those jobs fail.

Current Veeam versions can back up Proxmox VE and restore backups to it. That makes a restore from your existing VMware backups a possible migration path, and gives you a fallback copy of every VM at the same time.

10. Estimate copy time realistically

A simple rule of thumb: used storage divided by about 70% of your link speed. Real transfers rarely reach the full line rate.

Used storage 1 Gbit/s 10 Gbit/s
500 GB about 1.6 hours about 10 minutes
2 TB about 6.3 hours about 38 minutes
10 TB about 32 hours about 3.2 hours

This is pure transfer time. Testing, cut-over and downtime come on top. Disks larger than 2 TB deserve their own migration window.

11. Choose the migration path

  • Proxmox import wizard (Proxmox VE 8.2 and later). Add your ESXi host as a storage of type ESXi, then import VMs from the web interface. It is the simplest route for most VMs.
  • Backup and restore with Veeam or another tool that supports both platforms.
  • Manual export (OVF/VMDK) and conversion with qemu-img, for edge cases.

Whatever you use, migrate a few unimportant VMs first and test them properly before you move anything that matters.


The short version

Before migrating, know for every VM:

  • ☐ Does it have a blocker: physical RDM, shared disk, passthrough, encryption or Fault Tolerance?
  • ☐ Are snapshots consolidated and ISOs disconnected?
  • ☐ Windows: VirtIO drivers installed, IP settings documented, VMware Tools removed?
  • ☐ Linux: VirtIO drivers present, network interface names handled?
  • ☐ BIOS or UEFI, and is Secure Boot or vTPM in use?
  • ☐ Which networks and VLANs does it need, and which placement rules apply?
  • ☐ Is the operating system still supported?
  • ☐ How much used storage does it have, and how long will it take to copy?

Check all of this automatically

The VMware Exit Readiness Report reads your vCenter and runs these checks for every VM: blockers, preparation items, OS support, networks, DRS rules and copy time. It produces one HTML report with a summary for your manager. Read-only, plain PowerShell, one-time price.

See the report → View an example report