SRM 8.7 EOL October 11, 2025

The Real Deadline Is Sooner Than You Think

VMware Site Recovery Manager (SRM) 8.7 reaches end of life on October 11, 2025. This is not an LTS release, and the end-of-life date also marks the end of active support from VMware. With about six months remaining, the window for a comfortable migration is narrowing fast.

When you factor in procurement cycles, change freezes, and thorough testing, the actual deadline for starting your migration is much tighter than the calendar suggests.

Why the Window Is Shrinking

A typical enterprise migration from one SRM version to the next involves several time-consuming steps:

1. Procurement and licensing (2–4 weeks): Getting budget approval, placing orders, and receiving licenses.
2. Lab testing and validation (4–8 weeks): Verifying that the new version works with your existing vSphere and storage environments.
3. Change management and freeze periods (3–6 weeks): Many organizations have change freezes around holidays, end-of-quarter, or end-of-fiscal-year periods. October 11 lands in Q4, a common freeze window.
4. Staged production migration (2–4 weeks): Rolling the upgrade across multiple sites or clusters with rollback plans.

Working backwards from October 11, the latest you can start the migration is late June or early July 2025 — and that assumes no surprises.

What Happens If You Run Past End of Life

After October 11, 2025, VMware will no longer provide:

• Security patches
• Bug fixes
• Technical support for SRM 8.7
• Compatibility updates for new vSphere releases or storage arrays

Running an unsupported disaster recovery platform introduces several real risks:

• No security fixes: If a critical CVE is discovered in SRM 8.7 post-EOL, there will be no patch from VMware.
• Compatibility gaps: Future vSphere upgrades or storage firmware updates may break replication without warning.
• Compliance exposure: Auditors and regulators often require supported software for DR infrastructure.
• No vendor support: If SRM 8.7 fails during an actual disaster, VMware will not help recover it.

Third-Party Support Removes the Deadline Pressure

For organizations that cannot complete the migration by October 11 — or simply do not want to upgrade yet — third-party support can cover SRM 8.7 safely past end of life. With a third-party maintenance agreement, you get:

• Continued security patches and bug fixes for the unsupported version
• Technical support from engineers who know the product
• No forced upgrades on a vendor's timeline
• Full compliance coverage for audits

This approach lets you migrate SRM 8.7 on your own schedule, not VMware's. If you decide never to upgrade, third-party support can keep the current version running safely indefinitely.

Your Next Steps

If you are still on VMware Site Recovery Manager 8.7.0.4 or any earlier 8.7 build, start planning your migration now — or lock in support coverage before the October deadline passes.

• Review the VMware lifecycle resources on our site
• Map out your own timeline factoring in internal change freezes and testing windows
• Contact us to discuss third-party support options for SRM 8.7

The October 11 deadline is fixed. How you respond to it is still in your control.