Project · Migration

Migrating from VMware to Proxmox: analysis, cutover, operations

In brief

Our VMware to Proxmox migration follows nine stages: we analyze your ESXi environment, build the Proxmox VE cluster alongside it, convert and test every virtual machine (VM), and cut over with a rollback plan. Your VMware environment stays untouched until then, and each VM's switchover typically takes minutes. After the analysis, we quote a fixed price for migration and operations.

Background

Broadcom and vSphere: why companies are evaluating a VMware alternative now

Two vendor-side changes are prompting companies to evaluate a Broadcom VMware alternative: the move to subscription-only licensing and the end of general support for individual vSphere versions. Both are documented by the vendor, with sources and dates listed below this section. Which deadlines apply to you depends on your vSphere version and when your contracts end.

According to VMware, the company announced the move from perpetual licenses to a subscription model on December 11, 2023. In January 2024, VMware named VMware Cloud Foundation and VMware vSphere Foundation as its two new offers, both available as subscriptions only, and stated that many former standalone products would only be offered as part of these bundles (source 1).

Broadcom ended general support for vSphere 7.0, covering ESXi 7.x and vCenter Server 7.x, on October 2, 2025 (source 2). For how to plan around the vSphere 8 support deadline and how the licensing models differ, see our Proxmox vs VMware comparison.

When you replace vSphere, your own contract terms set the timeline: they determine when the new environment has to be in production. Our target platform, the managed Proxmox cluster, is based on Proxmox VE with KVM (Kernel-based Virtual Machine).

Sources: (1) VMware by Broadcom, “VMware End Of Availability of Perpetual Licensing and SaaS Services,” January 22, 2024, blogs.vmware.com · (2) Broadcom Knowledge Base, article 415405, “End of General Support for vSphere 7.0,” knowledge.broadcom.com · retrieved October 9, 2026 · As of October 2026

Process

Our VMware migration services in nine stages

Our VMware migration services take you through nine stages, from your existing environment to managed operations. The new cluster is built alongside your VMware environment, and the cutover, the point at which production switches to Proxmox VE, only happens once testing has passed.

Diagram · Migration Parallel build, cutover and rollback path
  • Existing environment (external)
  • Conversion ESXi → KVM
  • User access and rollback path
  • Existing setup stays ready to run
  • Target cluster built
The Proxmox VE cluster is built alongside the existing setup. Switchover happens VM by VM or in waves, each time after testing has passed.
Diagram as text
  1. Until the cutover, your users keep working on the VMware environment with its ESXi hosts and vCenter.
  2. In parallel, we build the Proxmox VE cluster: three or more nodes with KVM, storage on Ceph or ZFS.
  3. We convert the VMs from ESXi to KVM, in waves for larger environments, and test every VM.
  4. At cutover, user access moves to Proxmox VE on a date you choose. Until then, the VMware environment stays ready to run, and the rollback plan leads back to it if needed.
  5. We then take over managed operations with 24/7 monitoring, updates and backups.
  1. Stage 01

    Existing environment

    Your ESXi hosts, vCenter, VMs, network and storage as they run today.

  2. Stage 02

    Analysis

    We inventory VMs, dependencies and load profiles and resolve special cases such as appliances tied to specific hardware.

  3. Stage 03

    Sizing

    CPU, RAM, storage and network for the target cluster, with headroom for load peaks and growth (sizing and cluster design).

  4. Stage 04

    Proxmox cluster design

    Architecture, level of redundancy, storage design and migration sequence, in writing with an architecture diagram and a component list.

    Deliverable Written design with a fixed price

  5. Stage 05

    Parallel build

    The new cluster is built next to your existing setup, with monitoring, backups and a failover test before handover.

  6. Stage 06

    Migration

    Conversion from ESXi to KVM, including disk formats and VM configuration; larger environments are migrated in waves.

  7. Stage 07

    Testing

    Every migrated VM is checked for function, performance and reachability before it goes into production on Proxmox VE.

  8. Stage 08

    Cutover with a rollback plan

    Switchover in a planned window on a date you choose, typically within minutes per VM. Until then, the rollback plan keeps the way back to your untouched existing setup open.

    Deliverable Production running on Proxmox VE

  9. Stage 09

    Managed operations

    24/7 monitoring with on-call duty, updates, backups and a monthly operations report. You have a dedicated contact who knows your cluster.

How long the migration takes

Smaller environments are migrated in a few days, larger ones in waves over several weeks. Before that come the design and proposal, usually within a few business days, and build and testing, typically one to three weeks.

Scope

What moves when you migrate ESXi to Proxmox

When you migrate ESXi to Proxmox with us, the project covers six building blocks: converting your virtual machines from ESXi to KVM, moving network and storage, backup infrastructure in the target design, switchover planning and a rollback plan. All six are part of the scope of a managed migration.

  • Virtual machines: conversion from ESXi to KVM, including disk formats and VM configuration. Practically all common Linux and Windows VMs can be converted.
  • Network: we carry VLANs, IP addressing and firewall rules over to the target cluster, with separate networks for management, storage and public traffic.
  • Storage: your data moves to Ceph or ZFS (storage migration to Ceph). The Essentials and Business packages use Ceph; we use ZFS replication in individually designed, more compact setups.
  • Backup: backups in the target design run on infrastructure separate from the cluster, with defined retention periods and regular restore tests.
  • Downtime planning: we plan each VM's switchover time in advance, and you choose the date.
  • Rollback plan: the way back to your existing environment, which stays ready to run until the cutover has succeeded.

Features

What maps to what: VMware features in Proxmox VE

The core vSphere features have a counterpart in Proxmox VE: vMotion becomes live migration, vSphere HA becomes the HA Manager, and Ceph takes the place of vSAN. Management works differently because there is no central vCenter server. Every row is based on Proxmox documentation; for a fuller picture, read Proxmox VE or VMware vSphere.

What maps to what? VMware features and their Proxmox VE counterparts (as of October 2026)
VMware featureCounterpart in Proxmox VENote
vCenter Server Web interface, command line and REST API on every node Solved differently No central management server: any node can manage the whole cluster (multi-master).
vMotion Live migration of running VMs Equivalent Proxmox lists CPUs from the same vendor with similar capabilities on both hosts as a requirement. Passed-through PCI or USB devices block it.
vSphere HA Proxmox HA Manager with fencing Equivalent Restarts the VMs of a failed node on another node after fencing; according to Proxmox, at least three nodes are needed for reliable quorum.
DRS (Distributed Resource Scheduler) Cluster Resource Scheduler (CRS) with load balancer Solved differently According to the documentation, it currently only moves VMs and containers managed by the HA Manager.
vSAN Ceph, hyper-converged on the cluster nodes Equivalent In the Essentials and Business packages with three replicas of every block on different nodes.
Snapshots Snapshots Equivalent Provided by the storage layer, for example on Ceph RBD, ZFS or thin LVM; on file-level storage via the qcow2 format.
vSphere Standard and Distributed Switch Linux bridges with bonds and VLANs, cluster-wide via SDN VLAN zones Solved differently Link aggregation is called a bond in Proxmox VE.
NSX Proxmox VE SDN (software-defined networking) with zones for VLAN, QinQ, VXLAN and EVPN Partial According to Proxmox, core SDN is fully supported, while IP address management and complex routing are in technology preview. We record the NSX features you use during the analysis.
VMware Tools QEMU Guest Agent and VirtIO drivers Solved differently Proxmox recommends removing VMware Tools before the migration; Windows VMs need extra steps to switch to VirtIO SCSI.

Sources: Proxmox VE Administration Guide, version 9.2.13, dated September 24, 2026, chapters Introduction, QEMU/KVM, High Availability, Ceph, SDN; Proxmox wiki “Migrate to Proxmox VE” · retrieved October 9, 2026 · As of October 2026

Importing from ESXi into Proxmox VE

According to the vendor, Proxmox VE includes an import wizard that connects an ESXi host as a source and brings VMs over with most of their configuration, optionally as a live import with shorter downtime. Proxmox also documents the limits: the state of a virtual Trusted Platform Module (vTPM) cannot currently be carried over from VMware, encrypted VM disks have to be decrypted before the import, and VMs with disks on vSAN cannot be imported directly.

Risks

VMware migration risks and how we handle them

The most important safeguard in a VMware migration is parallel operation: your VMware environment stays untouched and ready to run until the cutover has succeeded, and the rollback plan takes you back to it if needed. We resolve special cases during the analysis, before the first VM moves. The table lists typical risks and how we counter them.

Risk and countermeasure How we handle the risks of a VMware migration
RiskCountermeasure
Errors or outages during the switchoverThe rollback plan leads back to your existing environment, which stays ready to run until the cutover has succeeded.
Special cases such as appliances tied to specific hardwareWe identify them during the analysis and resolve how to handle them before the migration starts.
Encrypted VM disks or a virtual TPMAccording to Proxmox, neither transfers directly. We record affected VMs during the analysis and agree on the approach before the migration.
Downtime for your usersSwitchover planned per VM, typically within minutes; you choose the date.
An undersized target clusterSizing based on load profile and requirements, with headroom for load peaks and growth.
Dependence on the service providerThe documentation of architecture, access and emergency plans belongs to you. The platform is based on Proxmox VE, KVM and Ceph.

Preparation

Checklist: what to prepare for the migration

For a VMware to Proxmox migration, we first need a complete picture of your existing environment. The more of the following you have on hand, the faster the analysis is done and the more precise the fixed-price proposal becomes. We fill in any gaps together during the analysis.

  • VM inventory: number, size and operating systems of your VMs, for example as an export from vCenter.
  • Dependencies: which systems talk to each other and in what order they need to start.
  • Guest licenses: operating system and application licenses, especially those tied to hardware characteristics.
  • Current backups: what is backed up today, how often, and how long backups are retained.
  • Maintenance windows: time slots in which individual systems can be switched over briefly.
  • Network plan: VLANs, IP ranges and firewall rules of the existing environment.
  • vSphere features in use: for example DRS rules, distributed switches, NSX or vTPM.
  • Contract terms: the end date of your VMware contracts as the latest date for the cutover.

Costs

Migration costs: comparing today with a managed Proxmox cluster

The cost of a VMware to Proxmox migration has two parts: a fixed price for the migration, which we quote after the analysis, and a fixed monthly price for operations. Whether switching pays off becomes clear when you compare your own figures over the same period. We do not quote VMware license prices because they depend on your contract.

How to compare Which cost items to set side by side, today and after the move
Cost itemToday with VMwareWith a managed Proxmox cluster
Licenses and vendor supportVMware subscription or support contract, per your agreementProxmox VE is open-source software and can be used without a license fee. The vendor offers optional subscriptions with access to the enterprise repository and vendor support, priced per CPU socket (source: proxmox.com, as of October 2026).
Hardwareyour own servers, maintenance and replacementsThe cluster nodes are part of the package; you do not need hardware of your own.
Data center and networkspace, power, cooling and connectivityPrimary site Maincubes FRA01, connected via our own network AS47263; network-level DDoS protection is included in the package.
Operationsinternal time for patching, monitoring and on-call dutyIncluded in the fixed monthly price: operations, 24/7 monitoring with on-call duty, updates and support, with no hidden hourly rates.
Your applicationyour responsibilityremains yours; we take care of everything beneath it.

You receive both fixed prices in one proposal after the analysis. Managed Proxmox clusters start with the Essentials package, three nodes with Ceph HA storage, from €449.99 net per month; we price Enterprise environments by data volume, RPO (recovery point objective) target and switchover time. All packages are listed under fixed prices for operations after the migration.

All prices are net, plus VAT.

FAQ

Questions about the VMware to Proxmox migration

How long does a migration from VMware to Proxmox take?

A few days to several weeks. Smaller environments are migrated in a few days, larger ones in waves over several weeks, while your existing setup keeps running. Before that, building and testing the target cluster typically takes one to three weeks.

Can every virtual machine be migrated?

Practically all common Linux and Windows VMs can. Special cases such as appliances tied to specific hardware are identified during the analysis and resolved before the migration starts.

How long will individual systems be offline?

Typically minutes per VM. We plan the switchover for each VM individually, and you choose the date. Until the cutover, your systems keep running on VMware.

What happens if something goes wrong during the switchover?

The rollback plan takes effect: we switch back to your existing environment, which stays untouched and ready to run until the cutover has succeeded.

How much does the migration cost?

That is settled after the analysis: you receive a fixed-price proposal for the migration and the managed operations that follow. Operating a managed Proxmox cluster starts at €449.99 net per month with the Essentials package. The initial assessment is free of charge.

Next step

How much work will your VMware migration be?

Tell us the number and type of your VMs, the vSphere features you use and your timeline. You receive an initial assessment of the effort and approach within one business day; the fixed-price proposal for migration and operations follows the analysis.

Get your VMware environment assessed

Related