Tesco Rips Out VMware as Broadcom Fight Heads to Court
A 40,000-workload migration shows what happens when a perpetual license meets a subscription-only vendor.
Tesco, the UK retail giant, is pulling 40,000 server workloads off VMware, according to recent filings in its UK High Court breach-of-contract case against Broadcom. Strip away the legal language and it is one of the largest documented platform migrations to come directly out of the post-acquisition VMware era — and a fairly stark case study in what happens when the terms you signed stop being the terms you have.
The shape of the dispute is, by now, familiar to anyone who runs a virtualization estate. The details are what make Tesco instructive.
What Tesco says it bought, and what it got
Per reporting from The Register cited by Ars Technica, Tesco's account runs roughly as follows: in January 2021 it bought perpetual licenses for VMware's vSphere Foundation and Cloud Foundation, a subscription to VMware Tanzu, and support running to 2026 with an option to extend for four more years. Then Broadcom closed its VMware acquisition in November 2023.
From there, Tesco alleges, Broadcom declined to honor the deal — pressing the retailer toward "excessive and inflated prices for virtualization software for which Tesco has already paid," and refusing to sell support for its perpetually licensed software unless Tesco also bought "duplicative subscription-based licenses for those same Software products." In January, Tesco says, Broadcom stopped supporting its VMware products entirely; the company has been paying for third-party support since.
That last point is the one developers and operators should sit with. Broadcom, per the initial complaint, declined to provide software upgrades or all security updates to customers without active subscriptions. A perpetual license means you can keep running the bits. It does not mean you keep getting patches. For an estate of this size, "runs fine, no longer receives security fixes" is not a stable state — it is a countdown.
The migration is the hard part — and the risky part
Tesco isn't framing this exit as a strategic modernization. In its own words, it was "forced to incur material costs to procure alternative solutions with reduced functionality, and to migrate to that software in a manner, and on a timeframe, that creates very significant risks to its business." Best case, working "at exceptional pace," it expects to be fully off VMware by the end of 2027 at the earliest.
The technical sting is in the dependencies. Tesco says its new — and as yet unnamed — virtualization platform is incompatible with the Veeam and Zerto products it relies on for backup and disaster recovery. That is the part of any hypervisor migration that quietly eats the schedule:
- The hypervisor is rarely the lock-in. vSphere is replaceable on paper. The data-protection, replication, and DR tooling wired into it is what makes a swap genuinely fraught.
- Backup and DR are security-critical. Losing alignment between your virtualization layer and your recovery tooling means a window where your restore path is uncertain — exactly the kind of gap you do not want open while you are also rebuilding the platform underneath it.
- "Reduced functionality" is a tell. When a customer migrating under duress concedes the replacement does less, that is the cost of doing it on someone else's timeline rather than your own.
The broader lesson is unglamorous but durable: virtualization lock-in lives in the ecosystem, not the hypervisor. Storage integrations, backup agents, DR orchestration, monitoring hooks, and the operational muscle memory of the team are the things that don't port cleanly. An emergency migration surfaces every one of them at once.
The numbers, and the standoff
Tesco initially sought at least £100 million (about $133.6 million) in damages each from Broadcom, VMware, and reseller Computacenter, plus interest. It says it turned down at least four offers to keep using VMware and Broadcom's mainframe products. One, per the filings, priced VMware Cloud Foundation 9.0 plus mainframe software and support at $23.5 million for a single year — which Tesco characterizes as roughly 175 percent above what it believes it should pay for VMware, and a 350 percent hike on the mainframe side. It called the pricing "manifestly unfair and excessive."
Broadcom, in an amended defense, denied the hikes were unfair, and argued it shouldn't owe damages over Tesco's difficulty finding alternatives before its support lapsed — given that the retailer has, in the end, found replacement products. The case is expected to reach court between November 2027 and February 2028, with a possible trial after that. In other words, Tesco will likely finish migrating before the matter is decided.
A pattern, not an outlier
Tesco is the loud case, not the lonely one. Broadcom has clashed publicly with other large customers: it settled with AT&T on undisclosed terms, and is pursuing Siemens for alleged software piracy in the US District Court for the District of Delaware. Across the industry, VMware shops have spent two years recalculating renewals against the cost, time, and compatibility pain of leaving — and many have stalled, moving only some workloads, precisely because exits like Tesco's are expensive and slow.
Meanwhile the rivals are circling. Hewlett Packard Enterprise and Nutanix have pushed hard for disgruntled VMware users, and the open-source corner — KVM-based stacks, Proxmox, and the like — has enjoyed an unusual amount of attention from teams that hadn't seriously evaluated alternatives in a decade. Broadcom, for its part, has reported financial success with its large-enterprise-focused VMware strategy and shows no sign of changing course.
The uncomfortable takeaway for anyone running someone else's platform at scale: a perpetual license protects your right to run software, not your right to maintain it. The defensible move is to know your exit cost before you need it — to inventory exactly which third-party tools are welded to your hypervisor, and to treat "can we still get security patches under these terms" as a live question rather than a settled one. Tesco is now finding out what that inventory looks like at 40,000 workloads, under deadline, while in litigation. It is a more expensive way to learn.
Sources & further reading
Emeka has spent over a decade tracking threat actors, vulnerability disclosures, and the evolving landscape of application security, bringing a sharp continent-spanning perspective to his reporting. He's known for translating dense CVE advisories into clear, actionable context that developers and security teams alike actually read.
Discussion 7
i'm no lawyer but it seems like a big part of the issue here is the licensing model, which is why i always say just use postgres and avoid all the drama that comes with proprietary vendors
At my company, we are seeing migration to HyperV as the path forward using Azure Local as the management plane.
i've seen this movie before, perpetual license meets subscription-only vendor and suddenly the terms you signed aren't so perpetual anymore, 40,000 workloads is a nightmare to migrate 🤯
need to review our vmware contracts ASAP
@rashid_patel just use the standard library for what you can, less dependencies
@rashid_patel don't wait, get a head start on that review, you don't want to get broadsided by unexpected costs, looks like tesco's experience is a wake up call for all of us
@rashid_patel, been there, done that - we had similar issues with oracle back in the 90s, review those contracts but also consider having an exit strategy, just in case 🚪
