Can We Let VMware Support Lapse and Buy a VVF Subscription Later?

The question behind the deadline

Licensing deadlines bring their own kind of anxiety, and it's different from the usual "budget approval" stress. It's more strategic and more political, and this time the question was about timing rather than pricing.

A team sitting on 15-year-old perpetual on-prem VMware licenses is staring at the calendar. Support is about to expire, and they already have a quote in hand for VMware vSphere Foundation (VVF). But there's talk of M&A activity in the background. Deals take time, approvals stall, and budgets freeze, and nobody wants to commit to a subscription model if the company's direction might shift in a few months.

So the question becomes: if we let our perpetual support lapse now, can we come back later and activate that VVF subscription when things settle down? It sounds simple, and it isn't.

Start with what's changed. Traditional perpetual support renewals aren't really a thing anymore. Once your support term ends, you don't "renew" perpetual support the way you used to. You either run unsupported or move to a subscription model like VVF or VCF.

One response cut straight to it: at the end of your support term, you either go unsupported or purchase a new VVF or VCF subscription that replaces your legacy perpetual licenses. That's the fork in the road, stated without any drama, and the nuance starts right after it.

What you keep after support expires

Going unsupported doesn't put you out of compliance. If you've already paid for your perpetual licenses, you still own the rights to run those versions, and you're entitled to patches released during your active support window. You can download them before the deadline and apply them later. There's nothing shady about that; it's how perpetual licensing has always worked.

The boundary is this: don't install versions released after your support expiration date. Once support ends, your upgrade window freezes in time.

That's a big psychological shift. For years, IT teams assumed that staying under support was the responsible move. Now some are openly considering running production environments unsupported for months, maybe longer, while waiting for corporate strategy to settle, which tells you how much things have changed.

Reseller pressure vs licensing reality

There's also a strong undercurrent of skepticism about reseller pressure. One voice in the conversation warned that resellers may "say all sorts of BS essentially threatening you," but as long as you're not exceeding your licensed entitlements and you're not installing versions beyond what was available at the end of support, you're within your rights.

That comment says a lot about the mood right now. Trust between customers and licensing channels isn't exactly at an all-time high, and there's a sense that urgency is sometimes manufactured and fear sometimes leveraged.

This particular question, though, is about flexibility more than scare tactics. If you let support lapse, can you still buy VVF later? The uncomfortable answer is probably, but not necessarily on the same terms.

VVF is a subscription model, and it's generally treated as a net-new purchase instead of a traditional renewal conversion. If you let your support expire and come back later, you're likely just buying a new subscription at whatever pricing and policies exist at that time, and nobody can guarantee what those will be.

Will Broadcom still be offering VVF in the same form? Will pricing stay where it is? Will there be incentives for customers transitioning from perpetual, or a reinstatement-style premium baked into the deal?

Can you buy VVF later?

There's speculation that if you lapse and come back, you might simply purchase net-new VVF subscriptions, possibly at a higher price that reflects a "reinstatement" dynamic. Nobody has confirmed that as policy; it's educated guessing based on how vendors have historically handled lapsed agreements.

The M&A timing complicates everything. If your organization is mid-acquisition or divestiture, locking into a subscription right now might create accounting or structural headaches. You might not even know what your infrastructure footprint will look like six months from now, so committing today could mean overbuying or underbuying.

The temptation is obvious: let it lapse, run unsupported, wait for clarity, and re-engage later. That strategy isn't reckless, but it isn't frictionless either.

Running unsupported means no official ticket escalation, no new patches, and no security updates beyond what you already have access to. If a critical vulnerability drops after your support date, you're stuck unless you've moved to subscription. Leadership needs to own that risk calculation.

It also takes operational discipline. Before support expires, you'd want to upgrade to the latest patch level available under your entitlement, download everything you might conceivably need, and document and archive it, with clean install media and offline patch bundles.

One commenter put it plainly: you're entitled to patches up to the support date, so just manually download them before the end of support. Simple enough, but it requires planning.

Operational safeguards during a lapse

Third-party support is another angle. Some organizations look at firms like Park Place for support on legacy perpetual environments. That doesn't give you access to new VMware patches, but it can provide break-fix assistance and operational guidance. For certain industries, especially those less bound by vendor-backed support requirements, that can buy time. It won't replace subscription access if your roadmap requires version upgrades.

What stands out about this whole discussion is how measured it feels. No one is panicking or claiming that letting support lapse will cause instant chaos. The tone is pragmatic: "You can go unsupported." "You can buy VVF later." "Just don't install versions beyond your entitlement." That's sober risk assessment.

It also points to something bigger. VMware customers are dealing with structural uncertainty on top of pricing changes, and subscription models change the psychology of infrastructure ownership. Perpetual licensing felt stable because you owned something and support was layered on top. Subscription flips that, so access and entitlement are now intertwined.

The strategic tradeoff

So when someone asks, "Can we let it lapse and come back later?" they're really asking how reversible the decision is.

Technically, it appears reversible. There's no clear indication that letting perpetual support lapse permanently blocks you from buying VVF later, and you're not blacklisted for stepping away. Economically and strategically, it's harder to predict. Pricing may shift, packaging may change, and product bundles may evolve, and you'd be buying into whatever the future looks like instead of the quote sitting on your desk today. Leadership needs to understand that part.

Letting support lapse is a lever. It buys time and preserves optionality during M&A turbulence, but it trades predictability for flexibility. In stable times predictability wins, and in uncertain times flexibility might.

The smartest move right now is probably neither rushing to renew out of fear nor casually ignoring the deadline. Document everything and lock down your final supported patch level. Get written clarification from your reseller about how VVF would be treated post-lapse, and find out whether incentives expire alongside your support term. Above all, tie this decision to business reality instead of IT comfort alone, because six months from now, when the M&A dust settles, the last thing you want is to discover that your "we'll deal with it later" plan became more expensive than anyone anticipated.

Letting it lapse is neither catastrophic nor neutral. Think of it as a calculated pause, and like any pause in enterprise IT, what you do before and after it matters more than the moment itself.