Migrating from VMware ESXi to Proxmox VE: When the Switch Makes Sense and How to Do It Without Downtime
The r/sysadmin discussion about moving from ESXi to Proxmox drew hundreds of comments for a reason. After Broadcom overhauled VMware's licensing policy, subscription costs for small installations rose to the point where continuing to pay stopped making economic sense for companies with 2–5 servers. Ukrainian small and mid-sized businesses — often running on grant-funded or self-owned hardware with no reserve budget for IT infrastructure — found themselves in a situation where a free Proxmox VE-based alternative looks less like an experiment and more like a necessity.
This article covers when the switch is genuinely justified, the pitfalls that await when migrating domain controllers and business applications, and how to build a rollback plan so you don't leave the company without infrastructure halfway through the process.
Context: Why ESXi Got More Expensive
After Broadcom acquired VMware, the licensing model shifted from perpetual licenses on individual products (vSphere Essentials, Essentials Plus) to bundled subscriptions aimed at large installations with minimum per-order core counts. For companies with one or two physical hosts, this means either a substantial per-unit cost increase or simply no suitable package at all. The Reddit discussion captures exactly this problem: small-business admins with a limited number of hosts no longer see the point in paying for functionality they only partly use.
Proxmox VE is a Debian Linux-based hypervisor using KVM for full virtualization and LXC for containers, with a web management interface and open source code. The current 2026 release line is Proxmox VE 9, version 9.2 (May 2026), based on Debian 13 "Trixie". The base version is free and fully featured: clustering, High Availability, live migration, and backup are all available without a subscription. Paid Proxmox subscriptions only cover access to the stable enterprise update repository and priority technical support — not the functionality itself.
What This Means for Ukrainian Business
For companies running an Active Directory domain controller, file server, 1C, or an internal CRM/ERP on 1–3 physical hosts under ESXi, moving to Proxmox lets them eliminate the annual licensing line item entirely. This is especially relevant for businesses that received server hardware through grant programs and have no budgeted funds for ongoing subscriptions, or for companies deliberately optimizing IT spend during wartime.
At the same time, it's worth honestly assessing the risks. Proxmox doesn't carry the same level of official certification from enterprise storage array vendors and certain corporate backup solutions as VMware does, and a team used to vCenter will spend time adapting to different networking and storage logic. For companies without in-house Linux expertise, this is an added factor — you need someone who understands Debian-based systems at least at a basic level.
Practical Migration Plan
1. Inventory and Preparation
Compile a full list of VMs on ESXi: domain controllers, file servers, business applications, and their dependencies (DNS, DHCP, license servers).
Document the current network topology: vSwitches, VLANs, port groups — you'll need to recreate them as Linux bridges on Proxmox.
Check guest OS versions and compatibility with KVM virtual hardware (especially older Windows Server editions).
2. Backup Before Migration
Make a full backup of each VM using your existing tool (Veeam Backup & Replication, if already in use) or export images as OVF/OVA via vCenter/ESXi.
Additionally, snapshot the domain controller configuration and verify backup integrity with a separate test restore — this is critical specifically for AD.
3. Installing Proxmox VE
Install Proxmox VE on separate test hardware or a spare host — not on top of production ESXi while migration is still in progress.
Configure network bridges (Linux bridge) matching your existing vSwitches and VLANs. The exact bridge and VLAN-aware bridge configuration depends on your network topology — verify against the official Proxmox documentation for your setup.
For storage, use local LVM-Thin, ZFS, or — if you have a SAN/NAS — configure the appropriate storage backend (NFS, iSCSI, Ceph). The choice depends on your available hardware.
4. Importing VMs from ESXi
Since Proxmox VE 8.2, a built-in ESXi Import Wizard is available, and in version 9.x it's the recommended first-choice method for most migrations. It connects directly to the ESXi host through the Proxmox web interface, lets you pick a VM from the list, and imports it without manual command-line VMDK copying.
In Proxmox: Datacenter → Storage → Add → ESXi. Enter the ESXi host's IP or hostname and credentials; for self-signed certificates, enable "Skip Certificate Verification".
The wizard connects directly to ESXi hosts. For vCenter-managed environments, connect to the specific host rather than to vCenter.
The VM on the ESXi side must be powered off and free of snapshots — imports with snapshots are significantly slower or fail outright.
Limitations: disks on VMware vSAN can't be imported directly (move them to other storage first), and encrypted disks require removing encryption before import.
Avoid "Live Import" for production systems — it's safer to let the data fully sync before first booting the VM.
Fallback method. If the wizard isn't available (older ESXi version, migration from VMware Workstation, a compatibility error), the classic OVF/OVA path still works. Export the VM as an OVF template, transfer the files to Proxmox, and use the qm importdisk utility to attach the converted disk to a new VM (VMDK-to-KVM conversion happens automatically). Verify the exact command flags for your Proxmox version against the current documentation.
5. Testing the Domain Controller in Isolation
Deploy the imported domain controller in an isolated VLAN or on a separate bridge with no access to the production network.
Verify AD DS and DNS services, replication (if you have a second DC), and test-client authentication.
Only after successful testing, move the DC into the production network — preferably during off-hours, within a short maintenance window.
6. Backup After the Switch
After migration, you have two main options for regular backups:
Proxmox Backup Server (PBS) — the native solution from the Proxmox developers, free and open source (AGPL-3.0), with deduplication and incremental backups. For a business moving specifically away from paid licenses, this is the most logical choice: no VM or socket limits. Basic VM backups can also be done with the built-in
vzdumputility.Veeam Backup & Replication natively supports Proxmox VE starting with Veeam Data Platform 12.2 (August 2024), with no separate plugins. It's licensed by the number of protected VMs: each consumes one Veeam Universal License (VUL). Note: only VUL is available for Proxmox — legacy socket licenses don't apply to this platform. This makes sense if you're already standardized on Veeam and want to keep a single backup stack.
7. Rollback Plan
Don't power off or delete the original ESXi VMs until the Proxmox versions have run in production for at least several days to a week.
Keep a separate, current backup copy until you fully trust the new environment.
Document a step-by-step return-to-ESXi scenario in case of a critical problem — who shuts down and powers on what, and in what order.
FAQ
Can you migrate from ESXi to Proxmox without downtime?
Completely without downtime is difficult, especially for a single domain controller. But for most business applications, you can reduce the maintenance window to a few hours during off-hours thanks to prior isolated testing and the built-in Import Wizard.
Does Proxmox support clustering and High Availability for free?
Yes. Clustering, HA, live migration, and backup are all available in the free version of Proxmox VE with no subscription required. A paid subscription only covers access to the stable enterprise update repository and priority support — not the functionality itself.
What about Veeam backups after the switch?
Veeam natively supports Proxmox VE from Veeam Data Platform 12.2 onward, licensed by the number of protected VMs (Veeam Universal License). The no-extra-license alternative is the native Proxmox Backup Server. Confirm the exact terms for your specific Veeam version with your supplier.
Is it worth switching if the company has only one server?
If it's a single physical host with no need for vMotion or clustering, the economic benefit of dropping VMware licenses usually justifies the time spent on migration and team training.
Sources
r/sysadmin discussion: Switching from ESXi to Proxmox
Official Proxmox VE documentation — Migrate to Proxmox VE (pve.proxmox.com/wiki/Migrate_to_Proxmox_VE)
Official Proxmox VE pricing page (proxmox.com/products/proxmox-virtual-environment/pricing)
Veeam — Proxmox VE Backup & Recovery (veeam.com)