Facing Broadcom price increases? Most clients save 75–87% on VMware support. Get your repricing analysis free.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
NSX-V: The Network Virtualisation Product Broadcom Wants You to Forget
VMware NSX for vSphere (NSX-V) went end of general support on 16 January 2022. VMware's successor is NSX-T (now just "NSX" under Broadcom). But — and this is the number Broadcom's account teams won't publicise — industry estimates suggest 2,000–3,000 organisations globally are still running NSX-V production environments in 2026. The migration to NSX-T is not a version upgrade: it requires a complete rearchitecting of the virtual network. NSX-V's distributed logical routers and VXLANs do not map 1:1 to NSX-T's Tier-0/Tier-1 topology. Migrations take 12–24 months for large environments.
NSX-V Version Timeline and Support Status
| Product Version | End of Support Date |
|---|---|
| NSX for vSphere 6.2.x | 15 August 2018 |
| NSX for vSphere 6.3.x | 22 August 2019 |
| NSX for vSphere 6.4.0–6.4.4 | 16 January 2021 |
| NSX for vSphere 6.4.5–6.4.10 | 16 January 2022 (General Support) |
| NSX for vSphere 6.4.12+ (final release) | 16 January 2022; Technical Guidance only to Jan 2024 |
| NSX-T 2.x | December 2021 |
| NSX-T 3.0.x | January 2023 |
| NSX-T 3.1.x | June 2023 |
| NSX-T 3.2.x | Standard Support (active) |
| NSX (formerly NSX-T) 4.x | Standard Support (active, Broadcom branding) |
The NSX-T Migration Problem: Why Organisations Are Still Running NSX-V
Technical Blockers
NSX-V uses vSphere Distributed Switches (VDS) and VXLANs; NSX-T uses Geneve tunnels (TEPs) and N-VDS (or VDS 7.0+). Migration is not in-place upgrade — it requires new transport zones, new logical segments, new routing topology. Dual-stack running (NSX-V and NSX-T simultaneously) is complex and not supported by VMware/Broadcom.
Change Freeze Restrictions
Regulated industries (banking, healthcare, utilities) have 6-12 month change freeze windows during which core infrastructure cannot be migrated.
Cost Barriers
NSX-T/NSX 4.x licensing is dramatically more expensive than NSX-V SnS. Under Broadcom's 2024 VCF bundling, NSX is only available as part of VCF (VMware Cloud Foundation) for new purchases — no standalone NSX subscription available to existing NSX-V perpetual customers without taking VCF. This means an NSX-V to NSX migration now comes with a forced VCF platform commitment.
What Does "End of Support" Mean for NSX-V in Practice?
Post-EOS NSX-V Realities
No new patches or bug fixes. No new CVE/security patches (critical for network virtualisation infrastructure), no new platform certifications (vSphere 7.0 U3+ compatibility issues emerging), no support tickets accepted by Broadcom/VMware support.
What Still Works
NSX-V continues to function — distributed firewall rules, logical switches, DLR/ESG topologies run without vendor involvement. The risk is unpatched CVEs and no recourse for novel failures.
Extend NSX-V Life Without Broadcom's VCF Trap
Third-party support keeps NSX-V operational, patched, and compliant. 65% lower cost than Broadcom.
Third-Party Support for NSX-V: What It Covers
GoVendorFree's third-party support (TPS) covers:
- NSX for vSphere 6.4.x (all sub-releases)
- NSX Manager / NSX Controllers / NSX Edges
- Distributed Logical Router (DLR) and Edge Services Gateway (ESG)
- Distributed Firewall (DFW) rule management and troubleshooting
- vSphere Distributed Switch (VDS) underlying layer
- VXLAN overlay network
- Integration with vCenter
- NSX-V REST API
- CVE assessment and mitigating controls (where patches unavailable, we provide documented risk and compensating controls)
- NSX-V to NSX-T migration planning (included in TPS engagement)
Cost Model: Four Environment Sizes
| Environment Size | Infrastructure Scale | Broadcom SnS Equiv. | TPS Cost | Saving |
|---|---|---|---|---|
| Small | 50 NSX-V hosts, 500 VMs | £85K/yr | £30K | 65% |
| Medium | 200 hosts, 2,500 VMs | £340K | £119K | 65% |
| Large | 600 hosts, 8,000 VMs | £1.02M | £357K | 65% |
| Enterprise | 1,500+ hosts, 20,000+ VMs | £2.55M | £880K | 65% |
The Broadcom VCF Bundling Trap for NSX Customers
Broadcom's strategy since 2024: no more standalone NSX subscriptions. If you want NSX (T/4.x) support, you must take VCF. VCF includes vSphere, vSAN, NSX, and Aria Operations. For an organisation that wants NSX but already has a different hypervisor arrangement, VCF is a forced multi-product purchase.
GoVendorFree's TPS on NSX-V avoids this entirely — you stay on NSX-V, your existing vSphere environment remains untouched, and you pay for only the support you actually need.
Strategic Options Grid
Option A: Migrate to NSX-T/NSX 4.x + VCF Bundle
High cost, 12–24 month migration project, Broadcom dependency, no standalone NSX option
Option B: Third-Party Support on NSX-V, Extend Life 3–5 Years
65% cost reduction, no migration disruption, time to plan deliberate NSX-T migration on your terms
Option C: Alternative Network Virtualisation
Nutanix Flow, Arista CloudVision, Open vSwitch — viable for orgs committed to leaving VMware/Broadcom ecosystem entirely
Option D: VMware VCF Migration with GoVendorFree TPS Bridge
TPS during migration planning phase, then selective VCF adoption for NSX-T only
Which Option Is Right for Your Organisation?
Let our experts assess your NSX-V environment and help you plan the cost-optimal path forward.
Sector Angles: Why TPS Makes Sense in Your Industry
Financial Services / Banking
DORA (Digital Operational Resilience Act) compliance deadline Jan 2025 has made network infrastructure change freezes stricter. NSX-V environments locked for DORA resilience testing cannot be migrated simultaneously. TPS provides a compliant, supported path during DORA implementation.
NHS / Healthcare
NHS Cyber Security Strategy 2023–2030 requires documented compensating controls for EOS software. GoVendorFree provides the compensating controls documentation required by NHS DSPT (Data Security and Protection Toolkit) for NSX-V environments.
Critical National Infrastructure
Energy, water, telecoms OT environments where network virtualisation runs SCADA-adjacent systems. Zero tolerance for unplanned outages means NSX-V migration is a multi-year project with full change control. TPS keeps the environment supported meanwhile.
NSX-V to NSX-T: Planning the Migration Correctly
Five-Phase Migration Path
- NSX-T Parallel Deployment — Build NSX-T fabric alongside existing NSX-V
- Workload Migration by Segment — Move non-critical workloads first
- Firewall Rule Translation — DFW policies to NSX-T DFW (syntax differences)
- Edge Topology Rebuild — ESG → Tier-0/Tier-1 gateway reconfiguration
- NSX-V Decommission — Drain and remove NSX Manager and Controllers
GoVendorFree's TPS engagement includes migration planning as standard — we want your NSX-V dependency to end on your terms, not Broadcom's.
Ready to Plan Your NSX Migration?
Download our Migration Playbook or schedule a 30-minute NSX strategy session.