Broadcom doesn’t call it a termination. They call it a simplification.

On January 26, 2026, non-renewal notices went out to VMware Cloud Service Provider partners across the US and Europe. The Advantage Partner Program for VCSPs: closed. The White Label model for the European Economic Area: ended. Hundreds of cloud service providers — some with ten or fifteen years of VMware partnership history — received the same form email telling them they had until March 31 to close any open opportunities.

Broadcom retained an invite-only group of authorized VCSPs. Reportedly nineteen US providers out of thousands.

Eight days from now, the rest are out.

This is getting covered as a channel story. It’s not. It’s an architecture story, and if you’re still treating it like a vendor relationship problem, you are going to be blindsided on April 1.

What Actually Happened

The VCSP program was the delivery mechanism for enterprise-grade VMware infrastructure for companies that couldn’t or wouldn’t build it themselves. Mid-market customers in particular relied on VCSPs to access vSphere, vSAN, and NSX through a managed service wrapper — enterprise performance without the capital expense.

Broadcom’s $69 billion acquisition of VMware closed in October 2023. In the two years since, the company has systematically restructured the commercial model: prices reportedly up tenfold for some segments, payment demanded upfront, products bundled regardless of customer need, and minimum commitments set against potential consumption rather than actual usage.

The VCSP purge is the final move. Consolidate from thousands of resellers down to nineteen authorized providers in the US. Force volume through fewer channels. Extract more margin per transaction. This is the VMware partner purge taken to its logical conclusion.

CISPE — the Cloud Infrastructure Service Providers of Europe, representing nearly 50 cloud providers, filed a formal complaint with the European Commission last week, calling the move a “death sentence” for smaller cloud businesses and alleging illegal abuse of market position. The EC complaint asks for interim measures that would immediately suspend the VCSP termination and readmit affected partners. Broadcom called the allegations a misrepresentation.

The EC will take months. March 31 is in eight days.

The Math Nobody’s Running

Here’s what I want you to actually calculate, not read abstractly.

If your customers are running workloads through a terminated VCSP, those customers have a service continuity problem. Non-renewing VCSPs can service existing contracts through their current commitment term. They cannot take new customers. They cannot expand existing deployments beyond what was contracted before the cutoff.

That means no new seats. No new workloads. No expansion. Your customer’s VMware infrastructure through that VCSP is frozen in amber until their contract expires — and then it’s gone.

Some of those VCSP contracts expire in 90 days. Some in six months. Some in eighteen months. But they all expire. And when they do, that customer needs a new home for their workloads.

You have three paths: move them to one of the nineteen remaining authorized US VCSPs (expect higher prices — they’re now operating with dramatically reduced competition), migrate them to an alternative platform (Nutanix, Azure Stack HCI, Proxmox) — the data sovereignty conversation may factor into that choice, or help them bring VMware in-house under a direct Broadcom enterprise agreement (also more expensive than it used to be).

None of these are quick. None of them are free. And all of them are decisions that should be made now, not when the contract clock runs out.

Why Waiting Is the Worst Strategy

Partners who’ve been watching this unfold are falling into a predictable trap: treating the March 31 date as a milestone for the terminated VCSP, not as a planning trigger for themselves.

The VCSP exits on March 31. The customer contracts they hold don’t all expire on March 31. So there’s an apparent lull — existing services keep running, the pain isn’t immediate, and the urgency drains out of the conversation.

That lull is the window to have architecture conversations with your customers. Not quarterly. Now.

Six months from now, when a contract is ninety days from expiration, you’re in reactive mode. You’re migrating under time pressure. You’re losing the conversation to whoever gets to the customer first with a migration offer. That’s probably one of the nineteen remaining authorized VCSPs, or a hyperscaler with an Azure Stack pitch ready.

I wrote about where displaced VMware partners went after the original purge last year. The pattern was consistent: partners who treated it as a vendor problem lost customers to partners who treated it as a positioning opportunity. The same thing is about to happen to a second wave of affected customers.

What the EU Complaint Actually Means (For You)

Nothing in the near term. Read the timeline honestly.

The European Commission’s complaint process is months long, possibly longer. Even if CISPE wins interim measures — and that’s a meaningful if — the process doesn’t move fast enough to matter for March 31. Broadcom’s spokesperson has already pushed back on the CISPE characterization. They’re not pausing.

Ars Technica’s coverage noted that CISPE’s membership includes hyperscalers Amazon Web Services and Microsoft as “adherent members.” That’s relevant context: the complaint is being made in part by the companies that stand to inherit workloads when European VCSPs lose their VMware authorization. That doesn’t make the complaint wrong, but it’s worth noting where the incentives sit.

The EU story is a long-term story. Your customer migration problem is an eight-day story.

The Single Directive

Audit your customer base this week. Find every customer running VMware infrastructure through a service provider. Call that provider and confirm their VCSP status. If they’re terminated, map the contract expiration dates. Then start the architecture conversation now — before the contract clock starts ticking visibly.

Broadcom didn’t acquire VMware. They acquired the customer relationships and the switching costs. It’s the same PE playbook applied at a different scale. The question you have to answer is whether you’re the partner helping your customers navigate that, or whether you’re the one who finds out about the migration conversation after someone else already had it.

The window closes March 31. Your customers’ windows close later. Use the gap.