Migrating from VMware to Proxmox: step-by-step guide and costs

Migrating from VMware to Proxmox is today the most direct way to stop depending on Broadcom’s new licensing without changing the way you work. In this guide we explain what has changed at VMware, how much Proxmox VE costs, how to prepare each machine, which migration method to choose and what to do with storage and clustering. At Binovo we have been a Proxmox partner since 2013, and we migrate and maintain environments for companies in Gipuzkoa, the Basque Country and the rest of Spain.

Information reviewed and expanded on 23 October 2026.

Migration from VMware to Proxmox VE

Why so many companies are leaving VMware

Since Broadcom bought VMware, the licensing model has changed completely. These are the changes that affect an SME the most:

  • Subscription only: since 11 December 2023, perpetual licences are no longer sold and their support is no longer renewed.
  • Per-core licensing: you pay per physical CPU core, with a minimum of 16 cores per processor. A server with an 8-core processor pays for 16.
  • Minimum order of 72 cores: several distributors have applied it since April 2025, although it does not appear in Broadcom’s public documentation. If you are renewing, ask for the figure in writing.
  • A reduced catalogue of a few bundles, with VMware Cloud Foundation (VCF) as the main product.

According to the summary published by cloudmagazin, average increases are around 60% compared with the previous model, with cases of 8 to 15 times the previous cost. For a company with two or three servers, the jump is usually hard to justify.

What’s new in autumn 2026

  • vSphere 7 no longer has general support since 2 October 2025, and vSphere 8 has it until October 2027. Anyone still on version 7 is outside general support and, if they renew, will probably have to upgrade at the same time.
  • Azure stops including VMware licences: since 31 October 2026, Microsoft no longer sells new Azure VMware Solution environments with licences included. You will have to buy VCF from Broadcom, and existing customers have until 30 August 2027 to make the switch. Moving to the cloud is no longer a way around the licence.
  • Broadcom has withdrawn the public download of VDDK, the library many third-party migration tools rely on. The Proxmox import wizard does not need it; we cover this in Proxmox launches 24/7 support (in Spanish).

What Proxmox VE is and what it offers compared with VMware

Proxmox Virtual Environment is an open-source virtualization platform based on Debian, KVM and LXC containers. The current version is 9.2, released in May 2026. It is managed from a web interface and covers what an SME uses every day in VMware:

Need In VMware In Proxmox VE
Virtual machines ESXi KVM, included
Centralized management and clustering vCenter Web interface on every node and multi-master cluster, included
Moving machines while running vMotion Live migration between nodes and between storage
High availability vSphere HA HA included in the cluster
Distributed storage vSAN Ceph, included
Virtual networking vSwitch, NSX Linux bridges (vmbr), bonds, VLANs and SDN
Backups Third-party products Proxmox Backup Server, free with optional support
Licence Per-core subscription Free software (AGPLv3); the subscription is optional and paid per processor

How much Proxmox VE costs

The software is free. The subscription gives access to the more thoroughly tested enterprise repository and to official support. It is paid per occupied physical processor per year, and in a cluster all nodes must have the same level. Net prices published by Proxmox in October 2026:

Plan Price per processor per year Support
Community €120 Enterprise repository, no tickets
Basic €370 3 tickets per year, response within 1 business day
Standard €550 10 tickets per year, response within 4 hours
Premium €1,100 Unlimited tickets, response within 2 hours, 24/7

A server with two processors on the Basic plan costs €740 per year, with no minimum number of cores. Since 19 October 2026, Proxmox also offers 24/7 support on the Premium plan.

How to migrate from VMware to Proxmox, step by step

  1. Inventory. List the virtual machines, their operating system, disks, networks and dependencies. Mark which ones are critical and when your VMware contract expires: it is best to finish before that date.
  2. Designing the Proxmox environment. Decide whether to reuse the current hardware or replace it, the storage (local, SAN array, NAS or Ceph) and whether you need a cluster with high availability.
  3. Backups and a rollback plan. Before moving anything, take a full backup and have a plan to go back to VMware if something fails. The original machine is shut down, but not deleted until the new one has been validated.
  4. Preparing each machine. Drivers, network, boot and encryption; see the checklist below for details.
  5. Pilot test. A non-critical machine is migrated first to check performance, drivers and networking.
  6. Import. Using the method that best suits each machine (see the table).
  7. Post-migration adjustments. The Proxmox agent (QEMU guest agent) and the VirtIO drivers are installed, IP addresses are checked and the applications are tested.
  8. Backups and monitoring. Proxmox Backup Server and monitoring are configured, and VMware is shut down once everything has been validated.

Checklist before migrating each machine

Most migration problems are avoided here. This is what we check on every virtual machine, following the official Proxmox documentation:

  • Remove VMware Tools before migrating. Uninstalling them afterwards is much harder.
  • Prepare the VirtIO drivers. On Linux, make sure they are in the initramfs. On Windows, the boot disk will first start as IDE or SATA and is then switched to VirtIO SCSI following a specific procedure. If a machine does not boot, this is usually why.
  • Write down the network configuration. The network card changes. On Windows, remove the static IP before migrating: otherwise it will warn that the IP is already assigned to a card that no longer exists.
  • Check DHCP reservations and licences tied to the MAC address. Adapt the reservation or manually set the same MAC in Proxmox that the machine had in VMware.
  • Encryption with a virtual TPM (for example, BitLocker). The vTPM state cannot be brought over from VMware. Disable that encryption beforehand or keep the recovery keys at hand.
  • BIOS or UEFI boot. You have to choose the same in Proxmox: SeaBIOS for classic BIOS, OVMF for UEFI, with an EFI disk.
  • Consolidate snapshots. A machine with snapshots imports considerably more slowly.
  • Disks on vSAN or encrypted by storage policy. The wizard cannot import them: move those disks to another datastore or remove the encryption first.

Which migration method to choose

Method Downtime When to use it
ESXi import wizard The time it takes to copy the disks The default option. Available since Proxmox VE 8, tested with ESXi 6.5 to 8.0. It maps almost all of the machine’s configuration.
Live import Minutes Starts the machine in Proxmox while the data is being copied. If the import fails, anything written since it started is lost: test it first and avoid it on slow or unstable networks.
OVF export and import High When there is no direct connection to the ESXi host or you already have the machines exported.
Disk import (qm disk import) Medium For disks copied to a shared resource or cases the wizard does not cover.
Attach the disk and move it live Minimal Large disks on a shared resource accessible from both environments. More laborious: the machine must never be running on both sides at the same time.
Restore from backup Variable If your backup tool can restore directly to Proxmox.

Many machines: how to organize the migration

  • Import from the ESXi host, not from vCenter. It can be done through vCenter, but performance drops considerably.
  • Don’t launch everything at once. Proxmox recommends importing no more than four disks at the same time. The ESXi API allows few connections and, if it is overloaded, it blocks all imports in progress.
  • Group by physical server. The VMware savings come when you empty entire hosts before the renewal, because the licence counts host cores, not virtual machines.

What to do with your SAN array or NAS

Many companies have their storage on an iSCSI or Fibre Channel array and want to keep using it. Proxmox recommends Ceph for shared storage, but version 9.2 offers several options for an existing array:

  • One large LUN with shared LVM. It is the easiest to maintain. Since version 9.0 it supports snapshots as a technology preview.
  • NFS or SMB from the array or NAS. Allows snapshots with the qcow2 format.
  • The array vendor’s plugin, if one is available.
  • Backups instead of snapshots. With Proxmox Backup Server, backups of running machines are fast and a machine can be started while it is being restored.

If there are several paths to the array, configure multipath.

Clustering and high availability: what you should know

  • At least three nodes. With two servers, an external vote (QDevice) is added, which can be a small machine.
  • A dedicated network for the cluster (Corosync), ideally with a second one as backup. If it shares cabling with storage or backups and becomes saturated, the nodes may reboot to protect the data.
  • Disks must be on shared storage for high availability to start the machines on another node. In small clusters, ZFS with replication works, bearing in mind that it is asynchronous and the last few minutes can be lost.

Common mistakes to avoid

  • Migrating without an inventory: forgotten dependencies appear, such as a licence tied to a MAC address or a disk.
  • Leaving the VMware drivers in place: on Windows you have to prepare the VirtIO drivers before changing the disk and network.
  • Forgetting backups: the VMware backup system does not work in Proxmox; the new one has to be running from day one.
  • Finishing after the renewal date: if the last batch is migrated a month late, you may pay for another full VMware period.
  • Calculating only the licence: migration hours, hardware and team training also count.

How we do it at Binovo

We are a Proxmox Silver Partner and have worked with Proxmox since 2013. We carry out the inventory and design, prepare each machine with the checklist, migrate during off-peak hours, leave the backups up and running and take over maintenance if you need it. If you have Odoo on those servers, we also review it so the migration does not affect invoicing, TicketBAI or Verifactu.

More information in Proxmox partner in Spain and Systems administration. If you want to know how much it would cost you, get in touch or call +34 943 569 206.

Frequently asked questions

Is Proxmox VE free?

Yes. The software is free and can be used in production without paying. The subscription is optional and gives access to the enterprise repository and official support.

How long is service down during the migration?

It depends on the size of the disks and the network. With live import, the machine starts in Proxmox while the data is copied, so downtime is usually a matter of minutes per machine.

Can I reuse my current servers?

Usually, yes. Proxmox runs on the same hardware as ESXi. It is worth checking the disk controller and the network before you start.

Can I import from vCenter?

Yes, but it is much slower. The recommended approach is to connect the wizard directly to each ESXi host.

What about vSAN?

The import wizard does not support disks on vSAN. They have to be moved to another datastore first, and distributed storage is set up with Ceph in Proxmox.

What about machines with BitLocker or a virtual TPM?

The virtual TPM state cannot be migrated from VMware. Disable that encryption before migrating or save the recovery keys to unlock the disk in Proxmox.

Can I keep using my SAN array?

Yes. It can be used with shared LVM over iSCSI or Fibre Channel, via NFS or SMB, or with the vendor’s plugin if there is one. Each option has different snapshot capabilities.

And backups?

Proxmox Backup Server makes incremental, deduplicated backups of the machines and is free. We recommend having it running before you shut down VMware.

Sources

Transparency: this article was prepared with the help of artificial intelligence from the sources cited and was reviewed and validated by the Binovo team before publication. It is a translation of the Spanish original.

Leave a Reply