Cutting recurring virtualization costs: what migrating to Ubuntu actually changes

Per-core subscription bundling reset virtualization costs permanently higher. Here is how the Ubuntu Pro model compares on licensing, flexibility and long-term cost — and how lift-and-shift migration actually runs.

Category: Cloud & Infrastructure · Published: August 6, 2026 · 10 min read · Author: ZM Technologies Team

There is a specific conversation happening in IT departments right now. The renewal quote arrives, someone reads it twice, and a meeting gets scheduled that nobody wanted to have. It is worth understanding precisely what changed, because the answer shapes what you should do next.

What changed in the virtualization market\n\nBroadcom's acquisition of VMware closed in November 2023, and what followed was a structural rebuild of how the product is sold. Perpetual licensing ended — VMware moved to subscription-only in 2024, which makes any increase a permanent change to your annual run rate rather than a one-time hit.\n\nThe catalogue collapsed: more than 8,000 SKUs were consolidated into a short bundle list led by VMware Cloud Foundation and vSphere Foundation, and vSphere Standard as a standalone perpetual product was discontinued, pushing smaller estates into richer bundles than they need.\n\nLicensing moved to per-core with a 16-core-per-CPU minimum; a 72-core minimum was proposed in April 2025 and reversed after customer pushback. Survey data published in 2026 found 86% of organisations actively reducing their VMware footprint and 88% still concerned about future pricing. In March 2026, CISPE filed an antitrust complaint with the European Commission over the termination of most VMware Cloud Service Provider partnerships in Europe.

The three differences that actually matter\n\n### 1. Licensing type\n\nPer-core subscription billing in mandatory bundles means your bill scales with the density of your hardware: buy denser servers to consolidate, and your licensing cost rises with them.\n\nUbuntu Pro is priced per physical machine. Sockets, cores and CPU count are irrelevant. One host running thirty virtual machines is one subscription, so consolidation lowers your bill instead of raising it. And it is a subscription rather than a licence — Ubuntu is open source and free to run, so the consequence of stopping is that you lose patches, not that you lose the right to run your infrastructure.\n\n### 2. Flexibility\n\nCatalogue consolidation means paying for capabilities you may not use. Ubuntu Pro runs the other direction: one subscription, and the platform components come with it. MicroCloud and OpenStack for virtualization, Ceph for storage, Kubernetes, Landscape for fleet management, MAAS for bare-metal provisioning, Juju for application automation — nothing separately purchased.\n\nThe same subscription also covers the applications running inside those VMs: over 36,000 open source packages in Ubuntu's Universe repository get security maintenance for up to ten years.\n\n### 3. Long-term cost\n\nBecause Ubuntu Pro also extends the life of the operating system — five years standard, ten with Pro, fifteen with the Legacy add-on — you are not forced into an OS upgrade project on someone else's schedule. Ubuntu 22.04 LTS leaves standard support in April 2027; with Pro that same release stays patched to April 2032, or April 2037 with Legacy.\n\nFor most estates the compounding saving is not the sticker price. It is not running a forced migration every five years.

Lift and shift from whatever you are running\n\nWe migrate using Coriolis, which performs automated lift-and-shift of virtual machines along with their storage and networking configuration. Source platforms include VMware vSphere and ESXi, Microsoft Hyper-V, OpenStack, AWS, Azure, Oracle Virtualization, Red Hat Virtualization, Virtuozzo Hybrid Infrastructure and physical Linux servers. Destinations include MicroCloud, Canonical OpenStack, bare-metal Ubuntu and public cloud.\n\nTwo destination options, both covered by the same Ubuntu Pro subscription with no additional platform licence:\n\n- MicroCloud suits smaller and edge deployments — hyperconverged, built on LXD, Ceph and OVN, one node for testing, three minimum for high availability, scaling to fifty-node clusters.\n- Canonical OpenStack suits large data centre environments needing full private-cloud capability.\n\nBeing straight about this: it is not a click-and-done exercise. Complexity depends on workload profile, and the honest sequencing for most organisations is to migrate in waves — non-critical workloads first, tier-one last, while the existing platform stays in place until the new one is proven.

Support you can escalate to\n\nRunning open source in production raises a fair question: who do you call at 3am? Canonical offers enterprise support tiers on top of Ubuntu Pro at 24/7 or weekday availability, covering the operating system, the infrastructure layer and the open source applications on top of it — phone and ticket access, break-fix, bug-fix and troubleshooting, from the organisation that builds the distribution. ZM Technologies sits alongside that as your local first line, with Canonical behind us for escalation.

Where to start\n\n1. Model your next renewal under per-core bundling, not your current bill.\n2. Count physical hosts, not VMs — this is what an Ubuntu Pro estimate is built from.\n3. Inventory your open source packages, since much of what you are separately subscribed to may already be covered.\n4. Pick a wave-one workload — something real but not tier-one.\n\nTalk to ZM Technologies and we will run steps one to three together. If you want the coverage detail first, read what Ubuntu Pro actually covers.