Updated: July 01, 2026
The email arrives, renewal quote attached, and the number has grown a digit since last year. For a lot of Indian IT leaders, that quote is the first real signal that the platform they have run quietly for a decade now sits at the centre of a budget problem. The instinct is to do something fast. The right move is to do something planned.
You have more room than the quote implies and less than you would like. This is how to use it: understand what changed, decide on the numbers rather than the shock, and if you move, move in a way that never takes production down.
Because Broadcom rebuilt the commercial model. After acquiring VMware, it retired perpetual licences, moved every customer to annual subscriptions, and bundled products into larger packages such as VMware Cloud Foundation and VVF rather than the individual components many estates were built on. For some organisations the increase has been modest. For others, renewals have doubled, tripled or worse, particularly where a small server now carries a large minimum licensing footprint.
The exact figures have been a moving target, which is its own lesson. Broadcom announced an aggressive minimum-core requirement, met a backlash, and walked part of it back. Quoting a single universal multiple would be wrong. What is consistent is the direction: subscription-only, bundled, renewed annually under stricter terms. Your specific number depends on your estate, which is exactly why it has to be modelled, not assumed.
No. A rushed migration is how a licensing problem becomes an outage. The renewal shock is real, but it is a prompt to decide, not to bolt. The disciplined response is a short, structured decision: model your renewal at the new terms, model the cost and effort of moving to each viable alternative, and compare them over three years. Some estates should move. Some should renegotiate and stay. The only wrong answer is choosing either under adrenaline.
There is a clock, and it helps to name it. Broadcom is steering customers toward an October 2027 VCF cutover. That is enough time to plan properly if you start now, and too little to leave until the deadline. The enterprises that will be calm in 2027 are the ones that did the analysis in 2026.
Three months is enough to reach a confident decision and a costed migration plan, without touching a single production workload yet. The work in this window is analysis and design, not cutover.
| Phase | Weeks | What you do | Outcome |
|---|---|---|---|
| Assess | 1–4 | Inventory the estate, dependencies and VMware-specific integrations | A clear picture of what you actually run |
| Model | 4–8 | Cost your renewal at the new terms against each alternative, over three years | A like-for-like financial comparison |
| Decide & design | 8–12 | Choose the path, design the target platform and a staged migration plan with a bill of quantities | A board-ready decision and a runbook |
At the end of ninety days, you have a number for staying, a number for each way of leaving, and a migration plan ready to execute on your timeline rather than Broadcom's.
In dependency-ordered waves, with a pilot first and a way back at every stage. You stand up the target platform, migrate a representative pilot and validate it, then move production in batches, checking each before the next. Modern tooling, such as Nutanix Move for the Nutanix path, automates much of the conversion so live workloads keep running while they are moved.
The outages in migration war stories almost always share one cause: trying to move everything in a single window to hit a date. Sequencing by dependency and risk is slower to plan and dramatically safer to run. The question that should govern the schedule is simple. What does one failed cutover cost your business, against the modest extra time of doing it in controlled waves?
Staying is a legitimate outcome, not a failure of nerve. For estates with deep VMware-specific integration, or no window to migrate before renewal, a renegotiated agreement can be the right answer. The point of the ninety-day analysis is that you negotiate from evidence: a costed migration alternative is the strongest lever you have at the table. A renewal signed because moving felt too hard is weak. A renewal signed because the maths genuinely favoured it is sound.
A hypervisor licence is easy to buy. A migration of thousands of virtual machines that keeps the business running is not, and that is where the choice of partner decides the outcome. The protection is in the assessment, the honest cost model and the sequencing, not the purchase order.
Proactive Data Systems plans and runs VMware exits and renewals for Indian enterprises, end-to-end. We are a Cisco Preferred Cloud and AI Partner, Dell Platinum Partner and NetApp Preferred Partner, with 35 years in enterprise IT, more than 1,500 organisations served, and a 24/7 service desk in India. We are multi-OEM by design, so the recommendation follows your estate rather than a quota, and we assess Nutanix, Hyper-V, Red Hat and a renegotiated VMware on their merits for your specific environment.
Send us your current VMware estate and your renewal date, and we will model the options and map the migration. Ask us for a VMware modernisation assessment.
Disclaimer: This article provides general information on VMware licensing and migration, not legal, financial or procurement advice, and is not a quote. Licensing terms, bundles, minimums and pricing change frequently and vary by agreement, and some announced changes have since been revised. Confirm your position with the vendor and qualified advisers before acting. VMware, Broadcom, Nutanix, Microsoft Hyper-V and Red Hat are trademarks of their respective owners; this is independent guidance, not endorsed by or affiliated with any of them, and should be reviewed by legal before publication.
Rokendra Singh Product Manager, Data Center, Proactive Data Systems
We'll get back to you shortly.
