Since VMware moved to subscription-based sales, many small and mid-sized companies have looked for alternatives, and Proxmox VE is one of the main options. Migration is feasible and, in most cases, can be done without long downtime. But if you start without a plan, you usually end up working late into the night with a VM that won’t boot or a server that has lost its IP address.
Step 1: Inventory and prioritization
Before anything else, record the following for each virtual machine:
- Operating system and version, CPU count, memory and disks
- Firmware type (BIOS or UEFI); the destination VM must use the same
- Network settings, static IP and VLAN
- Dependencies: which service depends on which server
- Licenses that may be tied to hardware or a MAC address
- Acceptable downtime for each service
Then set the migration order: low-priority and test VMs first, and critical servers such as finance and databases last.
Step 2: Prepare the Proxmox platform
Fully set up the Proxmox host or cluster: storage, networking and bridges with the same VLANs you use today, and most importantly, backup. Before moving the first VM, make sure backups work in the new environment, with Proxmox Backup Server or a backup product whose version supports Proxmox.
Step 3: Prepare the VMs
- VirtIO drivers for Windows: The best disk and network performance in Proxmox comes from VirtIO drivers. A Windows VM without these drivers may fail to boot with a VirtIO controller. Either install the drivers before migrating, or first bring the VM up with a more compatible disk controller (such as SATA), install the driver and then switch the controller.
- Snapshots: Delete or consolidate the VM’s snapshots before migrating.
- VMware Tools: It serves no purpose in the new environment and should be removed; install QEMU Guest Agent instead.
- A fresh backup: Before migrating each VM, make sure you have a good backup of it.
Step 4: Choose a migration method
Depending on your Proxmox version and situation, there are several common methods:
- Built-in import tool: Recent Proxmox versions can connect to ESXi and import VMs directly. Check its availability and limitations in the documentation for your version.
- OVF export or disk file: Export the VM from VMware and use the
qmcommand-line tool to import the disk into a new VM. - Restore from backup: Some backup products can restore a VM backed up in VMware directly onto Proxmox; check whether your software version supports this.
Whichever method you choose, test it first on a test VM and measure how long it takes.
Don’t delete the original VM for a few days after migration. Keep it powered off so you can roll back quickly if a problem appears; just make sure both copies are never running at the same time.
Step 5: After the first boot
- The new network adapter is usually detected as a new device, so static IP settings must be entered again.
- Test services, user access and connectivity with other servers.
- Check Windows activation and the licenses of any software sensitive to hardware changes.
- Add the VM to a backup job and complete a successful backup.
Checklist
- An inventory of VMs with firmware, network and dependencies has been prepared.
- Backups in the Proxmox environment were tested before migration.
- Installation of VirtIO drivers and QEMU Guest Agent has been planned.
- The migration method has been tested on a test VM.
- Original VMs are kept until the end of the validation period.
- Downtime for each critical service has been coordinated with users.
A successful migration depends more on planning than on tools. ITPlus724 engineers can prepare your Proxmox platform and migrate your VMs step by step with minimal downtime.