Open licensing model
- Proxmox VE is open source; the enterprise repository and vendor support are available by optional subscription
Migrate VMware to Proxmox - Move ESXi and vSphere workloads in a controlled process
WZ-IT inventories your VMware environment, designs the Proxmox target architecture, and supports the pilot migration, cutover, rollback path, and subsequent operations.
- Open licensing model
- Open source
- Privacy-focused
- Planned cutover
Why Switch?
VMware ESXi vs. Proxmox: The Difference
Compare technology, operating model, and licensing
Clustering and HA built in
- Cluster management and HA are part of Proxmox VE
No Vendor Lock-in
- Full control over your infrastructure
| Feature | VMware | Proxmox |
|---|---|---|
| License Costs | High annual fees | Open source; subscription optional |
| KVM Virtualization | ESXi (proprietary) | KVM (Linux Kernel) |
| Container Support | vSphere Kubernetes Service included in VVF | LXC (natively integrated) |
| Web Interface | vSphere Client | Integrated Web UI |
| Clustering / HA | vCenter included in VVF and VCF (per-core subscription) | Included |
| Live Migration | vMotion | Included |
| Storage Options | vSAN, VMFS | ZFS, Ceph, NFS, iSCSI |
| Backup Solution | Additional software needed | PBS (integrated) |
Technical Details
Enterprise Features in Detail
Proxmox VE provides all features for production enterprise environments
High Availability Cluster
Min. 3 nodes recommended for quorum · Automatic failover on node failure · Fencing for data consistency · Corosync for cluster communication
Security
LDAP/AD/OIDC integration · Two-factor authentication · Role-based access control · Integrated firewall
Storage Options
ZFS: Snapshots, compression, dedupe · Ceph: Distributed storage for HA · NFS/iSCSI: Network storage · LVM: Thin provisioning
Hardware Requirements
Intel VT-x / AMD-V CPU · Min. 2 GB RAM (8+ GB recommended) · SSD/NVMe for best performance · ECC RAM recommended for ZFS
Virtualization
KVM: Full virtualization (Windows, Linux) · LXC: Lightweight containers · VirtIO drivers for performance · GPU/PCI passthrough supported
Backup & Recovery
Proxmox Backup Server (PBS) · Incremental backups · Deduplication & compression · Encrypted offsite backups
More about PBS
Proxmox documentation: HA Documentation · Storage Documentation · System Requirements · VM Documentation · User Management
Reference Architectures
Typical Proxmox Setups
From simple single-server solutions to highly available enterprise clusters
Entry
Single-Node Setup
- Ideal for small businesses, development environments, or initial tests
- CPU: 16 Cores / 32 Threads
- RAM: 128 GB DDR5 ECC
- Storage: 2× 1.92 TB NVMe
- VMs: 10-30
- HA: No
Hetzner AX102: AMD Ryzen 9 7950X3D
Recommended
3-Node HA Cluster
- Production environment with high availability and automatic failover
- CPU: 3× 48 Cores / 96 Threads
- RAM: 3× 256 GB DDR5 ECC
- Storage: Ceph / Shared NFS
- VMs: 50-150
- HA: Yes (Quorum)
Hetzner: 3× AX162-R (AMD EPYC 9454P)
Enterprise
Hyper-Converged (Ceph)
- Distributed storage with Ceph for maximum scalability and redundancy
- CPU: 5+ × 48 Cores
- RAM: 5+ × 256+ GB ECC
- Storage: Ceph (NVMe OSDs)
- VMs: 200+
- HA: Yes + Storage-HA
Hetzner: 5× AX162-S (3.84 TB NVMe)
ZFS/Ceph: ECC RAM strongly recommended for data integrity
HA Cluster: Min. 3 nodes for quorum; 2-node only with ext. quorum device
Live migration: shared storage avoids transferring VM disks. Local disks can be transferred when target storage and network are suitable and no non-migratable local resources are attached Further prerequisites: same PVE cluster, compatible CPUs and the same or newer PVE packages at the destination (Proxmox QEMU manual).
Ceph: Only with sufficient hardware (RAM, 10GbE, NVMe) - otherwise ZFS/NFS
Building blocks
Storage, network and backup in the target design
Storage
Storage Options Comparison
- ZFS (Simple): Local per node. Snapshots, compression, dedupe. Ideal for single-node or local storage. ⚠ ECC RAM recommended
- Ceph (Complex): Distributed storage across all nodes. Self-healing, scalable. For HA clusters with high IOPS. ⚠ Min. 3 nodes, 10GbE network recommended
- NFS / iSCSI (External): External NAS/SAN. Shared storage for live migration without Ceph. Simpler with existing storage.
Network
Network Configuration
- Linux Bridge (Default): Simple configuration, sufficient for most setups. VLAN support available.
- Open vSwitch (OVS) (Advanced): Software-defined networking. VLANs, VXLAN, complex topologies. For large environments.
- SDN (Proxmox 7+) (Modern): Integrated SDN in Proxmox. Central management of zones, VNets, subnets.
Tip: Separate network for storage/cluster traffic recommended
3-2-1
Recommended Backup Strategy (3-2-1 Rule)
- 3 Copies: Original + 2 backups. PBS local + offsite (e.g., Hetzner Storage Box)
- 2 Media Types: Different storage types: Local (NVMe) + Remote (Object Storage/NFS)
- 1 Offsite: At least 1 backup stored externally. Encrypted, automated, regularly tested
Backup Frequency: Daily: Incremental backups of all VMs · Weekly: Full backup + offsite sync · Monthly: Perform restore test
PBS Features: Deduplication saves 50-80% storage · AES-256 encryption for offsite · Backup integrity verification More about Proxmox Backup Server →
Our Process
How Your VMware-to-Proxmox Migration Works
A proven 6-step process for secure migrations
- 01
Assessment & Planning
Analysis of your VMware ESXi infrastructure: Document VMs, networks, storage, dependencies, and license situation.
- 02
Set Up Proxmox Environment
Installation and configuration of Proxmox VE on dedicated hardware (on-prem or Hetzner).
- 03
Test Import & Validation
Test migration of individual VMs, check performance and functionality, install VirtIO drivers.
- 04
Full Migration
Import VMs to Proxmox (VMDK → qcow2/RAW), reconfigure network and storage.
- 05
Stabilization & Go-Live
Start VMs, verify, activate monitoring and backups, final cutover with minimal downtime.
- 06
Operations & Support
Maintenance, updates, performance tuning, and ongoing support by our team.
Proxmox VE 8 reached end of life in August 2026. New migrations should target PVE 9.2 with Debian 13.5 and Linux kernel 7.0 directly. Already migrated to PVE 8? We also assess and plan the upgrade to PVE 9.
- Proxmox VE9.2
- Debian13.5
- PVE 8End of life August 2026
Transparency
Risks & Pre-Migration Checklist
Every migration brings challenges - we handle them transparently
Potential Challenges
- VM Compatibility: VMs with vTPM, proprietary VMware drivers, or special vSphere features require adjustments
- Network Reconfiguration: vSwitches and port groups need to be mapped to Linux bridges or OVS
- Storage Conversion: VMDK disks are converted to qcow2/raw - time-intensive with large data volumes
- Downtime During Cut-Over: Brief downtime during final switchover is usually unavoidable
Our Solution: Through careful planning, test migrations, and rollback strategies, we minimize all risks.
Pre-Migration Checklist
- Complete VM inventory (names, IPs, resources, dependencies)
- Network documentation (VLANs, subnets, firewall rules)
- Storage analysis (capacity, performance requirements)
- Create backup of all VMs before migration
- Identify test VMs for pilot migration
- Coordinate maintenance window with stakeholders
- Document rollback plan
- Prepare VirtIO drivers for Windows VMs
- Validate target hardware (CPU, RAM, storage)
- Prepare monitoring & alerting
Hosting Options
Where Should Your Proxmox Environment Run?
Recommended
Dedicated Server at Hetzner
- German data centers (GDPR)
- High-performance hardware
- Transparent, low prices
- Unlimited traffic (1 Gbit/s uplink)
- Ideal for Proxmox clusters
Full control
On-Premises / Own Hardware
- Use existing hardware
- Maximum data control
- No ongoing hosting costs
- Ideal for compliance
- We install remotely
Practice & Resources
VMware migration by WZ-IT: services and evidence
Evidence from a cloud exit project (lift and shift, AWS to Hetzner).
- EVA Real Estate: 81% Cloud Cost Reduction
- 81%
- Case Study AWS → Hetzner
- per month
- $1.300 → $250
- Lift & shift migration (VMs transferred 1:1)
- $12,600 annual savings
- $12,600
- with documented privacy safeguards in Germany
VMware Migration Experience
We plan VMware-to-Proxmox migrations with a test run, cutover, validation and documented rollback plan.Controlled Cutover
Validation and an agreed rollback window reduce cutover risk.Full-Service Support
Migration, managed hosting, monitoring, and support from a single source - even after migration.Proxmox Experts
Deep expertise in Proxmox, ZFS, Ceph, clustering, and high-availability configurations.GDPR Compliance
EU target locations are selectable. We document data flows and advise on data protection and compliance requirements.Transparent Pricing
The migration scope is quoted transparently after inventory, pilot planning, and target-architecture review.
How we migrated EVA Real Estate's entire infrastructure from AWS to dedicated servers at Hetzner - from $1,300 to $250/month.
Read Case StudyBefore migration
Start VMware migration: fixed-price exit assessment
We assess your VMware infrastructure and define the target architecture, dependencies, pilot, cutover, and operations handover.
Virtualisation exit assessmentfrom €1,490 excl. VATSchedule agreed after receipt and review of the documents
Assess a VMware or Hyper-V exit with a defined scope
- The exit check provides a Proxmox target design, risks, migration waves and a reliable implementation framework before production systems change.
Non-binding initial assessment · Response usually within one business day
VMware Migration FAQ
Answers to the most important questions
Basics & Comparison
- Proxmox VE is a virtualization platform with KVM and LXC, licensed under GNU AGPLv3, with an integrated web interface and storage and network management. The software is free to download and use (source). Compared to VMware ESXi, Proxmox VE differs in its licensing model (open source instead of proprietary) and in that clustering, HA and management are part of the package.
- Typical reasons are VMware's changed licensing model since the Broadcom acquisition (subscription instead of perpetual licenses), the desire for cost and vendor independence, and open-source flexibility. Whether Proxmox costs less depends on the specific environment and quotations; licensing model, required features, operational effort and total costs need to be compared.
- Yes. Proxmox offers HA clustering, live migration, ZFS/Ceph storage, integrated backups, and container support - sufficient for SMBs to enterprise workloads.
- No - Proxmox is open source under AGPL. There are optional support subscriptions, but the base version is free and includes all features.
- Proxmox VE uses KVM, which is part of the Linux kernel. Performance depends on hardware, guest configuration (e.g. VirtIO drivers), storage and workload and should be measured for the intended environment. No blanket performance difference to VMware ESXi can be stated.
Migration Process
- We start with an assessment (VMs, resources, dependencies, network/VLANs, storage, backups) and then build the Proxmox target environment. We then migrate VMs in a pilot test, optimize drivers/performance, and plan the final cutover with minimal downtime.
- In practice, downtime mainly depends on the final cutover (last data synchronization, last shutdown/start). For many workloads, the production switch can be scheduled during a maintenance window; we plan it so the interruption is as short as possible (including rollback option).
- Classic server VMs (Windows/Linux), web/app servers, database servers, internal tools, monitoring/logging, file services, and many business workloads migrate very well. For special cases (e.g., very hardware-specific appliances), we check compatibility and alternatives in advance.
- The most common issues are: driver changes (network/SCSI), UEFI/BIOS mode, Secure Boot/vTPM, network mapping (vSwitch/Portgroups → Linux Bridge/OVS), storage layout, and cutover planning. That's exactly why we always do pilot VMs and a clear migration plan.
- Depending on the situation, disks are converted (e.g., to qcow2 or raw) and then attached in Proxmox. For conversions, qemu-img convert is a common approach (defining input/output format).
- Yes - Proxmox supports snapshots (depending on storage backend). We coordinate with you whether you prioritize 'VM snapshots for quick rollbacks' or 'backups for disaster recovery' (or both).
- Windows runs very well under KVM - the key is usually clean driver/device configuration (e.g., paravirtualized devices) so network and storage perform well. We test each VM (boot, network, services) and then optimize specifically.
- Yes - ideally: clean VM inventory, known dependencies (databases, AD, file shares), defined maintenance windows, and current backup status. We also clarify special features (UEFI/Secure Boot/vTPM, special NICs, passthrough) so the plan is realistic.
- Yes - we plan the cutover so your VMware environment remains untouched until final acceptance. If something unexpected occurs, you can abort go-live and switch back (rollback plan is part of the planning).
- These features can make migrations more complex because they have hypervisor-specific dependencies. We identify such VMs early (e.g., Windows 11, certain security policies) and plan the appropriate target configuration and test steps per VM.
- We work with checklists per VM: boot, network, storage I/O, services, monitoring, application function, logs. For critical systems, we also do 'app owner tests' and an acceptance phase before finally shutting down VMware.
- Timing depends on VM count, data volume and complexity. Larger estates are migrated iteratively (pilot → batch waves → cutover) with testing; the timeline is agreed after assessing data volume, dependencies, testing and cutover windows.
Technology & Features
- We map your VMware networks (Portgroups/VLANs) to Proxmox bridges (or OVS), including tagging/trunks, IP plan, and firewall rules. Goal: same segmentation as before - just under Proxmox.
- Usually yes. We plan the cutover so IPs/hostnames remain unchanged as much as possible (or we coordinate DNS/reverse-DNS/firewall changes). If networks need to change, we do it transparently and documented.
- Yes - live migration is possible in Proxmox when storage/cluster prerequisites are met (e.g., shared storage or suitable cluster setup). We advise you on which target setup (single-node vs 3-node cluster vs Ceph) meets your requirements.
- This depends heavily on your goals: ZFS is very popular for local performance + snapshots (simple/robust), NFS/iSCSI makes sense if you already have NAS/SAN or want shared storage, Ceph for scalable, highly available storage in cluster (with appropriate resources). We choose based on budget, IOPS, HA goal, and team size.
- Often not 1:1 as 'native restore' in the new hypervisor - but you can keep them as an additional safety layer (e.g., while VMware still runs in parallel). For Proxmox, many teams then switch to Proxmox Backup Server (PBS) for deduplicated, compressed backups with encryption options.
- Pragmatic: regular VM backups + offsite copy + restore tests. PBS is often the foundation because it supports incremental backups (with dedupe/compression) and offsite workflows are easily implemented.
- Proxmox includes central web management, cluster functions, and HA mechanisms - without a separate 'vCenter license world'. Whether you need HA immediately or scale later, we clarify based on your SLA requirements.
- Yes - Proxmox supports PCI/GPU passthrough for NVIDIA and AMD GPUs. Ideal for AI inference, machine learning, or graphics-intensive applications.
- Yes - Proxmox combines KVM VMs with LXC containers, providing maximum flexibility: VMs for heterogeneous operating systems, containers for lightweight services.
Hosting & Operations
- Yes - Proxmox is ideal for dedicated servers, both on-premises and in data centers or with hosting providers like Hetzner. This allows VMs and containers to run performantly and flexibly.
- Yes. Many customers separate locations/workspaces or implement hybrid architectures. We build it so latency, data residency requirements, and operational effort fit together (including technical documentation of components).
Our Service
- Yes. We operate Proxmox and, where required, PBS with monitoring, updates, backup management, capacity planning, and agreed incident response - on dedicated servers, European infrastructure, or on premises. Documented restore tests can be explicitly added.
- Proxmox is actively developed, with regular release cycles, security updates, and community + optional commercial support - so it's maintainable and future-proof long-term.
- Costs depend on VM count, storage and special cases. The virtualisation exit assessment starts at €1,490 net; the project is priced by scope after inventory.
- The import wizard requires the VM to be shut down on ESXi. Live import starts it on the target during import and can shorten interruption. vSAN is not supported as a source: move VMs to NFS or VMFS first. Proxmox migration documentation.
- Operating systems, storage, HA, backups and the operating model determine the choice. The Proxmox vs. VMware comparison explains the differences.
Knowledge
Migration guide and more Proxmox services
Migration Guide
More Proxmox Services
Not coming from VMware?
Related tutorials & guides
- k3s, k0s, RKE2 or Talos: Kubernetes distributions compared 2026Comparisons of Kubernetes distributions usually place k3s, k0s, RKE2 and Talos side by side and compare memory footprint and start-up time. That misses the most...
- The VMware licensing trap for SMEs: the Essentials Kit has no successorCoverage of VMware pricing works with large numbers: fourfold increases, 60 per cent extra cost, percentages from analyst reports. Such figures are striking and useless...
- pedit COW & DirtyClone: Two Critical Linux Kernel Flaws in 2026Within a few weeks in 2026, two Linux kernel local privilege-escalation flaws were published that work the same way: CVE-2026-46331 (nicknamed "pedit COW") and CVE-2026-43503...
- Hetzner price increase June 2026: CPX and CCX up to +176% - our takeFor many - us included - Hetzner was the obvious answer to expensive hyperscalers for years: cheap, solid, operated in the EU. That is exactly...
- Proxmox VE 9.2 vs VMware: Is It Time for SMEs to Switch?Proxmox VE 9.2 has been available since May 21, 2026. On paper, it is a minor release. In practice, it matters much more for many...
- Linux Kernel Vulnerabilities 2026: Why Patch Management Is Now a Board-Level Issue (Dirty Frag, Copy Fail & Co.)Three critical Local Privilege Escalation vulnerabilities in the Linux kernel within two weeks — all three sitting in the code for nine to twelve years....
- Proxmox Backup Server 4.2: S3 Storage Exits Tech Preview — What You Need to KnowWith Proxmox Backup Server 4.2 (released late April 2026), S3-compatible object storage is officially supported as a backup backend. No more tech preview label, no...
Reviews & projects
Proxmox proof from real projects
Customer feedback on virtualization, backup, VPN, security and ongoing cluster operations.
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT
Read client reviews
Enquiry
Assess a virtualisation migration to Proxmox
Describe the source platform, workloads, and available cutover window.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.