The Hidden Cost of Leaving Broadcom Without a File
CA sued Allstate in the Northern District of California on 5 May 2025 (CA, Inc. v. Allstate Insurance Co., No. 3:25-cv-03862). The claim is leftover use after Allstate sold Employer Voluntary Benefits to StanCorp. VMware sued on 15 December 2025 (VMware LLC v. Allstate Insurance Co., No. 3:25-cv-10687), alleging Allstate would not complete a contractual audit. In the VMware complaint, Allstate said on 12 September 2025 that VMware was gone from devices, and on 1 October 2025 that instances were gone from the ELA environment. Both cases remain open.
That’s the problem.
The parent pack is the VMware Broadcom stay vs exit page: perpetual versus VCF, the support path, portable VCF on AVS, and third-party cover.
This is not a revenge story, and it is not a stonewalling story. Those are the two versions already on the docket. It is what happens when you tell a vendor you are leaving before you have a file that can survive the conversation. Leftover licenses from a sale sit unmatched. The scripts arrive after you have uninstalled. If you cannot produce a defensible position before you send the notice, the notice itself becomes the trigger.
What the two dockets actually allege
No judgment. No settlement figure you should brief as yours.
Software license audits are not unusual. Vendors write the right into the contract, and that right can run past the term so the vendor can be paid for use under a time-limited deal. That is background, not a finding.
VMware’s version, in the December complaint, is cooperation refused. It says it issued a formal audit notice on 4 March 2025 under the Master Agreement, that Connor Consulting sent a questionnaire, a deployment workbook, and detection scripts, and that Allstate later returned a questionnaire VMware called “woefully incomplete.” It says Allstate then declared the software gone and the audit complete.
Allstate’s version, in later filings, is sequence and capacity. The audits, it says, landed once VMware knew Allstate would not renew. After the estate came down, Allstate said the scripts would not work because they needed components still running. Both sides tried alternative dispute resolution. The court has not decided who is right.
Tesco is the perpetual-to-subscription fight. Siemens is the inventory reminder. Neither is this docket.
The Broadcom exit audit starts when you say you are leaving
The decision to leave is a commercial event. So is the sentence that tells the vendor you will not renew. So is the sentence that says the software is already gone. Each one changes what the other side can ask for, and what you can still prove.
If your team treats “we are leaving” as the end of the SAM work, you are reading the exit as a project close. The vendor is reading it as the start of the window in which audit rights still apply. Those rights can extend past the term. An uninstall does not close that window. It closes the one evidence path the vendor’s scripts were built to use.
This is not a criticism of the teams who pull the estate down. Discovery tools report what is installed today. They do not produce the position you will need the week after the last VM is gone. The gap is not missing data. The gap is that nothing turned the pre-exit estate into a file you can still defend once the scripts have nothing to find.
Picture the Friday you notify the vendor. Legal wants the letter out. Infrastructure wants the hypervisor gone. SAM still has last quarter’s inventory. If the only answer you can produce is “we removed it,” you have a status. You do not have a position.
An analysis that arrives after the vendor has framed the meeting is a document. One that arrives before you send the notice is a decision input.
A sold business does not close the license file
The CA suit is not a hypervisor story. It is a leftover-license story.
WilmerHale’s reading of the complaint is the clean summary of CA’s allegations. Allstate announced the EVB sale to StanCorp in August 2024 and closed it on 1 April 2025. Between announcement and close, Allstate told CA it intended to let EVB and StanCorp keep using ESP Workload Automation for a transitional period. CA says the 2021 licence did not allow that, asked for a proposal, and then learned the deal had closed without new paper. CA seeks at least $80 million, plus an injunction. Allstate, in a May letter quoted in the same alert, said it had acted in accordance with its rights.
A carve-out moves people, applications, and often the installs. It does not automatically move, terminate, or re-paper the entitlements. Someone still has to say which licenses traveled, which stayed, and which use is now sitting on the wrong side of the boundary.
If your reports still treat the parent estate as one row after a sale, you are reading a reporting layer. You have a legal-entity change. You do not have a license position.
Do that match while the deal team is still in the room. Name the products the sold unit ran and the products you still run. Match both to current entitlement. Write down who may keep using what, for how long, and on whose paper.
VMware’s complaint describes more than one workstream. A team that can sit one questionnaire will not sit four in the same month unless that work was scoped before the notice went out.
What to have before you tell the vendor you are leaving
Do this before the letter, the “we will not renew” call, or the sentence that says the software is already gone.
| Before you send it | What you produce | Why it changes the next meeting |
|---|---|---|
| The leave notice | Deployment matched to entitlement for every Broadcom product you still run, dated the week you notify | VMware says Allstate returned a “woefully incomplete” questionnaire. A stale export is not a position. |
| “We have left” | Versions, counts, and locations from before cutover, plus the date each instance came down | Allstate said the scripts would not work after removal. Scripts detect installs. They do not reconstruct last month. |
| A recent divestiture | Products the sold unit took, products you kept, and the paper on each side of the boundary | CA’s claim is a post-sale breach after EVB went to StanCorp. The sale does not close the file. |
| The audit clause | How far the right runs past term, which entities it covers, and whether multiple probes can run at once | Know the clause before you decline or delay. Capacity is readiness, not an excuse from week two. |
| More than one notice | Named owners, one evidence room, and a written order of response | VMware’s complaint describes workstream teams. Scope the room before the scripts arrive. |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today, including the unit you already sold? If not, you have a notification, not an exit plan.
The decision layer, not another inventory
You already have discovery data, a divestiture folder, and a renewal date. The gap is not another inventory. The gap is turning that estate into a decision before you tell the vendor you are leaving: what is still deployed, what the sold unit took, what the audit clause still lets the vendor ask, and what you can prove after the scripts have nothing to find. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Infrastructure Mapper is the host topology you need before the last VM is gone. A 90-day audit preparation plan is the work before the letter, not after the scripts arrive. How audit pressure exposes what dashboards hide is the same sequence.
If you are heading into a Broadcom exit or audit and your current tools still need three weeks to turn “we are leaving” into a file, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “you left, so we audit.” Do not let your own side frame it as “we left, so the file is closed.” The right question is: what were we running the week before notice, what does the contract still let the vendor inspect, which licenses stayed with the sold unit, and what number walks into the room if those two files do not match. That is a data question, not a sales question.
Allstate calls the review late. Broadcom calls the response a stonewall. The court will sort the allegations. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and written before you say you are gone.
