Table of contents
For many cloud providers that Broadcom did not keep in its VMware partner program, VCSP contracts expire on March 31, 2027. That is a licensing deadline. It does not dictate which platform you run next. A second milestone follows on October 11, 2027, when vSphere 8 reaches end of general support. Your own contract end date and the transition route you choose determine what you need to do, and when.
In short
- March 31, 2027 ends many VCSP contracts; October 11, 2027 ends general support for vSphere 8. Plan for both.
- Three routes remain: stay on VMware through a retained Pinnacle partner, move tenants onto a partner’s VCF cloud, or leave VMware for your own KVM-based cloud.
- On every route, disaster recovery is the cheapest and lowest-risk workload to move first.
The VMware calendar for cloud providers
| Date | What changes | Who it affects |
|---|---|---|
| March 31, 2027 | VCSP contracts of many non-renewed providers expire | Providers outside the retained partner program |
| October 11, 2027 | End of general support for vSphere 8 (ESXi, vCenter, vSAN 8.x) and VCF 5.x | Every vSphere 8 estate, yours and your tenants’ |
| October 31, 2028 | EEA only: latest end of Extended Support in active vSphere Standard 8 and Enterprise Plus 8 subscriptions | EEA customers on those two editions |
| Workload placement | The ongoing practice of deciding where each workload should run | The whole portfolio |
What happens in March 2027
Broadcom has cut its VMware Cloud Service Provider (VCSP) program down to an invite-only group of partners that build their services on VMware Cloud Foundation (VCF). For many of the providers it did not invite back, VCSP contracts expire on March 31, 2027. In the European Economic Area, Broadcom told affected partners in January 2026 that it would not renew their VCSP contracts after January 26, 2026. They can keep serving existing customers until their current commitment term ends, and Broadcom encourages them to work with retained partners on the transition. The same non-renewal notice confirms that Broadcom has sunset the White Label model, which let smaller providers license VMware through a larger partner.
The market is already consolidating around the partners that remain. IBM sold contracts for hundreds of its VMware cloud customers to 11:11 Systems, and Leaseweb took over ITQ’s base of 51 white-label providers, about 35,000 cores, which move onto Leaseweb’s VCF platform and keep offering their services under its Pinnacle partner status. For background on prices and licensing since the acquisition, see how VMware pricing and licensing changed after the Broadcom deal.
The second deadline: October 11, 2027
Broadcom lists October 11, 2027 as the end of general support for vSphere 8, including ESXi, vCenter and vSAN 8.x. The software does not switch off, but you should plan an upgrade, an alternative platform or an applicable support arrangement before then.
One regional exception arrived in November 2026. In the EEA, vSphere Standard 8 and vSphere Enterprise Plus 8 stay on sale until October 31, 2027, and active subscriptions include Extended Support until the subscription ends or October 31, 2028, whichever comes first. As The Register notes, VCF 5.x, which is built on vSphere 8, keeps the October 11, 2027 date, so the extension covers those two editions only.
Whichever version you run, VCF is licensed per core and Broadcom publishes no rate card, so the quote from your partner is the commercial commitment that matters. The next article in this series shows how the per-core math works for a DR site. For scale, Gartner reports VMware software renewal increases averaging three to four times the last price paid to VMware.
Three routes after March 2027
| Route | What you do | What you still pay VMware for | Where Hystax Platform fits |
|---|---|---|---|
| 1. Stay on VMware through a retained Pinnacle partner | License VCF through the partner, on the multi-tier or wholesale terms it offers; tenants stay where they are | VCF cores on every vSphere host, DR hosts included | Move the DR site to any KVM-based platform now |
| 2. Move onto a Pinnacle partner’s VCF cloud | Migrate tenants onto the partner’s platform and keep the customer relationship, as ITQ’s white-label providers are doing with Leaseweb | The partner’s VCF service, with the margin shared | Keep DR outside the VCF estate, on capacity you control |
| 3. Leave VMware | Run your own KVM-based cloud: OpenStack, Apache CloudStack, OpenShift Virtualization or another KVM platform | Nothing | Migrate tenants into your cloud, then protect them in a separate recovery failure domain |
Check what a partner can actually offer before you commit to route 1: with the White Label model gone, terms differ by partner and region. Many providers will still take route 1 first because it changes the least. That is a sound choice for March, as long as it isn’t treated as the end of the decision. Every DR host stays in the VCF core count, and vSphere 8 general support ends six months later.
Where DR fits on every route
Disaster recovery is the only workload that occupies VMware capacity without serving tenants day to day, making it the cheapest place to start. On route 1, moving it to a KVM-based platform removes the DR hosts’ cores from your VCF subscription at the next renewal or reduction point. On route 2, it keeps your recovery service, and its margin, on capacity you control. Route 3 gives you a tested landing zone before production moves. On all three, every DR test boots tenant machines on the new platform, so each test doubles as a migration rehearsal. Hystax Disaster Recovery runs on any KVM-based platform, alongside the Veeam backups you already run.
Three numbers to know before March
- Your contract end date. It sets your real deadline, not the headline date. Ask for the renewal quote and its minimums at the same time.
- How many vSphere hosts run DR rather than production. Those hosts are the cheapest place to start leaving VMware; the next article in this series works through the math for a 30-host provider.
- Which tenants could move first. Small, well-documented tenants make the best first migration and DR test.
Frequently asked questions
Can a non-renewed VCSP keep running VMware after March 2027?
Not on its own VCSP contract once that contract ends. Broadcom lets non-renewing partners serve existing customers until the end of their current commitment term, then points them to retained partners. Running a VMware-powered cloud beyond that date means working with a retained partner, as on routes 1 and 2.
Will VMs stop running after October 11, 2027?
No. vSphere 8 keeps running after its end of general support; what ends is Broadcom's general support. Plan an upgrade, a move to another platform or an applicable support arrangement before then.
Do I have to move production off VMware to cut costs?
No. On route 1, moving only the DR site to a KVM-based platform removes the DR hosts' cores from your VCF subscription at the next renewal or reduction point, while production stays where it is. The next article in this series works through an example of when that pays for itself.
Next step
Email Edwin Kuss, Director of Global Sales, at [email protected] to set up a VMware cost and DR review. Include your contract end date and host count, and we'll map your route and your DR options.
Or join the Hystax Global Partner Program webinar on November 17, 2026 (register on Livestorm). It covers the three routes, the Veeam architecture and partner terms.
VMware 2027 for cloud providers: the series
- Part 1: March 2027 is a licensing deadline, not a platform decision (you are here)
- Part 2: Keep VMware, lose the dependency: move DR first
- Part 3: Veeam keeps the backups, Hystax runs the DR (coming soon)
Subscribe to the Hystax blog to get the next parts as they are published.
Stay licensed whichever way suits you, take DR off VMware now, and move production when you're ready.
VMware, vSphere, vSAN and VMware Cloud Foundation are trademarks of Broadcom Inc. or its subsidiaries. Hystax is not affiliated with or endorsed by Broadcom.