Leaving VMware: Plan the Exit to HPE Morpheus and a ProLiant Gen12 Rebuild
Broadcom has retired perpetual VMware licensing entirely and moved every customer to subscription-only VMware Cloud Foundation (VCF), billed per core with a 16-core-per-CPU minimum and a smaller catalog of bundled products that carries NSX and Aria whether you use them or not. Renewal quotes have landed anywhere from roughly double to well over ten times prior perpetual-plus-support costs depending on your legacy discount level, and Broadcom has started issuing compliance audit notices to accounts still running perpetual licenses outside the new bundles. If your estate is on vSphere 7.x, general support already ended October 2, 2025, with technical guidance only through April 2, 2027; vSphere 8.x general support is scheduled to end October 11, 2027, and neither date gets easier to hit the longer you wait. The realistic exit path is not a weekend cutover: analyst guidance on VMware modernization puts enterprise-scale migrations at 18 to 36 months, which is why HPE built Morpheus VM Essentials as a coexistence platform that manages VMware ESXi and HPE's KVM-based virtual machines from one console, migrating VMs in guided waves instead of a single risky cutover and rolling up into HPE Private Cloud Business Edition or GreenLake for the hybrid-cloud control plane. Pair that software exit with a ProLiant Gen12 hardware refresh and you replace the licensing model and the aging compute in one project instead of two. Uniqcli, an authorized HPE partner, scopes the assessment, the phased migration, and the Gen12 rebuild together, quoted on federally buyable terms.
Signs it’s time to refresh
- Your VMware renewal quote came back at multiples of what you paid before, and finance wants a lower-cost alternative before the next renewal cycle
- You are still running perpetual vSphere licenses and have received (or expect) a compliance audit notice from Broadcom
- Your estate runs vSphere 7.x, where general support already ended in October 2025 and technical guidance runs out in April 2027
- You are being quoted full VMware Cloud Foundation (VCF) pricing, NSX and Aria included, when you only use core vSphere compute and hypervisor features
- Your hosts are older, lower-core-count CPUs that get billed against the 16-core-per-processor minimum, inflating cost per host
- Leadership has asked for a multi-hypervisor exit plan so no single vendor controls your virtualization roadmap again
Your refresh planning checklist
Work these in order, or send us where you are and we’ll build the plan with you.
- 1
Inventory the full VMware estate before pricing anything
Count every ESXi host, VM, vCenter instance, and dependent product (NSX, Aria, vSAN, Horizon) plus the hardware generation underneath. You cannot scope a realistic exit, or a realistic VCF renewal comparison, without an accurate count.
- 2
Classify workloads: migrate first, migrate later, or keep on VMware for now
Not every VM needs to move on day one. Separate low-risk, well-documented workloads for an early wave from complex or vendor-locked applications that need more validation time.
- 3
Map current core counts against the 16-core-per-CPU VCF minimum
Confirm what your actual VMware renewal would cost under Broadcom's current per-core, bundle-included pricing versus a Morpheus VM Essentials plus ProLiant Gen12 rebuild, so the business case is based on your numbers, not an industry average.
- 4
Pilot HPE Morpheus VM Essentials in coexistence mode
Stand up Morpheus alongside existing VMware infrastructure so it manages ESXi and HPE VM (HVM) side by side from one console. Validate the guided ESXi-to-HVM migration workflow on a small, low-risk workload set first.
- 5
Size the ProLiant Gen12 rebuild platform
Right-size Gen12 hosts to real utilization rather than replicating over-provisioned legacy VMware hosts core for core. Confirm memory, PCIe Gen5, and accelerator needs against current and near-term workloads.
- 6
Decide the storage path alongside the compute rebuild
Pair the hypervisor exit with Alletra dHCI or Alletra Storage MP so storage isn't left tied to a VMware-specific stack (vSAN) while everything else moves.
- 7
Sequence migration waves against your VMware support and renewal dates
Build the wave plan backward from your actual vSphere end-of-support or renewal date so critical workloads are validated on the new stack before you are forced into another VMware renewal cycle.
- 8
Plan licensing overlap and decommissioning
Budget for a period of running both platforms during migration, use available VM Essentials/Zerto migration incentives to offset that overlap, and set a clean decommission and data-sanitization step for retired VMware hosts.
A typical refresh timeline
Assessment (weeks 1-4)
Inventory the VMware estate, classify workloads by migration priority, and price your actual VCF renewal against a Morpheus VM Essentials plus ProLiant Gen12 alternative.
Pilot and design (weeks 4-10)
Stand up Morpheus VM Essentials in coexistence mode, migrate a small low-risk workload set to validate the process, and finalize the Gen12 and Alletra rebuild configuration and quote.
Procure and stage (weeks 10-16)
Order and rack ProLiant Gen12 hosts and Alletra storage, build out the target Morpheus/GreenLake environment, and prepare migration runbooks for each wave.
Migrate in waves (months 4-18+)
Move workloads in dependency order across defined waves, validating each on the new platform before proceeding. Enterprise-scale estates typically run 18 to 36 months end to end; smaller, well-documented environments move faster.
Decommission and close out (final phase)
Confirm sign-off on each migrated workload, retire and securely wipe legacy VMware hosts, and close out any remaining VMware licensing and support obligations.
Why run the refresh with Uniqcli
Coexistence, not a forced big-bang cutover
HPE Morpheus VM Essentials manages VMware ESXi and HPE VM side by side from one console, so you migrate in validated waves on your timeline instead of a single high-risk cutover weekend.
Software exit and hardware refresh planned as one project
We scope the Morpheus migration alongside the ProLiant Gen12 rebuild and Alletra storage so you solve the licensing exit and the aging-hardware problem together, not sequentially.
A real business case, not an industry-average estimate
We price your actual VMware renewal, including the 16-core-per-CPU minimum and bundled VCF components you may not use, against a Morpheus and ProLiant Gen12 alternative sized to your environment.
Authorized HPE partner, TAA-compliant, federally buyable
Genuine HPE Morpheus, GreenLake, ProLiant Gen12, and Alletra on TAA-compliant terms, quoted through GPC direct, SAP/FAR channels, and GSA eBuy, built for federal, DoD, SLED, and healthcare procurement.
Solutions to refresh into
Refresh planning — FAQs
Why are VMware renewal quotes so much higher than before?
Broadcom retired perpetual VMware licensing and moved every customer to subscription-only VMware Cloud Foundation, priced per core with a 16-core-per-CPU minimum, bundling components like NSX and Aria into the price whether you use them or not. Publicly reported renewal increases have ranged from roughly double prior costs to well over ten times for accounts on older, deeply discounted agreements, and at least one large enterprise customer publicly disputed an increase in the four-figure percentage range before settling.
Do we have to migrate everything at once?
No. HPE Morpheus VM Essentials is built for coexistence: it manages your existing VMware ESXi hosts and new HPE VM (KVM-based) hosts from a single console, so you migrate workloads in validated waves instead of a single forced cutover. Most organizations keep VMware running for complex or legacy workloads while moving lower-risk workloads first.
How long does a realistic VMware exit take?
For enterprise-scale estates, plan on 18 to 36 months from assessment to full decommission, sometimes longer for very large or dependency-heavy environments; smaller, well-documented environments move faster. Analyst guidance consistently flags undiscovered operational dependencies, not VM count, as the biggest source of schedule slip, which is why assessment and a small pilot wave come before any bulk migration commitment.
Does the hypervisor exit require new hardware?
Not strictly, but it is the natural pairing. Most VMware estates approaching a costly renewal are also running older server hardware that is due for a refresh anyway. Rebuilding on current HPE ProLiant Gen12 compute and Alletra storage while you migrate the hypervisor layer means you are not re-licensing an old platform you plan to replace within a year or two.
What happens to VMware-specific storage like vSAN during the exit?
vSAN is tied to the VMware stack, so it needs its own decision point in the plan. Moving to HPE Alletra dHCI or Alletra Storage MP decouples storage from the hypervisor, letting compute and storage scale independently and removing one more piece of VMware-specific dependency from the environment.
How do we actually buy the replacement stack?
Uniqcli is an authorized HPE partner and quotes Morpheus, GreenLake, ProLiant Gen12, and Alletra as TAA-compliant configurations through Government Purchase Card (GPC) direct, Simplified Acquisition Procedures (SAP, FAR Part 13), FAR-based purchase orders and RFQs, and GSA eBuy, with WAWF/PIEE registration for DoD invoicing and acceptance. Our GSA MAS application is in progress. We map the purchase to whichever vehicle your office already holds.
Build your HPE bill of materials.
Send us the requirement, the project, or an existing quote to beat. We come back with a validated, TAA-compliant HPE configuration and a real price, often below list.
connect [at] getuniqcli.com · Chicago, IL