A VMware renewal is approaching. The quote changes, but the infrastructure still carries the same applications, availability commitments and dependencies. The decision must bring commercial changes together with the organisation's ability to transform production.
A higher quote may justify evaluating another platform. It establishes neither the full migration cost nor its duration or realistically movable scope.
What to check in the licensing model
Start with exact quote references, included products, versions and coverage period. Broadcom documentation for VCF and VVF does not necessarily describe every VMware offering and contract.
For these solutions, the official counting method uses physical cores with a minimum of 16 cores per processor. vSAN entitlement sizing also involves raw capacity. Do not confuse useful capacity displayed by the datastore with the quantity used for licensing calculations.
The documented workflow for vSphere 9.x and VCF 9.0 uses subscriptions managed through VCF Operations, replacing traditional 25-character keys. Include this change in operations and upgrade planning.
For existing installations, review usage rights, support, patch access and upgrade rights separately. The end of a support period and a subscription expiry are different events. Clarify the conditions of the specific contract before setting an exit timeline.
Build a reliable comparison baseline
The decision file should contain four items:
- an inventory of hosts, processors, cores, versions and storage use;
- a mapping between products in use and quote line items;
- expiry dates and hardware and application support constraints;
- a dependency map covering vCenter, NSX, vSAN, backups and automation.
A total carried over from year to year can conceal scope changes. Compare quotes with identified features and periods, then separate any included migration or advisory services.
Applying a price multiplier from someone else's account to your estate would be unreliable. The outcome depends on the contract, configuration and required features.
Cost three paths over the same horizon
Choose a common study period, such as three years, as a working assumption. Account for hardware age and application deadlines.
| Path | Costs to include | Deciding question |
|---|---|---|
| Renew VMware | Subscriptions, support, hardware and management tools | Do retained capabilities and commitments justify the full cost? |
| Migrate progressively | Target, POC, transfer, training and temporary dual operations | Which workloads can leave with controlled risk? |
| Organise coexistence | Two platforms, two support chains and interfaces to maintain | Do remaining dependencies justify the lasting complexity? |
Include internal team effort in all three scenarios. A migration occupying the people responsible for disaster recovery or security has an opportunity cost even when no additional invoice records it.
Assign an owner and review date to coexistence. Otherwise, a transition can become permanent without an explicit operations budget.
Identify what prevents a quick exit
A VM booting on another platform does not prove that its service can be operated there. Check application support conditions, drivers, backups, restore procedures and monitoring integrations.
If vSAN holds the disks, assess storage options in our Ceph and SAN comparison. If the service depends on recovery after host failure, examine VMware HA and Proxmox HA.
For maintenance, vMotion and Live Migration examines live movement requirements. Our Proxmox and VMware comparison places these features in the wider operating model.
Use the deadline as a planning constraint
Work backwards from the contractual date through decision, target validation, hardware availability, POC, gap remediation, migration waves and operations handover.
If the schedule does not fit, document the choice: reduce the first wave, negotiate a transition or retain some workloads. A commercial deadline does not shorten the time needed for recovery and restore testing.
Rollback must account for writes made after cutover. Keeping a powered-off source VM may help technical rollback; it does not guarantee that it holds the latest data.
Document the next decision
Before choosing a hypervisor, list movable workloads, blocking dependencies and unverified assumptions. Attach a cost, deadline and required evidence to each.
A POC built around decision criteria can test the decisive assumptions. Our VMware-to-Proxmox migration method describes the path from inventory to migration waves.
If your renewal is approaching, request a VMware audit and roadmap assessment. The aim is to compare executable options using your estate and deadlines.
Official sources
Sources reviewed on 15 October 2026. Commercial rules and versions evolve; check the offering and contract applicable to the evaluated scope. Proposed horizons are methodological assumptions, without guaranteed savings or deadlines.