Why Proxmox Keeps Turning Up in Migration Plans

Very few pieces of infrastructure software win market share on merit alone. Most of them win it because the incumbent did something to its pricing. Proxmox Virtual Environment has spent the last two years as the beneficiary of exactly that dynamic, and the arithmetic is worth walking through carefully, because it explains why the platform keeps appearing in migration plans written by people who had never previously considered leaving VMware.

The number that started it

Broadcom closed its acquisition of VMware in late 2023 and began restructuring how the product is sold. The change that did the most damage to small deployments arrived in spring 2025.

The Register reported in March 2025, citing distributor Arrow, that as of April 10 the minimum core count on a VMware subscription would rise from 16 to 72. The consequence is easy to state and hard to argue with: a customer running a single eight-core processor pays for 72 cores, which is 64 cores of software they cannot use.

The same reporting noted a 20% uplift applied to customers who miss their renewal anniversary.

By May 2025, The Register was reporting European customers’ claims of increases between 800% and 1,500%. Those figures come from customers rather than from Broadcom, and they describe particular situations rather than an average, so treat them as the shape of the complaint rather than a published price list. The direction is not in dispute.

For a large enterprise with dense hosts, a 72-core floor is irrelevant because they were already past it. For a two-host cluster in a regional business, a school district, or a managed service provider running many small tenants, it is the entire budget conversation.

What the alternative costs

Proxmox VE is open source and can be run with no subscription at all. Subscriptions buy access to the enterprise package repository and support, priced per CPU socket per year. From Proxmox’s own pricing page:

Tier	Price per socket per year	What it buys
Community	€120	Enterprise repository, community forum support
Basic	€370	3 support tickets, one business day response
Standard	€550	10 tickets, four hour response
Premium	€1,100	Unlimited tickets, two hour response

Every tier has identical features. You are buying support response times, not capability, which is a refreshingly legible way to sell software.

Note the unit as well. Proxmox charges per socket. The pricing change that pushed people out of VMware was denominated in cores. On a modern two-socket host with high core counts, that difference compounds quickly.

The honest counterweight

This is the point where a vendor-neutral post is supposed to say the migration is easy. It is not, and pretending otherwise does nobody any favors.

What you give up leaving vSphere is a mature and very deep operational ecosystem. Distributed Resource Scheduler behavior, the backup and replication tooling built around VMware’s APIs, the vendor support relationships, the staff who have run it for a decade, and the third-party products that assume it exists. Proxmox has answers for most of these. They are not the same answers, and your runbooks do not transfer unedited.

There is also a skills question. Proxmox is Debian underneath, currently Debian 13 in the 9.0 release. Storage is frequently ZFS or Ceph rather than VMFS. Containers are LXC rather than a VMware construct. A team that is fluent in vSphere and uncomfortable at a Linux shell is going to find the first six months harder than the sales case implied.

That is a training cost, and it belongs in the migration budget next to the licensing savings. Teams that leave it out are the ones who end up unhappy.

Why this matters beyond virtualization

The reason to pay attention even if you have no VMware estate is that this is the clearest recent example of a pattern worth recognizing. A platform becomes ubiquitous. Ubiquity gets acquired. Pricing is restructured toward the largest customers. The long tail goes looking, and an open source option that was previously considered a homelab toy gets a second evaluation from people with purchase authority.

The same story has played out with monitoring stacks, with CI systems, and with databases. It will play out again. The practical lesson for anyone building a career in infrastructure is that the skill worth having is not deep fluency in one vendor’s console. It is understanding the underlying primitives well enough that a platform change is an inconvenience rather than a crisis.

Storage, networking, and virtualization concepts move between platforms. Menu paths do not. What actually transfers is worth knowing before the migration plan is written.

Sources: The Register on the 16-to-72 core minimum, The Register on European customer price claims, Proxmox VE pricing, Proxmox VE 9.0 release.