RACK TRAIL
Solutions
VMware MigrationOpenStack at scaleProxmox at scalePrivate AICloud Cost OptimizationManaged Private CloudLarge Scale MigrationBig Data InfrastructureConfidential Computing InfrastructureCephKubernetes WorkloadsCloud Infrastructure for Startups
Why RacktrailGroundworkAbout Talk to an Engineer
14 minutes

Your VMware host may not be allowed to run VMware after March 2027

Broadcom has cut most of its VMware cloud partners, and the ones it dropped may not run VMware-powered clouds after March 2027. If your VMs live on someone else’s VMware, here’s how to tell whether you’re affected, the three options you have, and a plan that finishes in time.

If your workloads run on someone else’s VMware (a local hosting company, an MSP, a telco, IBM or Azure), your platform has a deadline you may never have been told about.

Since November 2025, Broadcom has worked with an invite-only group of VMware cloud partners. The providers it dropped lost the right to resell VMware, stopped getting contract renewals in January, and may not run VMware-powered clouds after March 2027. On 8 October, IBM handed “hundreds” of its VMware cloud customers to 11:11 Systems. More handovers like that are likely.

160days until the end of March 2027, after which providers Broadcom dropped may no longer run VMware-powered clouds.Counted from today. Your provider’s contract sets your exact date.

That is enough time to choose calmly. It is not enough if you start in February.

Short answer

Since November 2025, Broadcom has run its VMware Cloud Service Provider (VCSP) programme as invite-only. Providers it didn’t retain can serve existing customers only until their current contracts end, and may not run VMware-powered clouds after March 2027. Their customers must follow them to a retained partner, license VMware themselves, or migrate.

Key takeaways

  • Broadcom moved its VMware cloud partners to an invite-only model in November 2025. Providers that weren’t invited got non-renewal notices on 26 January 2026.
  • Dropped providers may not run VMware-powered clouds after March 2027. Some providers cite 31 March; your contract decides the exact date.
  • Retained providers face a deadline too. vSphere 8, vSAN 8, NSX 4 and VCF 5.2 reach end of service on 11 October 2027, so expect a VCF 9 upgrade and new terms.
  • Hyperscaler VMware is changing as well. Azure stops selling licence-included Azure VMware Solution on 31 October 2026, and existing customers must bring their own VCF licence by August 2027.
  • You have three options: follow your provider to a retained partner, license VCF yourself, or migrate off VMware. Each takes time, so decide this quarter.
  • Start by asking your provider seven questions in writing. Their answers tell you which option you’re actually in.

What changed in Broadcom’s VMware cloud partner programme

Broadcom rebuilt VMware’s cloud partner programme in two steps. First it closed the programme to all but invited providers, then it stopped renewing the rest. The notices went to providers, not customers, so many customers still don’t know their provider was dropped.

Hosted VMware timeline, October 2025 to October 2027 31 OCT 2025Old partner programme closesVCSP goes invite-only; dropped providers lose resale rights 26 JAN 2026Non-renewal notices sentDropped providers can no longer renew commitment contracts 08 OCT 2026IBM hands customers to 11:11 SystemsHundreds of VCF customers get a new provider PUBLISHED 22 OCT 2026 31 OCT 2026Azure stops selling licence-included AVSAzure VMware Solution moves to bring-your-own VCF licence 31 MAR 2027Dropped providers’ VMware cutoffThey may no longer run VMware-powered clouds 30 AUG 2027Azure VMware customers must be on BYOLLicence-included AVS customers must have moved 11 OCT 2027vSphere 8 and VCF 5.2 end of serviceNo patches or support; move to VCF 9 or off VMware
The dates that decide your options. The March 2027 cutoff is reported, not published by Broadcom; check your contract.
  • October 2025. The VMware Cloud Service Provider (VCSP) programme closed and became invite-only from 1 November. Dropped providers lost the right to resell VMware, and the white-label route was retired in the European Economic Area (SDxCentral).
  • 26 January 2026. Non-renewal notices went out. Dropped providers can keep serving existing customers until their current commitment contract ends, but they can’t renew it (The Register).
  • 8 October 2026. IBM, once one of VMware’s biggest partners, sold contracts for hundreds of VMware Cloud Foundation customers to 11:11 Systems, its eighth acquisition of a VMware provider. 11:11’s CEO, Brett Diamond, called the customers, who run VCF 7 and 8, “ripe for migration” (he means to VCF 9) (The Register). Expect more sales like this: dropped providers can sell their contracts to a wholesaler or a retained partner.
  • March 2027. Dropped providers may not run VMware-powered clouds after this point.
  • 11 October 2027. vSphere 8, vSAN 8, NSX 4 and VCF 5.2 reach end of service, with no patches or support after it (Broadcom). Every provider, retained or not, has to move you to VCF 9 or off VMware before then.

Broadcom hasn’t said how many providers it kept. It told The Register it is “going deeper with the VCSPs who have demonstrated commitment” to VMware-based cloud services. Reports describe hundreds of providers dropped in Europe alone, and the European cloud trade body CISPE has taken the issue to EU competition authorities (The Register).

Is your hosted VMware affected?

You’re exposed if VMware runs underneath a service you rent, even if you never bought a VMware licence yourself. Find your row.

ExposureHow you use VMwareWhat to check
High

Hosted private cloud, VPS, backup or DR from a local provider or MSP that wasn’t retained

Whether your provider is still a Broadcom cloud partner after March 2027

Medium

Hosted VMware from a provider that was retained

When they move you to VCF 9, and whether your price or bundle changes

Medium

Your contract was sold to another provider, as with IBM to 11:11

The new provider’s terms, data location and support model

Medium

Azure VMware Solution

Buying VCF from Broadcom and moving to bring-your-own-licence by August 2027

Low

VMware on your own servers, with your own licences

Your renewal, and vSphere 8’s end of service in October 2027

Not sure VMware is underneath?

Clues include a VMware Cloud Director portal, workloads grouped into “vApps”, VMware Tools installed in your VMs, or .vmdk disks in your exports. Or ask your provider directly.

Your three options before March 2027

Every affected customer ends up in one of three places. The worst outcome is landing in one by default because the deadline arrived first.

Option A

Follow your provider

Your contract moves to a retained partner, or your provider becomes a reseller under one.

You keep
The same tools, portal and VM formats
What changes
A new counterparty and contract. Possibly a new country for your data, a VCF 9 upgrade and a different bundle or price
Main risk
Fewer providers to choose from at your next renewal
Time to land
Weeks, if the new provider is ready

Option B

License VCF yourself

You buy VMware Cloud Foundation from Broadcom and run it on your own or colocated hardware, or on a hyperscaler.

You keep
Full control of the VMware licence
What changes
A full VCF subscription (Broadcom sells bundles, not parts), hardware, and people to run it
Main risk
Committing to the bundle you were trying to avoid
Time to land
Months: procurement, hardware, deployment

Option C

Migrate off VMware

You move VMs to an open platform (Proxmox VE, OpenStack or KubeVirt) on your hardware, a provider’s, or managed for you.

You keep
Control of the platform, standard APIs and a documented exit
What changes
VM formats and drivers, your network design, and your team’s runbooks
Main risk
A rushed migration if you start late
Time to land
Weeks to months, depending on VM count and complexity

Staying can be right

If you depend on VMware-specific tooling (vCloud Director automation, SRM-based DR, certified appliances) and a retained provider serves your country, following your provider may be the cheapest path for now. Go in with your eyes open about the next renewal.

The options combine

Some teams move to a retained provider as a bridge, then migrate over 12 to 18 months on their own schedule. That’s reasonable, as long as the bridge contract doesn’t lock you in past the date you plan to leave.

If you’re leaning towards migrating, Leaving VMware: what to settle before you choose where to go covers the decisions to make first, and Proxmox vs OpenStack vs VMware in 2026 compares the main platforms.

Your VMware renewal is a decision, not an invoice.Even when the renewal is your provider’s.

Questions to ask your VMware hosting provider

Ask these in writing. A provider that answers clearly and quickly is a good sign whichever option you choose.

  1. Are you a retained Broadcom cloud partner after March 2027, or are you winding down your VMware service?If retained, at which tier, and directly or through another partner?
  2. If you’re winding down, what happens to our contract?Who takes it over, on what terms, and when will we be told?
  3. Where will our data physically sit after any transfer?Which country, which data centre, and which legal entity operates it?
  4. Which VMware version are we on, and when do we move to VCF 9?vSphere 8 support ends on 11 October 2027. Who pays for the upgrade, and how much disruption will it cause?
  5. Will our price, bundle or minimum commitment change at transfer or renewal?Ask for the new terms before you agree to any transfer.
  6. How do we get our VMs out?In what format (OVF, VMDK), how long does an export take, and are backups and network configuration included?
  7. What does our contract say about notice, termination and continuity of service?Specifically, what happens if you can no longer run VMware?

Save the replies. If your provider later sells your contract, these answers are your baseline.

How to migrate off hosted VMware before March 2027

A full enterprise VMware exit takes three years or more, according to Gartner. A hosted footprint is usually smaller: tens or hundreds of VMs, with the hardware already someone else’s problem. For that, about 20 weeks is realistic if you start now, work in waves and leave buffer for year-end change freezes.

A 20-week plan that finishes before the March 2027 cutoff NOVDECJANFEBMAR Inventory Choose the target Build and pilot Migrate in waves Close outbuffer START NOW31 MAR 2027 CUTOFF
About 20 weeks, worked backwards from the cutoff, with the last two weeks kept free.
  1. Inventory (November, 2 weeks). List every VM with its OS, size, disks, IP addresses, dependencies and backup policy. Ask your provider for an export path and test it on one VM.
  2. Choose the target (November, 2 weeks). Pick the platform (Proxmox VE for straightforward virtualization, OpenStack for multi-tenant self-service) and where it runs: your hardware, colocation, or a provider in the country your data must stay in.
  3. Build and pilot (December, 4 weeks). Set up networking (VLANs, IP plan, VPN or interconnect), storage and backups. Migrate 3 to 5 low-risk VMs. Fix Windows VirtIO drivers, VMware Tools removal and MAC or IP changes here, not in production.
  4. Migrate in waves (January to February, 8 to 10 weeks). Group VMs by application and dependency. Replicate disks continuously at block level, then do a per-VM cutover in minutes. Keep each source VM bootable for rollback until its owner signs off.
  5. Close out (March, 2 to 4 weeks). Run the final waves, decommission, and end the old contract on its notice terms. Keep the last two weeks as buffer.

What slows migrations down

Rarely the copying. It’s undocumented dependencies, licences tied to MAC addresses or hardware IDs, and waiting for approvals. Start those conversations in the first two weeks.

If you are the provider: options for MSPs and regional clouds

For hosting companies, MSPs, ISPs and regional clouds that weren’t retained, the question isn’t technical. It’s who keeps the customer relationship after March.

Path 1

Sell your contracts

A wholesaler or retained partner buys them, as 11:11 did with IBM’s.

Who keeps the customerThey do

Path 2

Resell through a retained partner

Where the white-label route still exists (it’s gone in the European Economic Area), you resell another provider’s VMware platform.

Who keeps the customerYou do, on their platform and margins

Path 3

Build your own open platform

You stand up OpenStack, CloudStack or Proxmox and migrate your customers onto it.

Who keeps the customerYou do, on infrastructure you control

The third path takes the most work, but it’s the only one where your platform isn’t someone else’s to revoke. If you choose it, build the landing platform first, then move customers in waves: start with your simplest tenants and keep the VMware estate running until each one signs off.

Whichever platform you build on, check that it doesn’t recreate the lock-in you’re leaving. Seven ways an “open source” cloud still locks you in lists what to test for.

Five months is tight but workable if you start now. A provider’s VMware estate is usually larger and more mixed than one customer’s, so delays can’t be absorbed at the end.

Frequently asked questions

What is the VMware March 2027 deadline?

It’s the point after which cloud providers that Broadcom didn’t keep in its invite-only VMware partner programme may no longer run VMware-powered clouds. Their customers have to move to a retained provider, license VMware themselves, or migrate to another platform.

Does this affect VMware I run on my own servers?

Not directly. The March 2027 cutoff applies to cloud providers Broadcom didn’t retain. On your own servers, your deadlines are your licence renewal and vSphere 8’s end of service on 11 October 2027.

Is 31 March 2027 the exact date?

Reports say dropped providers may not run VMware-powered clouds after March 2027, and some providers, such as iomart, cite 31 March. Your provider’s contract with Broadcom, and your contract with your provider, set the exact date for you. Ask for it in writing.

My provider says nothing will change. Should I believe them?

Ask whether they’re a retained partner, at which tier and until when. A retained provider can answer in one line. “We’re working on it” usually means they don’t know yet.

Can we migrate without downtime?

Plan for minutes of downtime per VM, not zero. With continuous block-level replication, each VM gets a per-VM cutover in minutes, and the source stays bootable for rollback until you sign off.

Is moving to a retained VMware provider a mistake?

No. It can be the right call, especially as a bridge. Check where your data will sit, what the next renewal will cost, and that the contract lets you leave when you’re ready.

We’re in Nepal, India or Southeast Asia. Does this apply to us?

Yes. The partner changes are global, and fewer retained providers in a country can mean your data moves abroad on transfer. If residency rules apply to you, ask question 3 first. In Nepal, many teams land on Proxmox; Proxmox was the easy choice. Is it still the right one? covers what to check.


Sources

Your VMware renewal is a decision, not an invoice.

Tell us what's running and when your renewal lands. An engineer will map the estate and give you a costed plan to set against your renewal quote.

GPUs where your data is allowed to live.

Tell us the workload, the GPUs you need and the region it has to stay in. An engineer will tell you honestly what to build, rent or skip.

Tell us what needs to run.

Send us the workload, the constraints, and the region it has to live in. An engineer — not a sales rep — will tell you honestly whether we're the right fit.