Broadcom's cut to its VMware cloud partner list has turned hosted VMware contracts into assets that trade between providers. For customers on the wrong side of that list, 2027 brings a new counterparty, a forced platform upgrade and a renewal, close together. The cheapest time to reopen the platform question is before all three arrive.
On October 8, 11:11 Systems announced it had completed the purchase of "select" enterprise customers from IBM's VMware cloud business. Neither side disclosed terms or a customer count, though 11:11's executives have described the haul as "hundreds." IBM did not answer The Register's questions about the deal, and the same report says some IBM customers are not moving to 11:11 at all.
As a services deal, it barely registers. 11:11 has now bought eight VMware cloud providers, Sungard Availability Services, Faction and Ntirety among them, and Broadcom's infrastructure chief, Ram Velaga, supplied a line for the release calling 11:11 "a partner that reflects our model." As a customer, you should read it differently. The company you signed a private-cloud contract with no longer gets to decide whether it keeps serving you. Its software supplier does.
A licensor now picks your landlord
Since buying VMware in late 2023, Broadcom has rebuilt the program that lets service providers host VMware for their customers. It went invitation-only in November 2025. In January it told a large share of the remaining partners their contracts would not be renewed. Those partners may keep serving existing customers until their terms run out, but they cannot renew or add capacity, and The Register, citing sources, reports that they may no longer run VMware-powered clouds after March 2027. One count it cited earlier this year put the retained US providers at 19, from a field that once ran into the thousands. The European cloud trade group CISPE is fighting the consolidation in court.
IBM stopped selling VMware on IBM Cloud for new workloads in October 2025 and is no longer on Broadcom's list of certified providers. The Register suggests one reason it fell off: IBM also sells Red Hat OpenShift, which now runs virtual machines well enough to compete with VMware head-on.
A departing provider has two ways out: run contracts to term, or sell the book to a provider Broadcom kept. IBM sold. Others, some holding customer contracts that run past the cutoff, will find the same logic hard to resist.
You signed your private-cloud contract with a hosting provider. Whether that provider gets to keep honoring it is now decided by the provider's software supplier.
Three clocks, one year
The change of name on the invoice is the smallest part of this. Brett Diamond, 11:11's chief executive, told The Register that the IBM customers run VMware versions 7 and 8, called them "ripe for migration," and said the plan is to move them to VCF 9. vSphere 7 left general support in October 2025. vSphere 8 is scheduled to follow in October 2027.
Line the dates up. A customer whose provider is exiting gets a new counterparty around March 2027, a major platform upgrade before October 2027, and a renewal priced in a market Broadcom has deliberately thinned. Azure VMware Solution customers have their own version of the squeeze: Microsoft stops selling license-included AVS to new customers on October 31 and retires it on August 30, 2027, after which existing customers must buy a portable VCF subscription from Broadcom or leave. Google Cloud VMware Engine made the equivalent switch a year ago.
The routes differ. The destination doesn't. By late 2027, almost every hosted VMware customer will be paying Broadcom directly, or through a provider Broadcom picked, to run VCF 9.
Figure 1
Where you sit | What changes | The clock | The decision you actually face |
|---|---|---|---|
Provider retained by Broadcom | Little at first; renewals get priced in a thinner market | Your renewal date | Whether the renewal price still justifies staying |
Provider exiting, book sold (the IBM case) | New counterparty; likely VCF 9 move on its schedule | Transfer now; vSphere 8 support ends October 2027 | Accept the assignment, or use the transition to re-price or move |
Provider exiting, running to term | Service continues until the contract ends, then stops | Your contract end; reported March 2027 cutoff | Choose the next host or platform before wind-down erodes support |
Azure VMware Solution, license included | VCF bought separately from Broadcom (BYOL) | New sales end Oct. 31, 2026; retired Aug. 30, 2027 | Whether VMware on a hyperscaler beats native compute once the license is a separate bill |
Google Cloud VMware Engine | Portable-license only since November 2025 | Your Broadcom subscription term | The same question, with the license cost already visible |
Different routes, one destination: VCF 9, licensed by Broadcom. Dates from Microsoft and Google Cloud notices, The Register's reporting and published vSphere lifecycle dates. Illustrative; your position depends on the contract you hold.
The migration you were avoiding is already on the calendar
Plenty of enterprises stayed on hosted VMware through the Broadcom price shock for one reason: leaving meant a migration, with new tooling, retrained operators and a cutover the business would notice. In 2024 that was a defensible call.
For customers in IBM's position, staying has stopped being low-effort. A version upgrade to VCF 9 at a new provider, possibly on new hardware, with new runbooks and a new support desk, is a migration in everything but name. It is smaller than a move to OpenShift Virtualization, Nutanix or native hyperscaler compute, and it does keep the hypervisor. But the gap between staying and leaving has shrunk, and the fixed cost of moving gets paid either way.
Diamond also told The Register that "no other hypervisor can handle the mid-to-large enterprise." That is a reasonable thing for a VMware hosting company to believe. Some of your workloads will prove him right: the ones with deep dependencies on VMware networking and storage features, or vendor support statements that name vSphere. Many won't. Whether yours do is now worth finding out, because you're paying for a move regardless.
Leverage belongs to customers who could leave
Whoever buys a book of hosted VMware contracts is paying for revenue that exists only if customers stay. That makes the first renewal after a transfer one of the rare moments a hosted customer holds real leverage. The acquirer needs retention to justify the purchase. A customer with a credibly priced alternative can ask for things a customer without one cannot. A customer who has priced nothing is simply part of the inventory.
Pull these from the hosting contract this month
Assignment. Can the provider assign your contract without consent, and does an assignment give you a right to terminate?
The provider's own end date. When does its Broadcom agreement expire, and does your contract outlive it?
Upgrade obligations. Who schedules and pays for the move to VCF 9, and do service levels hold during it?
Price pass-through. Can Broadcom's price changes flow through to you at renewal, and on how much notice?
Exit terms. VM and data export formats, egress charges, and how much transition help the provider owes you on the way out.
What this means for CIOs and infrastructure leaders
Ask your provider one question, in writing: are you a retained Broadcom partner, and through what date does your VMware agreement let you serve us? A provider winding down has little reason to volunteer it.
Then put two prices side by side for every hosted VMware estate. One is the VCF 9 path with the provider you will actually have, not the one you signed with. The other is a credible alternative for the workloads easiest to move. You don't need to leave to need the second number. You need it to make the first one honest.
Treat any transfer notice as a decision date rather than paperwork. A customer who accepts an assignment by doing nothing starts 2027 with a counterparty it didn't choose, an upgrade it didn't schedule and a renewal against a supplier with few rivals. IBM's customers found out their contracts could be sold. The ones who come out ahead will be the ones who already know what it costs to walk.
Sources and notes. 11:11 Systems release of October 8, 2026, as published by VMblog (October 9): completed acquisition of "select IBM VMware Cloud Service Provider enterprise customers"; terms undisclosed; eighth VMware CSP acquisition; Broadcom's Ram Velaga quoted. Simon Sharwood, The Register, "IBM offloads 'hundreds' of its cloudy VMware customers" (October 8, 2026): IBM did not respond; some customers reportedly not moving; Brett Diamond on VMware versions 7 and 8, VCF 9 and other hypervisors; departing partners' reported March 2027 cutoff; the Red Hat OpenShift explanation; CISPE's EU antitrust case. Fierce Network (October 9) and Channel Dive (October 12) on the "hundreds" figure and 11:11's acquisition history. CloudTech/Cloud Computing News (October 9) on IBM's October 2025 sales halt and Broadcom's November 2025 invitation-only program. The Register (January 31, 2026) on Broadcom's VCSP non-renewal notices and the reported count of 19 retained US providers. Petri (August 21, 2026), citing Microsoft's Azure update: license-included AVS sales end October 31, 2026, service retired August 30, 2027. Google Cloud blog (updated October 9, 2025): VCF on GCVE moves to Broadcom-purchased portable subscriptions from November 1, 2025. vSphere 7 end of general support October 2, 2025, and vSphere 8 October 11, 2027, per Broadcom lifecycle dates as reported by third-party trackers. The March 2027 cutoff and the 19-provider count rest on The Register's sources, not a Broadcom statement; the customer count is 11:11's description, not a disclosed figure. Journalism, not procurement or legal advice. Corrections welcome.
