T-Mobile moving tens of thousands of virtual machines off VMware amid lawsuit

T-Mobile filed suit in New York seeking a court ruling that Broadcom must continue supporting VMware perpetual licenses, citing tens of thousands of virtual machines running on ~303,140 CPU cores. While T-Mobile is migrating off VMware, it says moving more than 1,000 applications is time-consuming and technically challenging. The dispute is likely to create near-term uncertainty for VMware licensing continuity and ongoing IT cost/systems planning.

Analysis

This matters less as a one-customer dispute and more as a test case for how much control Broadcom really has over the VMware installed base. If the court narrows or invalidates the support obligation, it weakens the monetization path for every large enterprise still sitting on perpetual entitlements, and that should translate into lower confidence in the software segment’s durability and a higher discount rate on the multiple. The real issue is not damages; it is whether Broadcom can keep converting legacy licenses into a managed migration funnel without triggering broader customer resistance.

The near-term winners are enterprises with large VMware estates and the ecosystem that monetizes migration friction: systems integrators, automation vendors, and alternative platforms such as Nutanix and Red Hat/OpenShift. The catch is that a legal fight can also slow migration decisions, which paradoxically keeps customers trapped on VMware longer and delays share gains for competitors. That makes the first-order revenue impact ambiguous, but the second-order effect is a trust penalty: once CIOs think perpetual rights are unstable, they start designing Broadcom out of future infrastructure plans even if they cannot move immediately.

Catalysts are legal, not operational: motions to dismiss, summary judgment, or a settlement that clarifies support obligations over the next 1-3 months. The bearish thesis is falsified if Broadcom wins quickly on contract language or if management can show the dispute is immaterial to VMware cash flow on the next earnings call; absent that, the litigation adds a persistent multiple overhang over 6-18 months. The contrarian point is that a prolonged case may actually preserve near-term maintenance revenue by slowing migration, so this is best traded around event dates rather than as a structural short on the core company.

Key Decisions for Investors

• Use AVGO put spreads into the next court milestone or earnings print rather than an outright short; the cleaner trade is multiple compression risk, not a near-term earnings miss. Look for 10-15% relative downside if legal headlines escalate, and cut if the case is dismissed early.
• If already long AVGO, hedge 25-30% of the position with short-dated downside protection through the litigation calendar; the risk is a software-multiple de-rate, not semiconductor demand weakness.
• Watch NTNX and the VMware-migration ecosystem as a delayed beneficiary basket only if the case signals that customer lock-in is breaking; do not chase immediately, because the first reaction is likely to be slower migration rather than faster displacement.
• Set an alert for any management commentary quantifying VMware support obligations, renewal rates, or migration churn; if those metrics hold up despite the lawsuit, the market may be overpricing the legal overhang.