VMware SRM 8.8 End of Life October 2025: Maintenance Options

VMware Site Recovery Manager 8.8 Reaches End of Life October 2025: Assessing Your Options

VMware Site Recovery Manager (SRM) version 8.8 reaches end of life on October 11, 2025 — approximately nine months from today. This is not a long-term support (LTS) release, and end of active support coincides with end of life. The latest update in this line is 8.8.0.3. For details on VMware’s broader lifecycle, see the vendor page.

With nine months to plan, IT teams have three realistic paths forward: upgrade or migrate to a supported version, purchase vendor extended support (if offered), or transition to third-party maintenance. Each option carries a different cost profile, risk level, and timeline, and the right choice depends on your environment’s current state and future direction.

Option 1: Upgrade or Migrate to a Supported Version

What it entails — Moving to the next major release of SRM (typically requiring a new license) or migrating to an alternative DR orchestration platform. This path ensures continued vendor support and full compatibility with the latest VMware vSphere releases.

Cost profile — New licensing fees plus internal or external labor for planning, testing, and cutover. The total cost can be significant if the upgrade exposes hardware or software dependencies that must also be addressed.

Risk — Upgrade projects carry inherent risk of regression or downtime. Nine months may be enough for a well-scoped migration, but tight if your environment includes complex multi-site configurations or custom integrations.

Timeline — Requires immediate action. Sizing, testing, and dry runs need to begin within the next few months to allow for a rollback if issues arise. Certification with your current vSphere build must be verified.

Suits — Environments under active development where new features are valuable, or where auditing policies require vendor-supported software.

Option 2: Vendor Extended Support (if available)

What it entails — Requesting a post‑end‑of‑life support contract directly from VMware. For non-LTS releases like SRM 8.8, extended support is not guaranteed and, when offered, typically covers only critical security patches for a limited period (often one year or less).

Cost profile — Premium pricing that can reach 50–100% of the original annual maintenance fee. The contract may also limit support to break-fix scenarios, excluding feature updates.

Risk — Low in the short term, but the clock restarts in 12–18 months, requiring another migration decision. Additionally, vendor extended support does not cover issues caused by changes to underlying infrastructure that VMware considers outdated.

Timeline — Start the conversation now. Contract negotiations can take weeks. If extended support is not offered, this path is unavailable.

Suits — Organizations that need a short bridge (e.g., during a data center consolidation) and are willing to pay a premium to avoid an immediate upgrade.

Option 3: Third-Party Support

What it entails — Engaging a third-party maintenance provider (like 3rd Party Support) to continue supporting SRM 8.8 after October 11, 2025. Support includes troubleshooting, bug fixes, and security patches developed independently of the vendor.

Cost profile — Typically 30–60% lower than vendor maintenance. There are no upgrade costs; the existing licenses remain valid. Pricing is predictable and often locked for multi-year contracts.

Risk — Minimal for stable, non-development environments. Third-party support does not provide new features or compatibility with future vSphere versions, but it keeps the current deployment running safely. Security patches are backported to the 8.8 codebase.

Timeline — No immediate pressure. You can transition to third-party support at any point before or after October 11, 2025. Implementation is administrative — no software changes required.

Suits — Stable workloads that just need to keep running. Environments where the DR orchestration is proven and unlikely to be modified. Organizations with budget constraints that want to defer a full upgrade.

Decision Checklist

Before choosing a path, ask these questions:

• Is the SRM 8.8 environment stable and unlikely to need new features in the next 2–3 years?
• Do you have an upcoming vSphere upgrade that will break SRM 8.8 compatibility anyway?
• Can you absorb the labor cost of a full upgrade within the next six to eight months?
• Is your organization willing to pay a premium for vendor extended support if it is available?
• Are compliance or audit requirements satisfied by a recognized third-party support provider?

Criterion	Upgrade / Migrate	Vendor Extended Support	Third-Party Support
Cost (5-year TCO)	High	Highest	Low–Medium
Implementation Risk	Medium–High	Low	Low
Timeline Urgency	High	Medium	Low
Best for	Active dev / compliance	Short bridge only	Stable, long-life workloads

Next Steps

With nine months until end of life, you have time to evaluate each path carefully. Third-party support offers a no‑upgrade, cost‑effective option for keeping SRM 8.8 operational long after VMware stops supporting it. To discuss whether your environment is a good fit, contact our team.