VMware Broadcom Stay vs Exit Is a Priced Decision
You still have a row that says “vSphere” and a renewal date that says “next conversation.” The quote walking in is VMware Cloud Foundation. The file on disk still says perpetual. Support is an option you thought you had, a partner invoice you thought would renew, or a third-party desk you have not priced. Azure VMware Solution, if you run it, is about to stop including the VMware license inside the node.
That’s the problem.
A VMware Broadcom stay vs exit is not a hypervisor bake-off. It is four commercial objects on one page: perpetual versus VCF, the support path versus a conversion, portable VCF on Azure VMware Solution, and third-party cover on the versions you actually run. This page is the parent: the decision pack you produce before anyone picks a destination.
Perpetual versus VCF is not a rename
A perpetual license is a right to keep using a version. It is not a right to patches, upgrades, or a vendor who still sells the SKU. Broadcom’s current catalog is subscription. VMware Cloud Foundation is the suite that conversation now walks in with. Previously you could pick parts of the stack. Broadcom now sells the complete suite.
If your reports still treat “VMware” as one product, you are reading a reporting layer. You have a hypervisor count. You do not have a commercial outcome.
Stay on perpetual only if you can name the support path that keeps those versions alive. Convert to VCF only if you can name which SKUs in the bundle you will operate, which you will pay for and park, and what that costs against the estate you already run (this week, with the current bill still attached). A five-year VCF lock without that split is a headline, not a stay case. LSEG stayed and bundled. The price is not in the announcement. Your stay case is a number on your cores.
Do not let the vendor frame the next meeting as “perpetual is over, here is Cloud Foundation.” Do not let your own side frame it as “we should stay because a serious operator stayed.” Both sentences skip the file.
This is not a criticism of the teams building those reports. Traditional SAM tools prove completeness, not what Cloud Foundation costs against the SKUs you operate this week. An analysis that arrives after the destination vendor has booked the room is a document. One that arrives during the meeting is a decision input.
The support path is a third object
Owned is not the same as supported. Tesco, T-Mobile, and Siemens are already on the record for that split. None of those dockets is your license position. Support rights on the way out (or the way through) are a priced path, not a renewal you can assume.
Separate the objects on paper: the entitlement you already hold; the support term that is still live, and the date it ends; any option or “stated out year” language, and who can still sell it; the VCF conversion quote on the same hosts. If your file collapses those four into one status called “covered,” you are answering a conversion meeting with a reporting layer.
A GSA framework discount is not this object either. A published percentage on Tanzu, Avi, and vDefend does not tell you what you are entitled to on vSphere. A CSP invoice is not a renewal path once the partner program that issued it has closed. Who can still transact is part of the support path.
Portable VCF on AVS is two counterparties
If you run Azure VMware Solution, stay versus exit has a second clock.
Microsoft’s portable VCF licensing reference is the primary source. Customers must purchase VCF licenses directly from Broadcom to use hyperscaler cloud services. As of 1 November 2025, Microsoft no longer includes a VCF license with new AVS node purchases. License-included pay-as-you-go deployments must transition to portable VCF by 31 October 2026 to remain compliant. Reserved instances that still carry a Microsoft-managed VCF license must be exchanged for VCF BYOL reservations, or those workloads must leave AVS, by 30 August 2027. If a reservation expires earlier, the license-included benefit ends on the expiry date.
Azure VMware Solution is not being switched off. After the cutoff, Microsoft sells the host. Broadcom sells the VCF. Two invoices. Two counterparties. One estate.
Do not let the announcement reframe this as modernization. The question is narrower: which of your AVS hosts are still license-included, what VCF you would have to buy to cover them, and whether you stay on AVS as BYOL or leave. Count by host type (AV36 and AV36P are 36 cores, AV48 is 48, AV52 is 52, AV64 is 64). Microsoft says a noncompliant private cloud can be suspended.
Third-party support is a priced option, not a feeling
Independent support is the fourth path people name when they do not want VCF and do not want to leave yet. It is a real option. It does not convert a perpetual license into a subscription you no longer need, retire an audit clause, or move the AVS dates. It buys time on the versions you already run, at a price you can put next to the VCF quote and next to an exit. If you cannot name the versions, the exclusions, and the end date, you do not have a third-party path. You have a rumor that the partner is looking into it.
The 2026 VMware file, already on the record
This page is the stay-versus-exit parent. The 2026 posts sit under it. Do not treat them as a rewrite of this pack.
Perpetual, support, and the channel: perpetual support with no path (Tesco), support list is not a license position (Siemens), exit support is a priced option (T-Mobile), CSP invoice is not the renewal path, GSA discount is not a license position.
Stay, shrink, or leave: exit needs a license position first (Western Union), VCF hike versus switching cost, five-year VCF stay is still a priced decision (LSEG), shrinking usage can raise unit price, leaving Broadcom without a file (Allstate).
Overlay and AVS: CISPE filing is not your license position, portable VCF turns AVS into two counterparties.
Start with perpetual-support, exit-first, and portable VCF.
Stay versus exit checklist
Do this in the next thirty days, as a decision pack rather than a migration program.
| Path | What you lock first | What “done” looks like |
|---|---|---|
| Stay on perpetual | Current count by product and version, matched to license, upgrade rights, and a named support path (vendor, documented exception, or third-party). | One page a non-specialist can brief. No third status called “the partner is looking into it.” |
| Convert to VCF | Deployment matched to the VCF SKU list. Operate versus pay-and-park. Current bill versus the VCF quote on this estate. Professional services as its own line. | A stay number on your cores, not a customer story. Term and price-protection language in writing. |
| Shrink | Named workloads that can move, certified. Residual cost on what stays. Switching cost on the slice. New unit price after the discount changes. | A dated shrink, not a 2028 hope. Confirm 8.x end of general support on Broadcom’s Product Lifecycle Matrix. Technical guidance for ESXi 8.0, vCenter Server 8.0, and vSAN 8.0 runs to 11 October 2029. |
| Exit | Applications you cannot unwind. Certification gaps. Residual Broadcom cost through cutover. Audit-ready file before you send the notice. | A destination cheaper than stay on a clock you can keep. Leftover licenses matched before uninstall. |
| AVS portable VCF | Host-level count of every license-included PAYG private cloud, by host type and core count. VCF purchase for the hosts you keep, or a dated exit. 31 October 2026 for PAYG. 30 August 2027 for reserved instances. | Registered portable VCF cores that match deployed BYOL cores. No growth on the old PAYG SKU after October. |
| Third-party support | Versions, exclusions, start date, end date, priced next to VCF and next to exit. | A cover letter you can put in the pack, not a verbal. |
| Who can still sell | Vendor, distributor, reseller, CSP: who took the last order, who is still authorized. | Named counterparty before the meeting. A closed CSP program or a GSA framework is not this name. |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have a stay-versus-exit. You have a library.
Picture your procurement director, sixty days out. The CIO has a stay headline and an exit headline. Finance wants the saving on this year’s forecast. None of those is a license position. The stay number is the VCF quote (or the perpetual-plus-support quote) on the estate you run. The leave number is not a rival’s list price. Switching cost is the residual you cannot unwind, plus extra platforms and extra hardware. That stay-versus-leave number is a cost-optimization problem on the cores you already run.
The decision layer, not another VMware inventory
You already have discovery data, a CMDB full of VMware records, and a renewal date on a spreadsheet. The gap is not another inventory. The gap is turning that estate into a decision: what you run, what perpetual still grants, what VCF costs against those SKUs, what support costs through a move, what portable VCF costs on AVS before October, and whether any destination is cheaper on a clock you can keep. 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. Audit defense is the ELP if Broadcom asks, or if you are about to say you are leaving.
If you are heading into a VMware renewal, a Cloud Foundation conversation, or an AVS cutoff and your current tools still need three weeks to turn a stay-versus-leave plan into a priced position, 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 “here is Cloud Foundation” or “here is the off-ramp.” The right question is: what are we actually running, what does stay cost, what does leave cost once you price the residual, what does portable VCF cost on AVS before 31 October 2026, and which path is cheaper on a clock we can keep. That is a data question, not a sales question.
The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
