From VMware to Proxmox: a sane migration
When Broadcom acquired VMware, the licensing model changed: subscriptions became mandatory, perpetual licenses ended, bundles grew. For small teams and homelabbers, the bill is now out of proportion. That is why many are looking at Proxmox. This page covers three things: why Proxmox is the natural destination, how to migrate sanely, and how Atlas makes the Proxmox side comfortable once the move lands.
Why people are leaving VMware
The licensing model moved to subscription; perpetual licenses ended. The recurring yearly cost for the same hardware became disproportionate, especially on small setups.
Bundling grew: tiers priced with components nobody asked for. The bill for a simple hypervisor is larger than the part actually used.
Uncertainty: roadmap and pricing depend on a single vendor. An open-source foundation removes that dependency.
Why Proxmox?
Open source and no vendor lock-in: KVM (full virtualization) and LXC (containers) on one platform, usable without a subscription.
ZFS, snapshots, live migration, clustering and built-in backup (PBS): enterprise features that come in the free core.
Mature and active: a large community, regular releases, real production use. It scales from homelab to small business.
A sane migration order
Migration is not something to rush; this order lowers the risk:
Take inventory: VMs, resources, disk sizes, network dependencies. Know what moves and in what order.
Plan target storage: ZFS or LVM on the Proxmox side, what redundancy. Set it up before the migration.
Convert disks: turn VMware disks (vmdk) into a Proxmox format (qcow2/raw); qm importdisk exists for this.
Map the network: VMware port groups should map to Proxmox bridge/VLAN structure; lay out the IP and VLAN plan.
Test first: move a non-critical VM, verify boot and services; then continue down the order.
Cut over in a window: move the remaining VMs in a maintenance window, watch the first boots, keep the old side as backup for a while.
Atlas softens the landing
Atlas does not perform the migration; it makes the Proxmox on the other side comfortable from day one:
Everything moved, on the map
Migrated VMs and containers appear on the live topology: which resource they use, where they sit, at a glance.
Safe updates
Keeping the new Proxmox current stops being scary: effect groups, dry-run, snapshot-first and boot guard.
Storage on one screen
After migration, ZFS/LVM pools, datasets and disk health on one map; the new setup becomes readable at once.
A sentinel from day one
Atlas Watch monitors the host: if something goes wrong right after the migration, word arrives in daylight, by email.
Frequently asked questions
- Is Proxmox ready for production?
- Yes. Proxmox VE has been used in real production for years; KVM and LXC are mature technologies. Enterprise features including clustering, live migration and built-in backup come in the free core.
- Can I import my VMware machines into Proxmox?
- Yes. VM disks are converted from the VMware format (vmdk) to a Proxmox format and imported; qm importdisk is made for this. Some guests may need driver or boot adjustments after the move.
- Does Atlas migrate for me?
- No, let us be clear: Atlas is not a migration tool. The migration itself follows the steps above; Atlas makes managing the Proxmox on the other side comfortable, with topology, safe updates, storage and Watch.
- What should I use instead of the free ESXi edition?
- Proxmox VE. Even for a single host the free core is more than enough, and the limits of free ESXi (no central management, no vMotion) are not here. Atlas also makes the single-host experience visual and safe.
- Will there be downtime during migration?
- There is a short per-VM downtime (power off, move/convert the disk, boot on the target). With a good inventory and a maintenance window, total downtime stays at a few minutes per VM; start by testing with non-critical ones.
Related entries
- Moved a machine from VMware and it will not boot: the disk is there, the road to it is not The most common failure after a VMware migration is not a lost disk. It is a guest that no longer recognises the controller in front of the disk, and the fix is reversible at every step if you change one thing at a time.