Moving from VMware to Proxmox VE

Proxmox VE runs virtual machines and containers on standard servers. inett plans the migration from VMware ESXi, builds the cluster and supports it in production.

Proxmox VE 9.2 web interface showing a five-node cluster in the datacenter view with the Cluster Resource Scheduling dialog set to Dynamic Load
Screenshot: Proxmox Server Solutions GmbH

The problem with staying on VMware

Since the Broadcom acquisition, VMware is sold as a subscription and several product bundles have gone. Many organisations now pay considerably more for the same hosts. Some can no longer buy the edition they used before. When the renewal date comes, you need a way out that keeps production running.

Comparisons of Proxmox VE and VMware are easy to find. A migration plan for your own environment is not. Which VMs move first? What happens to the backup software, the storage and the Windows guests? Who handles the cut-over at night?

What inett does

Proxmox VE is a virtualisation platform built on Debian. It runs virtual machines with KVM/QEMU and Linux containers with LXC. You manage it through a web interface, a REST API or the command line.

inett is a Proxmox Gold Partner. We work through the migration with your team:

  1. Inventory. We record your VMs, datastores, networks and dependencies. You then know which systems can move as they are.
  2. Design. We size the hardware, the number of nodes, the network separation and the storage. If you need shared storage without a SAN, we include Ceph in the design.
  3. Build. We install the nodes and configure the cluster, high availability, the firewall and user permissions.
  4. Migration. Proxmox VE includes an import wizard that reads VMs directly from an ESXi host or through vCenter. We test it on non-critical VMs first, then agree maintenance windows with you for the rest.
  5. Operation. After the project, our managed services can take over updates, monitoring and troubleshooting.

We estimate the migration effort after the assessment. On that basis, a fixed price is also possible.

The import wizard has limits worth knowing before you plan. The source VM must be powered off during the import. vTPM state is not transferred. Encrypted disks and VMs on vSAN cannot be imported. Importing through vCenter is much slower than connecting to the ESXi host directly. Windows guests need VirtIO drivers to perform well after the move. Proxmox still labels the wizard a technology preview, so we check every VM before it moves.

Technical details

Current release
Proxmox VE 9.2, released 21 May 2026 (as of October 2026)
Base system
Debian 13 “Trixie”, Linux kernel 7.0, QEMU 11.0
Virtualisation
KVM/QEMU for Linux, Windows and BSD guests; LXC for Linux containers
Cluster
Corosync for quorum and configuration; nodes also need SSH (TCP port 22) between them. Proxmox recommends a dedicated network interface for cluster traffic
High availability
at least three nodes for reliable quorum, or two nodes plus a QDevice as third vote
Storage
local LVM or ZFS, Ceph (RBD and CephFS), NFS, SMB/CIFS, iSCSI and others
ESXi import
import wizard since Proxmox VE 8.2, still a technology preview; tested with ESXi 6.5 to 8.0 (Proxmox wiki)
Licence
GNU AGPLv3, no licence fees
Subscription
optional, per occupied CPU socket; gives access to the enterprise repository and, depending on level, support tickets with Proxmox (overview)

What is included

  • Review of your VMware environment and a migration plan per VM
  • Hardware and network design for the cluster
  • Installation and configuration of the Proxmox VE nodes
  • Cluster, high availability, firewall and permission set-up
  • Storage integration and backup with Proxmox Backup Server
  • Pilot migration, then migration of the remaining VMs
  • Documentation and handover to your team
  • Introduction for your administrators; in-depth training on request

Who it is for

Proxmox VE suits organisations that run their own servers and want lower or more predictable virtualisation costs. That covers a small business with three hosts as well as a public body that wants less dependence on a single vendor. Linux skills in the team help, because Proxmox VE is Debian underneath.

It is a poor fit if you rely heavily on VMware add-ons such as NSX or Horizon. The same applies if the vendor of a business application only supports VMware. In that case we first check whether a move is possible at all.

Frequently asked questions

Do I need a Proxmox subscription?

No. Proxmox VE has the full feature set without one. A subscription gives access to the enterprise repository, which Proxmox recommends for production, and depending on the level, support from Proxmox itself.

How many servers do I need?

One server is enough to start. High availability needs three nodes, or two nodes plus a QDevice. With Ceph as shared storage, three nodes are the minimum.

Can I reuse my current VMware hosts?

Often, yes. On x86 servers Proxmox VE needs a 64-bit CPU with Intel VT or AMD-V. We check during the inventory whether your RAID controller suits ZFS or Ceph.

You can buy Proxmox VE subscriptions in the inett shop.