Why Your VMware Exit Needs a License Position First
Western Union is in the analysis phase of a VMware exit: 900 to 1,200 applications on a roughly 4,000-core estate. Brandon Shaw, vice president and head of technology services, told audiences at Nutanix’s .NEXT conference the firm had to choose between upgrading an aging vSphere platform and changing strategy. Broadcom’s “new economic structure,” he said, “had a significant part in it.” Cloud Foundation is the suite that conversation now walks in with. A destination is a consequence. The VMware exit license position is the cause.
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 hypervisor bake-off. It is a licensing-driven exit. The story only teaches you something if you can price stay-on-Cloud-Foundation against leave-for-somewhere-else against the estate you already run (this week, with the current bill still attached). If that answer takes three weeks of specialist reading, the destination vendor has already framed the meeting.
What Shaw actually said
Shaw spoke on the record at .NEXT, and the interviews that followed (Diginomica and SDxCentral) are the primary colour that matters. Western Union is 175 years old, operates in more than 200 countries, and has in-country processing requirements. Shaw joined in April 2024. The estate is not a lab. “We had to do something,” he said. Upgrade the aging hypervisor and continue the status quo, or look at company strategy.
Asked whether Broadcom’s post-acquisition price changes were a factor, he said yes. They were not a surprise. Western Union was running several VMware products, including vSphere. “At a certain point we had to make a decision on, do we keep going down this road or do we decide to build a new road.”
The destination is Nutanix. Shaw called the relationship a partnership rather than a supplier slot, and said executives were concerned about moving off a vendor they knew. Continuity language went into the paper. “That made them comfortable with the longevity of the deal.” He also wanted flexibility for in-country placement. The move is early. “We are early on. We’re in the analysis phase right now, and really kind of sorting and stacking and figuring out the order with which we’re going to be lifting and moving stuff over.” Older software is the obstacle he expected. Sometimes that means refactor. Sometimes it means the application is no longer needed.
Nutanix CEO Rajiv Ramaswami, speaking at the same event, put the addressable pool at about 165,000 of VMware’s current customers, approached in waves. Treat the case study as a named exit, not a census. It does not tell your CFO the market is leaving. It tells you the pattern your next VMware conversation will run on.
A VMware exit is a license event before it is a destination
Look at your own VMware file. Most SAM teams still have a row that says “vSphere” and a renewal date that says “next conversation.” Those two facts do not tell you whether the quote walking in is a like-for-like refresh or a Cloud Foundation conversion.
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.
This is not a criticism of the teams building those reports. Traditional SAM tools were built to prove completeness, not to tell you, this week, what Cloud Foundation costs against the SKUs you actually operate. 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.
Western Union did not leave because a slide said Nutanix was faster. Shaw named partnership friction and a new economic structure. The destination was a consequence. The license event was the cause.
Do not let either vendor frame the next meeting as “do you want a modern private cloud” or “do you want to get off Broadcom.” The question is which SKUs in the Cloud Foundation bundle you will operate, which you will pay for and park, and what that costs against the estate you already run: stay, convert, or leave.
That stay-versus-leave number is a cost-optimization problem on the cores you already run; Infrastructure Mapper and data sources (RVTools / vCenter) are the topology and intake. Hypervisor switches are not a new commercial pattern. Citrix’s post-Broadcom U-turn and the perpetual-to-subscription fight in Tesco vs Broadcom / VMware are already on the record.
Picture your procurement director, sixty days from a VMware conversation. The CIO has read the Western Union interviews. Finance wants the saving on this year’s forecast. Ramaswami expects people to arrive at an alternative when a product hits end of life or a license comes up for renewal. If you cannot put a stay-on-VCF case and a leave case on the table that survive contact with your current deployment, you do not have an exit case. You have a conference quote.
Nutanix is one place a named estate went. That does not make the destination the decision. A migration in its analysis phase is still a VMware estate. Continuity language is useful. It is not a license position for the product you have not finished leaving. You need your number first, on your cores, against the Cloud Foundation quote and against whatever alternative paper is in the room.
What to lock before you pick a destination
Do this before the next VMware conversation. Produce a decision pack, not a migration program.
| If this is the pressure | What the source shows | What you lock before you pick |
|---|---|---|
| Stay or convert to Cloud Foundation | Shaw: Broadcom’s new economic structure was a significant part of the decision. The suite is the quote most estates now see. | Deployment matched to the VCF SKU list. What you will operate vs pay-and-park. Current bill vs the VCF quote on this estate. |
| Leave because the revised licenses do not fit the strategy | Shaw: upgrade the aging platform, or change strategy. Price was a factor, not a surprise. | Revised quote vs current entitlement, dated. No delta this week means you have a feeling, not a case. |
| Leave over the partnership | Shaw: decent lines of communication with Broadcom, and still a desire for a “true partnership.” Continuity went into the Nutanix paper. | Written list of Broadcom products you will still buy after the hypervisor move. Continuity language on the destination, in the contract. |
| Leave on a renewal or end-of-life wave | Ramaswami: waves at EOL and license renewal, against an addressable pool of ~165,000 VMware customers. | Named exit date vs support end date. Residual Broadcom cost through cutover. Audit-ready if the move slips. |
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 license position. You have a destination rumor.
Your job is not to decide whether Nutanix is the right architecture. Western Union bought continuity assurances and is still sorting the order of the lift. Walk in with your own numbers before someone else’s case study becomes the default.
The decision layer, not another migration deck
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 Cloud Foundation costs against the SKUs you operate, what you will still owe Broadcom through a move, and whether the destination is a priced exit or a conference story. 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.
If you are heading into a VMware renewal or a Cloud Foundation conversation and your current tools still need three weeks to turn a 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 Cloud Foundation cost against that estate, what will we still pay through a move, and which destination (if any) is cheaper than that number on a clock we can keep. That is a data question, not a sales question.
Western Union is still in analysis on roughly 4,000 cores. 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.
