If you are re-budgeting your VMware renewal bill, you are not alone. Since Broadcom completed its acquisition of VMware, VMware's licensing and sales model has changed significantly — perpetual licenses are being phased out, subscriptions have become the norm, and many enterprises have seen their renewal costs climb severalfold. This article is not here to sell anxiety. Its goal is to clarify three things: where exactly the change happened, which category your company falls into, and what to do next.
💡 The one-sentence takeaway: VMware's licensing change is a settled reality. But whether to replace it — and how — depends on your actual usage, licensing status, and business dependency. This article helps you build your own decision framework.
1. Where the Change Comes From: Perpetual to Subscription
For a long time, enterprises purchased VMware mainly under perpetual licenses: pay once for the right to use ESXi, vCenter, and other components, then pay only a relatively small support fee each year. For factory scenarios of "deploy once and run stably long-term," this model kept total cost of ownership (TCO) manageable.
After Broadcom completed the acquisition, it adjusted the sales model:
- Stopped selling new perpetual licenses; existing perpetual licenses must convert to subscription at renewal.
- Pushed bundled subscriptions: instead of flexible per-component purchasing, everything is sold as VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) packages.
- Restructured pricing: the industry widely reports that renewal costs for comparable scale have risen noticeably, in some scenarios severalfold.
For large enterprises, this cost may be acceptable; but for cost-conscious small and mid-sized factories, a virtualization budget that was tens of thousands of yuan per year could rise to over a hundred thousand or more. This calls for a reassessment of the cost structure.
2. VCF vs. VVF: The Two Subscription Models You Need to Know
The other key to understanding this change is the two new subscription models — VVF and VCF. They serve different positions, with very different costs and complexity.
| Dimension | VMware vSphere Foundation (VVF) | VMware Cloud Foundation (VCF) |
|---|---|---|
| Market position | Mid-market / departmental, virtualization consolidation and basic cloud management | Large enterprise / mission-critical, full-stack private cloud and hybrid cloud |
| Core architecture | vSphere-centric management suite | Fully integrated software-defined data center platform |
| Network & security | No NSX included; advanced networking sold separately | NSX mandatory, with native micro-segmentation and advanced network services |
| Storage | Includes vSAN license; external storage also supported | vSAN-centric, hyper-converged architecture |
| Hardware requirements | Follows VMware compatibility guide; relatively flexible | Requires VCF-certified hardware; strict |
| Total cost of ownership | Relatively lower | Higher (software license + certified hardware + professional services) |
📌 Key insight: VCF is a "full-stack" solution that integrates compute, storage, and networking under a unified platform — comprehensive but costly and hardware-demanding. VVF focuses more on virtualization consolidation and is relatively lightweight. Many enterprises only ever used vSphere's basic capabilities, yet were steered toward the more expensive VCF bundled subscription — a major reason costs rose.
3. Do a 3-Step Self-Check Before Deciding Whether to Replace
Before considering replacement, answer these three questions to avoid hasty decisions based on incomplete information:
Step 1: How much are you actually using?
- How many virtual machines (VMs)? Dozens or over a hundred?
- What workloads run on them? ERP, MES, databases, or office systems?
- How many physical servers and CPU cores?
Step 2: What is your licensing status?
- Perpetual or already subscription? Has the perpetual license expired or is it about to?
- What is the genuine-license coverage ratio? Does it include components beyond vSphere?
- How much has renewal cost risen? Get exact figures before deciding.
Step 3: What is your tolerance for downtime?
- Which systems must run 24×7? Which can accept planned maintenance windows?
- Can existing disaster recovery capabilities cover you?
- How much downtime is acceptable during migration?
After these three steps, you will have a clear picture: your scale, your cost pressure, your migration risk tolerance. This is the foundation for all subsequent decisions.
4. Nine Customer Profiles: Find Where You Fit
Different enterprises are affected very differently by this change. Based on our observations, we group affected customers into nine profiles. Match yourself against the categories below to determine your profile and action priority.
| Profile | Core characteristics | Primary driver |
|---|---|---|
| Profile 1 | Strong Xinchuang (domestic tech) compliance constraints (government, finance, central SOEs) | Compliance requirements |
| Profile 2 | High genuine ratio, many components, perpetual license expired or about to expire | Renewal cost up sharply |
| Profile 3 | High genuine ratio, many components, license not yet expired | Cost up (can plan ahead) |
| Profile 4 | vSphere only, running critical workloads | Service & patch access harder |
| Profile 5 | vSphere only, critical workloads, service access acceptable | Service continuity (monitor) |
| Profile 6 | High genuine ratio, vSphere only, non-critical workloads | Low short-term pressure |
| Profile 7 | Low genuine ratio, pays annually for service, critical workloads | Legitimization + service access difficulty |
| Profile 8 | Low genuine ratio, non-critical workloads, paid service | Low short-term pressure |
| Profile 9 | Low genuine ratio, non-critical workloads, no paid service | Very low short-term pressure |
To generalize, these nine profiles can be grouped by replacement driver into three tiers:
- Strong driver (Profiles 1, 2, 3): subject to hard compliance requirements, or high genuine ratio with many components and expiring licenses, driving renewal costs sharply up. These are the earliest and most in need of starting an evaluation.
- Moderate driver (Profiles 4, 5, 7): relatively high genuine ratio but only using vSphere basics, or low genuine ratio but running critical workloads. Common concern is future service and patch access, plus stability of critical workloads.
- Low driver (Profiles 6, 8, 9): no critical workloads; no clear short-term cost or service pressure. These can slow down, but should keep watching the trend.
🎯 The core of the judgment isn't "whose technology is more advanced," but "how much you actually use, your licensing status, and how heavy your business dependency is." The shallower your usage and the lighter your dependency, the lower the cost and risk of replacement — and the simpler the decision.
5. Three Replacement Paths, and Who Each Fits
Combining the self-check and classification above, a small or mid-sized manufacturer's replacement path usually falls into one of these three:
| Path | Who it fits | Concerns | Benefits |
|---|---|---|---|
| A. Keep using VMware | Small scale, high migration risk, better not to change in the short term | Ongoing subscription cost; budget carefully | Zero migration risk, stable operations |
| B. Replace with domestic hyper-converged (e.g., Sangfor) | Shallow VMware usage; value cost-performance and local service | One-time migration effort; needs validation | Cost drops markedly; fast local support |
| C. Move to cloud / hybrid cloud | Needs elasticity; wants to reduce data-center ops burden | Complex migration; architecture redesign | Elastic scaling; ops burden shifted |
A practical decision guide:
- If you mainly run basic VM scenarios and haven't deeply used advanced components like vSAN or NSX, replacing with domestic hyper-converged is usually the most cost-effective and lightest migration.
- If you are deeply tied to advanced VMware ecosystem features and migration risk is high, continuing to use VMware or partial cloud migration may be safer.
- If your hardware is itself due for a refresh, combine "server repurposing assessment" with replacement planning to finish upgrade and migration in one pass and avoid duplicate investment.
6. Key Points During Migration
Replacing VMware is not "swap the software and reinstall." Based on our migration experience, pay attention to these areas:
- Information gathering first: before migration, fully collect hardware, business, and existing VM inventory — the prerequisite for a migration plan.
- The plan must include risk and rollback: clearly define migration method, risk points, time estimate, and rollback path in case of anomalies; don't "migrate while figuring it out."
- Rehearse before cutover: validate migration time and rollback through a rehearsal, then move into formal batch migration with a trial-run period.
- Plan downtime windows in advance: which systems support online migration and which must shut down directly determine interruption duration.
- Verify compatibility early: test key systems (ERP, MES, databases) against the new platform in advance to avoid post-migration surprises.
- Repurposing hardware has standards: if reusing existing servers, assess whether CPU, memory, SSD/HDD meet hyper-converged requirements to avoid performance pitfalls.
⚠️ The most important point: don't wait until the license is about to expire to start evaluating. Migration needs a full planning and rehearsal cycle. Leaving enough time gives you the initiative to decide calmly.
7. Conclusion: An Actionable Recommendation
Stringing the analysis together, the conclusion is:
- First, find your profile: determine which of the nine profiles you fall into — "evaluate now," "plan ahead," or "keep watching."
- Then take stock: VM count, licensing status, and business dependency — these three facts are the decision foundation; all are essential.
- Finally, choose a path: shallow usage and cost-sensitive → prioritize domestic hyper-converged; deep dependency and high migration risk → continue using or move gradually to cloud.
More important than agonizing over "should we replace" is first understanding "where exactly we stand." The clearer the information, the simpler the choice — and the less likely a single renewal bill throws off your rhythm.
About Cloud Valley
Cloud Valley Information Technology has served manufacturing IT for 20+ years, with deep implementation experience in virtualization migration, private cloud, and hyper-converged deployment and transformation. We can help you:
- Free inventory of your existing VMware environment (VM list + licensing status + cost estimate)
- Based on your actual usage, determine your profile and the best replacement path
- Migration assessment and implementation, covering information gathering, planning, rehearsal, and trial run
- Post-migration managed operations, letting you focus on production