PPK exited VMware and moved to Azure Local after Broadcom renewal pressure changed the platform decision
PPK Mining Equipment operates in the Newcastle industrial corridor, supporting mining and industrial customers through specialist equipment, service and operational capability. When Broadcom's VMware renewal model changed the economics of staying on VMware, PPK needed more than a licence response. The business needed a structured infrastructure decision: whether to renew, reduce, bridge, migrate to public cloud, or replace VMware with a supportable local platform.
Inlight IT reviewed PPK's three-node VMware estate, assessed six landing paths, selected Azure Local, planned the migration and delivered the exit. More than 20 virtual server workloads were reviewed and migrated, with backup, recovery, cutover sequencing and post-migration support included in the scope. The outcome was a controlled VMware exit: renewal exposure removed, Azure Local established as the new platform, backup aligned to the new environment, and the estate brought into managed support after cutover.
- Client
- PPK Mining Equipment
- Industry
- Mining equipment and industrial services
- Location
- Newcastle industrial corridor
- Starting point
- Three-node VMware estate facing Broadcom subscription renewal pressure
- Engagement type
- VMware estate review, six-path landing assessment, Azure Local migration, backup alignment and managed support
- Workload scope
- More than 20 virtual server workloads reviewed and migrated, with backup, recovery, cutover sequencing and post-migration support in scope
- Platform outcome
- Azure Local established as the retained local platform, with backup and day-two support included
PPK Mining Equipment — VMware exit to Azure Local
A structured infrastructure decision delivered from estate review through to managed support.
Six paths assessed, one controlled exit
The existing estate — hosts, lifecycle, VM footprint and the dependencies behind the workloads — reviewed before any platform decision was made.
More than 20 virtual server workloads assessed and migrated through controlled sequencing.
Renew, reduce, bridge with AVS, public-cloud migration, Nutanix and Azure Local — assessed so the decision was made on fit, not default.
Azure Local selected as a Microsoft-aligned local platform for retained workloads, with a clearer path to hybrid management.
For an industrial business, a VMware renewal is not just a licence event — it is the moment the platform direction gets tested
PPK Mining Equipment runs in an industrial environment where technology supports communication, access to business systems, operational coordination, customer response and continuity.
Broadcom renewal pressure created the decision point. Staying on VMware may have been possible, but it needed to be justified. Exiting VMware was also possible, but only if the migration path protected workloads, dependencies, backup and day-two support.
Inlight IT treated the work as a platform decision, not a licensing reaction.
PPK needed to exit VMware without turning renewal pressure into migration risk
VMware renewal shock can push a business to move quickly. The risk is moving too quickly in the wrong way. For PPK, the exit needed to be structured around workloads, dependencies, backup, cutover and support after migration.
The decision needed structure, not reaction
PPK needed more than a licence response. The business needed a structured infrastructure decision: whether to renew, reduce, bridge, migrate to public cloud, or replace VMware with a supportable local platform.
The renewal had become a platform question
Broadcom completed its acquisition of VMware in November 2023, then shifted to subscription licensing, including the end of sale of perpetual licences and Support and Subscription renewals for perpetual offerings. That changed many VMware renewals from routine licence events into broader infrastructure decisions.
Not every workload needed a public-cloud landing
PPK needed to exit VMware, but the estate still needed local control, predictable access, supportable infrastructure and clear backup alignment. A blanket public-cloud move was not the right answer for every workload.
The exit had to protect backup and recovery
More than 20 virtual server workloads had to move with backup, recovery and dependency continuity intact. A platform change that left recovery unclear would not have been a credible exit.
Day-two support had to be part of the plan
The migration was only complete if the new platform could be operated and supported after cutover, not just stood up.
A VMware exit to Azure Local delivered through assessment, migration planning, backup alignment and controlled cutover
Inlight IT structured the project across five delivery streams. Each stream reduced a different migration risk, and the project deliberately avoided premature platform selection.
01Estate review
The project started by understanding what PPK was actually running — the three-node VMware estate, host lifecycle, VM footprint and the dependencies behind the workloads.
02Workload mapping
The workloads were assessed before migration sequencing began, so dependencies, performance needs and migration risk were understood per workload rather than assumed.
03Platform comparison
Azure Local was selected after the realistic options were assessed — renew, reduce, bridge with AVS, public-cloud migration, Nutanix and Azure Local — so the decision was made on fit, not default.
04Azure Local migration planning
The VMware exit moved from review into execution, with migration sequencing, cutover windows and rollback considered before production change.
05Backup and managed support alignment
Backup and day-two operations were included in the migration scope, so recovery was aligned to the new platform and the estate came into managed support after cutover.
From renewal pressure to a controlled platform decision
Select a stage to trace how renewal pressure became a controlled exit to Azure Local.
VMware renewal pressure has turned virtualisation into a platform decision
Broadcom completed its acquisition of VMware in November 2023. VMware by Broadcom then announced a shift to subscription licensing, including the end of sale of perpetual licences and Support and Subscription renewals for perpetual offerings. That changed many VMware renewals from routine licence events into broader infrastructure decisions — which is exactly the position PPK faced.
Broadcom completed its acquisition of VMware, then shifted to subscription licensing and ended the sale of perpetual licences.
Landing paths assessed against the estate before Azure Local was selected — the decision made on fit, not default.
Virtual server workloads moved with backup, recovery and dependency continuity intact.
Node VMware estate reviewed before any landing path was selected.
PPK exited VMware and moved to Azure Local through a controlled platform decision
The project moved PPK from VMware renewal pressure to a clearer Azure Local operating model. The business avoided renewing by inertia, avoided a rushed platform decision, and completed the migration with workload fit, backup, recovery and supportability considered.
Renewal exposure removed
The VMware subscription renewal pressure no longer dictated the platform direction.
Azure Local established
A Microsoft-aligned local platform was stood up for retained workloads, with a clearer path to hybrid management.
Backup aligned to the new platform
Recovery was re-aligned to Azure Local rather than left attached to the old environment.
Brought into managed support
The estate moved into ongoing managed support after cutover, so day-two operations had an owner.
Cutover planned with rollback in mind
Migration sequencing, cutover windows and rollback were considered before production change.
Workloads moved with dependencies understood
Dependencies, performance needs and migration risk were understood per workload rather than assumed.
The business avoided renewing by inertia, avoided a rushed platform decision, and completed the migration with workload fit, backup, recovery and supportability considered.
A VMware exit delivered as a platform decision, not a licensing reaction
Newcastle industrial operating context
Platform decision aligned to PPK's Newcastle industrial environment.
Three-node VMware estate reviewed
The existing estate was assessed before any landing path was selected.
Six landing paths compared
Renew, reduce, bridge, public cloud, Nutanix and Azure Local were assessed against the estate.
20+ workloads migrated
More than 20 virtual server workloads moved through controlled sequencing.
Backup and recovery aligned
Backup was re-aligned to Azure Local as part of the migration scope.
Managed support after cutover
Day-two operations were included so the new platform stayed supportable.
The work connected platform assessment, controlled migration and day-two support
Platform decision
6- VMware exit
- Broadcom renewal response
- HCI platform selection
- Six-path landing assessment
- Azure Local
- Nutanix and public cloud assessed
Assessment and planning
6- Estate review
- Workload assessment
- Dependency mapping
- Migration planning
- Cutover sequencing
- Rollback planning
Backup and recovery
6- Backup alignment
- Recovery validation
- Dependency continuity
- Recovery re-aligned to Azure Local
- Backup in migration scope
- Credible exit criteria
Operations after cutover
6- Managed infrastructure support
- Day-two operations
- Post-migration support
- Hybrid management pathway
- Supportable local platform
- Renewal exposure removed
Is your VMware renewal forcing a bigger infrastructure decision?
We assess your VMware estate, workload placement and target platform ahead of renewal.
Discuss infrastructure refresh