Broadcom VMware renewal
We review your Broadcom VMware renewal against the hosts, applications and hardware it covers, then deliver the chosen path. That can mean renewing VMware, reducing the capacity being licensed or moving workloads to another platform, with migration, backup and ongoing operations planned together.
| Area | Quoted | After planned retirement |
|---|---|---|
| ESXi hosts | 4 | 3 |
| Physical cores | 128 | 96 |
| vSAN raw capacity | 40 TiB | 30 TiB |
Count the physical cores before comparing the quote
Broadcom's published capacity guidance for VMware Cloud Foundation and VMware vSphere Foundation counts physical cores across the ESXi hosts being licensed, with a minimum of 16 cores per physical CPU. Disabling cores in the BIOS doesn't remove them from that requirement.
For vSAN, we check the raw storage capacity contributed to the cluster against the entitlement in the quoted product and any additional capacity required. The usable datastore figure alone isn't enough for that calculation.
We reconcile the quote with the host inventory, processors, core counts, product, term and support. Production, standby and recovery arrangements are checked against the applicable terms, including any order requirements. That establishes what the business is committing to before alternatives are costed.
Broadcom subscription capacity guidance ↗A smaller VM estate has to become a smaller licence requirement
Moving or retiring virtual machines can release capacity. A lower renewal cost depends on reducing the hosts or cores that need licensing, or changing the applicable product or commercial arrangement. Any consolidation still needs capacity for growth, maintenance and host failure.
Renew deliberately, stage a transition or change platform
Keep VMware where it continues to fit
Renewal can be the sound choice where applications depend on VMware capabilities, the hardware remains serviceable and the cost of change outweighs the benefit. We validate the product and licensed capacity against the period you intend to keep the environment, including any consolidation that can be completed before renewal.
Create time to build and validate the destination
Where an exit can't be completed within the current window, we align the available renewal term with the migration plan. That includes the cost of running both platforms and any commitment that remains after workloads move. The plan has defined milestones and a date for the next decision.
Move when the workload and commercial case support it
We compare the destinations against the same applications, recovery requirements and operating period. The selected environment is built and tested before production moves, with application owners involved in validation and the operating team prepared for the change.
Align the renewal with the infrastructure lifecycle
The VMware commitment and the hardware lifecycle often run to different dates. We bring both into the programme before either investment is locked in.
The hosts may still have useful life. A renewal or staged transition can preserve that investment while applications, backup and the target platform are prepared for migration.
Settle the platform direction before ordering servers and storage. Compatibility, core density, resilience and the workloads remaining locally affect what should be purchased.
We cost licensing, hardware, workload moves and recovery as one investment. Procurement lead times and the migration window are included, so the proposed saving is achievable in the time available.
Build the VMware exit plan around the workloads
We map each application and its dependencies before choosing a replacement. The review covers guest operating systems, application vendor support, storage I/O, latency, network paths, backup tooling and any VMware-specific capabilities in use. Workloads can then be retained, moved, replaced or retired individually.
Azure Local
A local hyperconverged platform with Azure-connected management. We check validated hardware, application compatibility, licensing, backup and the operating requirements of the proposed configuration.
Compare VMware and Azure Local →Hyper-V on Windows Server
A conventional Microsoft virtualisation option for suitable local workloads. We assess host and guest licensing, storage, clustering, backup and hardware support, including whether existing equipment can be retained.
Explore local infrastructure options →Nutanix AHV
An HCI option combining AHV virtualisation, AOS storage and Prism management. We compare the commercial package, supported hardware, application fit, migration tooling and the skills needed to operate it.
Compare Azure Local and Nutanix →Proxmox VE
An option for Windows and Linux workloads where KVM, storage flexibility and the subscription model suit the estate. Application support, backup compatibility, cluster design and access to Linux expertise form part of the decision.
See where Proxmox fits →Azure services and Microsoft 365
Some workloads can skip another local hypervisor and move to Azure VMs, managed application services or Microsoft 365. We test the benefit against application changes, connectivity, consumption and recovery costs.
Explore workload placement and cloud migration →Azure VMware Solution is still VMware
AVS runs VMware in Azure and can suit a data centre exit or a requirement to keep the VMware operating model. It can be an interim or longer-term destination. The commercial comparison needs both Azure infrastructure charges and the applicable VMware licensing.
Microsoft is moving AVS to portable VMware Cloud Foundation licensing as licence-included SKUs retire. For an existing AVS environment, we check the SKU, entitlement and transition deadline before planning a renewal or move.
The comparison covers platform and guest licensing, hardware, backup, networking, management, migration, parallel running and training over a common planning period. We document the viable destinations, the selected path for each workload group, the cost assumptions and what must be resolved before migration.
Read our insight on VMware exit and workload placement →We deliver the platform change and manage what follows
Build and prove the target
We design and source the destination, then validate representative workloads against application, performance and recovery requirements. Guest drivers, vendor support, virtual networking and backup integration are checked for the selected platform.
Prepare coexistence and recovery
We maintain identity, DNS, network access, monitoring and protection while old and new platforms operate together. Backup compatibility, retention and restore procedures are confirmed for the target, including how historical backups stay accessible.
Migrate in dependency groups
Applications move with the databases, file services and authentication they rely on. Each wave has agreed change windows, owners, validation criteria and rollback limits, and we mark the point after which rolling back means a restore or data reconciliation.
Stabilise and retire the old platform
Application owners validate access, data and performance before acceptance. We verify destination backups and document the environment, then decommission the VMware components covered by the exit. Ongoing patching, monitoring, capacity and recovery testing can stay with our team under the agreed scope.
Bring the renewal quote and the estate behind it
Send us the quote and renewal date, with the host inventory, hardware support position and a summary of the applications. Existing backup reports, recovery requirements and known migration constraints help set the scope. We can fill the gaps with your team before committing to a platform or programme.
See what we’ve delivered for our clients
nodes in the VMware estate
virtual server workloads migrated
landing paths assessed before selection
Questions about VMware renewal and alternatives
When does renewing VMware make sense?
When the platform still fits, the infrastructure has useful life and the quoted commitment is justified over the intended period. Keeping VMware can also give a migration the time it needs, with a defined destination and transition plan.
Does moving VMs reduce VMware licensing?
Moving VMs may allow hosts to be removed or replaced with a smaller licensed configuration. The financial benefit depends on that capacity change and the applicable commercial terms, and the remaining environment still needs to meet performance and resilience requirements.
Can we renew now and move later?
Yes, where the available term and conditions support the plan. We work backwards from the intended exit date, allowing for procurement, testing, application availability and parallel running. Any renewal cost that continues after migration stays in the comparison.
Is Azure VMware Solution a VMware exit?
AVS moves VMware workloads into Azure while keeping the VMware platform. It can support a data centre exit or provide a longer-term home for suitable workloads. A move to Azure VMs, Azure Local or another hypervisor changes the platform itself.
Which VMware alternative is best?
It depends on the applications, hardware, recovery requirements and operating team, and an estate may need more than one destination. We compare local platforms and cloud options against those requirements before selecting the configuration.
Can we keep some workloads on VMware and move others?
Yes. A smaller VMware footprint can stay for applications that depend on it while others move, as long as the remaining hosts and cores are licensed on terms that still make sense. We plan the two environments together, including backup, monitoring and how long both will run.
What happens to our backups when we leave VMware?
Backup tooling and retention are set up and tested on the new platform before production moves. We also plan how historical backups taken on VMware stay accessible for their retention period, so restores remain possible after the old hosts are retired.
Can you deliver the migration and run the new environment?
Yes. We take the work from estate review and design through procurement, migration and ongoing management. The scope sets out responsibilities for Inlight IT, your team and application vendors, including validation, support hours and escalation.
Settle the VMware decision before the next commitment
Talk to us before the renewal or hardware order is locked in. We'll work through the commercial and technical requirements, then carry the selected path through to implementation and operation.