T-Mobile moving tens of thousands of virtual machines off VMware amid lawsuit
Let's be clear about what's happening here. T-Mobile isn't just suing Broadcom over a contract dispute. It's executing a strategic divorce from VMware that has been building since Broadcom closed its $69 billion acquisition — and the lawsuit is merely the alimony hearing.
The numbers are staggering: 303,140 CPU cores. Tens of thousands of virtual machines. Over 1,000 applications tangled in the VMware stack. This isn't a departmental pilot project; it's the nervous system of a major wireless carrier. And T-Mobile is ripping it out root and branch, not because it wants to, but because Broadcom left it no viable alternative.
The perpetual license lie
Perpetual licenses were supposed to mean something. You pay once, you own the right to run the software forever. Support renewals are optional — a choice, not a shakedown. When T-Mobile bought its VMware licenses in 2023, it secured two years of support with a contractual option for a third. That option was worth $5.28 million. Pocket change for Broadcom. Principle and precedent for everyone else.
Then Broadcom did what Broadcom does: rewrote the rules retroactively. Ended perpetual licenses. Forced subscription bundles. Told T-Mobile the renewal option it paid for no longer exists because Broadcom decided it doesn't. The email is almost comic in its brazenness: "Broadcom announced end of availability of all perpetual products, which includes Stated Out Year Renewals for perpetual support." Translation: we changed our mind, your contract be damned.
A pattern, not an anomaly
This is the Broadcom playbook. We saw it with CA Technologies. We saw it with Symantec. Acquire a franchise, jack prices, kill licensing models customers built their infrastructure around, dare them to litigate or migrate. Most pay up because migration is a nightmare. T-Mobile is rare: it's doing both.
The injunction T-Mobile won — support through August 2026 for the contracted price plus a $500,000 bond — is a tactical victory. But it's also a countdown clock. Every day until August 3, 2026 is a day T-Mobile's engineers are burning to untangle 1,000+ applications from vSphere, vSAN, NSX, and the rest of the VMware taxonomy. That's not IT work. That's archaeological excavation with a deadline.
The real cost isn't the license fee
Industry analysts love to model TCO around license costs. They miss the real expense: engineering time, risk, opportunity cost. T-Mobile didn't file this suit to save $5.28 million. It filed to buy time — time to finish a migration that Broadcom's unilateral changes made inevitable. The lawsuit is a holding action. The migration is the strategy.
And make no mistake: every enterprise running VMware is watching. The perpetual license model that built VMware's dominance is dead. Broadcom killed it. The only question is whether the courts will let Broadcom kill the contracts that went with it.
No good options, only less bad ones
T-Mobile's migration destination matters less than the fact that migration is happening at all. OpenStack. Nutanix. Red Hat OpenShift. Bare metal with Kubernetes. Public cloud repatriation. Each path carries its own vendor lock-in, its own operational complexity. But they share one virtue: they're not Broadcom's VMware.
That's the industry's new baseline. Not "which platform is best?" but "which vendor won't unilaterally rewrite my contract after I've architected my business around it?"
A bellwether for the subscription squeeze
The Register broke this story because it's the first major enterprise to publicly litigate Broadcom's bait-and-switch. It won't be the last. CIOs everywhere are staring at renewal notices with triple-digit percentage increases and bundle requirements that force them to pay for products they don't use. The perpetual license was a hedge against exactly this. Broadcom just torched the hedge.
T-Mobile's complaint seeks a declaration that it was entitled to renew support. That's the legal ask. The practical ask is simpler: honor the deal you inherited when you bought the company. Broadcom didn't buy VMware's assets without its liabilities. Contracts are liabilities.
The migration tax
There's a term for what T-Mobile is paying: the migration tax. Every enterprise on VMware now owes it. Some will pay in lawsuit fees. Some in engineering years. Some in subscription ransoms. But the tax is universal, and Broadcom levied it.
T-Mobile is just the first to itemize the bill in open court. The 303,140 cores aren't moving because T-Mobile wants a modern stack. They're moving because the vendor broke the social contract that makes enterprise software viable: we build, you run, the terms don't change because our quarterly targets shifted.
Watch the docket. Watch the migration timeline. And if you're running VMware on perpetual licenses with renewal options, start counting your cores. The clock is ticking.