VMware in the Post‑Broadcom Era 2026: What DACH Companies Must Decide Now

8 min. read Updated: 22.04.2026

Broadcom has fundamentally restructured VMware’s licensing model: perpetual licenses have been abolished, 168 product bundles have been reduced to four, the metric has shifted from per-CPU to per-core, and the minimum order stands at 72 cores per purchase. For DACH companies running a mature VMware environment, this has led to an average cost increase of 60 percent over seven years; in individual cases, price hikes between eight- and fifteen-fold have been reported. The question in spring 2026 is no longer whether to respond, but how.

Key Takeaways

• Subscription Only: Broadcom has eliminated all perpetual licenses; VMware is now sold exclusively as a subscription. The metric is per-core, with every CPU counted at a minimum of 16 cores.
• Four Bundles Instead of 168: The product landscape has been reduced to VMware Cloud Foundation (VCF), vSphere Foundation (VVF), vSphere Standard (VVS), and vSphere Essential Plus (VVEP). VCF carries a list price of approximately 350 US dollars per core per year (Redress Compliance analysis).
• Minimum Order 72 Cores: Smaller environments must overbuy, and single-host scenarios are barely economically viable. Late renewals carry a flat 20 percent surcharge with no grace period.
• Alternatives Are Maturing: Nutanix AHV is widely regarded as the most direct enterprise replacement for VCF; Proxmox VE has graduated from lab environments to production-ready status; Microsoft Azure Stack HCI and Red Hat OpenShift Virtualization are also in the running.
• The Window Is Closing: DACH companies facing renewals in late 2026 or early 2027 should be evaluating alternatives right now. Those who wait negotiate from a position of weakness and leave less room for discounts.

RelatedBSI KRITIS and Cloud Compliance 2026  /  Reshoring in the Mittelstand

What Broadcom Did to VMware

What is the post-Broadcom era? In November 2023, Broadcom completed its acquisition of VMware and radically restructured the portfolio over the months that followed. Perpetual licenses were discontinued, partner programs redesigned, bundles heavily trimmed, and prices sharply increased. The term post-Broadcom era describes the period in which customers can no longer renew their legacy agreements and must instead migrate into a new, subscription-based world. For enterprise customers across DACH, Europe, and globally, 2024 and 2025 were above all a period of uncertainty — 2026 is the year of decisions.

The numbers are well documented. VMware Cloud Foundation, Broadcom’s flagship bundle, packages vSphere, vCenter, vSAN, NSX, the Aria Suite, HCX, and SDDC Manager into a single offering. The list price runs around 350 US dollars per core per year. Customers who previously ran only vSphere now pay for NSX and Aria as well, regardless of whether those modules are actually used. A minimum purchase of 72 cores means that even small environments with three or four hosts appear on the invoice as a full 72-core configuration — even where the physical hardware carries fewer cores.

The financial impact for DACH customers can be summarized in a single formula. Organizations that continue running their VMware estate unchanged pay on average 60 percent more over seven years, measured against the old perpetual-plus-maintenance model. In individual cases, price increases by a factor of eight to fifteen have been reported — particularly among customers who held historically favorable framework agreements or were swept into the VCF bundle with a large number of unused modules.

Source: Broadcom price list and enterprise audit analyses Q1 2026.

Three Response Patterns Emerging Across DACH

The movement among German, Austrian, and Swiss enterprise customers is not a monolithic retreat — it is a three-way split shaped by company size, compliance pressure, and available in-house expertise.

First, the pragmatic path: staying with Broadcom. Large enterprises with deeply integrated VMware estates, existing enterprise agreements, and regulatory requirements for long-term support commitments are remaining with VMware — but negotiating harder. The focus is on choosing the right bundle, auditing every module in the VCF package, and avoiding over-licensing caused by the minimum-purchase rule. Organizations taking this route frequently bring in specialized license advisory firms, because the negotiation dynamics with Broadcom differ markedly from the pre-acquisition era.

Second, the partial migration path. Here, the core of the productive environment stays on VMware for now, while new workloads, development environments, and less critical systems move to alternatives. This progressively reduces the Broadcom cost base without requiring an immediate rebuild of production infrastructure. Proxmox VE is a natural fit for smaller sandbox clusters, Nutanix AHV for stable production workloads, and Azure Stack HCI for stacks already running heavily Microsoft.

Third, full migration. A number of DACH mid-market companies — and some larger organizations with shallower VMware integration — have committed to replacing their entire virtualization layer within two to three years. It is a substantial undertaking that demands change management, training, and infrastructure redesign simultaneously, but specialized integrators now support this path with proven methodologies.

Alternative Stacks Under Enterprise Scrutiny

Choosing an alternative is not a matter of faith — it depends on your infrastructure DNA, existing skills, and the depth of your current management stack. The following overview maps the most relevant candidates for 2026.

Nutanix remains the most pragmatic choice for organizations looking to move off the VCF bundle onto a comparable enterprise stack without fundamentally rearchitecting. The AHV hypervisor replaces VMware ESXi, management depth is on par, and the learning curve for admin teams is manageable. Proxmox is significantly cheaper, but in enterprise support contexts it still lacks an established integrator landscape at every location. Azure Stack HCI makes sense when the organization is already heavily invested in Azure and holds Windows Server licenses in its portfolio.

Migration Economics at a Glance

The cost debate too often fixates on list prices alone — that’s a mistake. A realistic calculation covers five line items: licensing, hardware adjustments, migration project, internal skill development, and ongoing operational overhead. For a typical DACH enterprise environment with 300 cores and 40 hosts, migration projects to Nutanix realistically take twelve to eighteen months; projects to Proxmox frequently land in six to twelve months, depending on internal skill levels.

Broadcom’s 60-percent surcharge scenario is the benchmark against which migration projects justify themselves. Organizations that land on Nutanix typically save between 25 and 40 percent over a five-year period compared to the new VMware model, according to enterprise analyses — but they trade one vendor lock-in for another. Those that land on Proxmox cut licensing costs to a third of Nutanix levels, yet pay the price in internal operational effort and specialized expertise.

One frequently underestimated factor is the timing of the decision. Organizations evaluating alternatives six months before a Broadcom contract renewal are negotiating from a position of weakness with little room for discounts. Those who start eighteen months out can credibly threaten to walk — and achieve significantly better terms, even if the Broadcom renewal ultimately gets signed anyway.

Roadmap for the Next Twelve Months

This roadmap is calibrated to the realities of DACH mid-market and enterprise organizations. Moving faster is possible, but rarely realistic — integrator capacity is noticeably constrained throughout 2026. Moving slower risks signing the first renewal under the new Broadcom terms before alternatives have been genuinely evaluated.

What Gets Overlooked

Three aspects are consistently underestimated in cost comparisons. First, the storage layer. vSAN is included in the VCF bundle, but a migration to a non-VMware stack almost always pulls the storage tier along with it — whether to traditional SAN systems, software-defined solutions, or cloud-based storage services. Those costs frequently run in the same order of magnitude as the virtualization license itself.

Second, the network layer. NSX is included in VCF and is in productive use at many organizations. Anyone migrating must decide whether the existing network setup — traditional firewalls and VLANs — is sufficient, or whether a different software-defined networking solution is required. Cilium, Calico, and commercial alternatives are the usual candidates here.

Third, the disaster recovery stack. VMware SRM and HCX come with the VCF offering; migrations to Nutanix or Proxmox require an entirely different DR approach. Tools like Veeam, Commvault, or Zerto provide the relevant alternatives, but they carry additional costs that must be factored into the overall plan.

Conclusion

The post-Broadcom era is not a storm you can simply weather by keeping your head down. It permanently reshapes the economics of virtualization. Every DACH organization running a VMware landscape needs to find an answer in 2026. That answer might be staying with Broadcom, migrating incrementally, or replacing the platform entirely. What matters is that the answer is chosen deliberately — based on a workload inventory, a cost model, and a realistic timeline. Organizations that react to headlines by migrating often make the same bad decisions as those who reflexively chose to do nothing. A clean seven-year cost calculation and an honest assessment of your own operational maturity are the two instruments that will ultimately tip the scales.

Existing server hardware is another factor in the decision. Many organizations bought VMware-certified hardware stacks with long depreciation cycles — hardware that doesn’t automatically carry over when you migrate. Nutanix traditionally relies on its own appliances, even though software-only options are now available; Proxmox runs on standard x86 hardware with no hardware lock-in. Depreciation realities must be factored into the overall calculation, or the honest amortization math shifts by one to two years — quietly, but consequentially.

Frequently Asked Questions

Does every VMware environment now have to migrate to VCF?

No. Broadcom also offers smaller bundles with vSphere Foundation, vSphere Standard, and vSphere Essential Plus. VCF is the full-stack package, not the only option. What matters is which modules are actively used in production and whether the minimum purchase requirement for a given bundle is economically viable.

Is Proxmox VE truly production-ready for large environments?

For many use cases, yes. Proxmox has made a significant leap in maturity over the past three years — cluster functionality, storage integration, and backup are all at enterprise level. What large environments often lack, however, is the dense partner and integrator network that Nutanix or VMware provides. Organizations with in-house Linux and virtualization expertise can run Proxmox in production confidently; those relying on external expertise should assess the partner landscape in their own DACH region first.

How do you handle the 72-core minimum purchase requirement?

For very small environments, this is economically hard to justify. Consolidating the environment onto fewer but more heavily utilized hosts can improve the math. Alternatively, hyperscaler-based workloads on AWS, Azure, or GCP offer a path that avoids VMware entirely. For many smaller DACH companies, that is the more pragmatic route following Broadcom’s pricing reform.

What role does NSX play in the decision?

NSX is automatically included in the VCF bundle regardless of actual usage. Organizations that actively use NSX benefit from the integrated package. Those that do not use NSX are paying for something they receive no value from — and should evaluate whether a smaller bundle such as VVF or VVS, which does not include NSX, would be sufficient.

When is the right time to make a migration decision?

Ideally 18 months before the next contract renewal. That leaves room for proof-of-concepts, negotiations with Broadcom, and parallel evaluation of alternatives. Organizations that wait until six months out have neither negotiating leverage nor sufficient time for implementation.

More from the MBF Media Network

• Autodesk CIO Appointment on Digital Chiefs
• Cisco SD-WAN Manager KEV Alert on SecurityToday
• EU Digital Omnibus in Trilogue on MyBusinessFuture

Quelle Titelbild: Pexels / Christina Morillo (px:1181335)