VMware SRM 8.6 End of Life: Oct 11, 2025 – Time to Act
With the end-of-life date for VMware Site Recovery Manager (SRM) 8.6 set for October 11, 2025, IT organizations have about six months to plan and execute a migration. This isn’t a long-term support (LTS) release, so there’s no extended support window. The latest build in the 8.6 line is 8.6.0.2, but that fix pack doesn’t change the deadline. If you’re still running SRM 8.6, the clock is ticking — and the window for a comfortable move up to a supported version is closing fast.
A Realistic Migration Timeline (Worked Backwards)
A straightforward SRM upgrade from 8.6 to a newer supported version typically requires three to four months when done methodically. Break that down:
- Procurement & licensing (2–3 weeks): Getting purchase approvals, ordering new licenses (or confirming eligibility under existing VMware agreements), and waiting for delivery. If your organization has quarterly budget cycles, that alone can eat a month.
- Lab testing & validation (4–6 weeks): Deploying the target SRM version in a non-production environment, testing failover/failback workflows, verifying compatibility with vCenter and storage replication adapters, and validating recovery plans. SRM upgrades touch recovery SLAs, so testing can’t be rushed.
- Change freeze windows (variable): Many enterprises have change freezes during fiscal year-end, quarter-end, or holidays. If your freeze falls between July and September, that’s three weeks or more of blocked time.
- Production cutover & rollback planning (2–3 weeks): Scheduling the upgrade, communicating with stakeholders, running the cutover, and documenting rollback steps.
Working backwards from October 11, 2025, you’d need to start the procurement and lab phase by early July at the latest — and that’s assuming no delays. If you’re reading this in mid-April 2025, you have roughly 11 weeks before that July start date. Any slip in testing or a surprise change freeze means you’ll be cutting it very close to the deadline.
The Risks of Running Past October 11, 2025
Once SRM 8.6 reaches end of life, VMware will no longer provide:
- Security patches for vulnerabilities discovered after that date.
- Bug fixes for stability or performance issues.
- Technical support for any SRM 8.6-related incident.
Running an unsupported disaster recovery platform is a compliance and operational risk. If a zero-day vulnerability is disclosed in November 2025, your SRM instance will be exposed with no vendor remedy. Similarly, if a configuration error causes a failover failure, you’ll have no vendor escalation path. Auditors and insurers may also flag unsupported software in critical DR infrastructure.
How Third-Party Support Removes the Deadline Pressure
Locking in third-party maintenance for VMware SRM 8.6 now changes the equation. Instead of racing the calendar, you gain:
- Continued security patches and bug fixes for the 8.6 release, provided by a third-party engineering team that reverse-engineers vendor updates.
- Access to break-fix support at all hours, so your DR environment remains reliable even after the vendor’s support ends.
- Freedom to migrate on your own schedule — you can take an extra quarter (or more) to test a new SRM version, align with a hardware refresh, or wait for a stable major release.
- The option to stay on 8.6 permanently if the version meets your needs. Many IT teams prefer to freeze a known-good SRM build rather than chase every vendor upgrade cycle.
Third-party support covers the same SRM 8.6 environment you already have, including the latest 8.6.0.2 build. There’s no need to upgrade, re-license, or reconfigure. You simply sign a maintenance agreement and the deadline becomes irrelevant.
Next Steps for Your Team
If your organization runs VMware SRM 8.6, the next six weeks are the realistic window to evaluate options. You can either begin the migration process immediately — with all the procurement, testing, and change-management pressure that entails — or secure third-party support and eliminate the deadline altogether.
To learn more about supported lifecycle dates for VMware products, see our VMware software lifecycle page. For a confidential discussion of your SRM 8.6 transition options, contact our team today.
Get support for what you run
How we can help
Keep it supported after end of life
The vendor's date doesn't have to be yours. Our engineers keep VMware Site Recovery Manager 8.6 running after official support ends — independent third-party support that covers most operational issues, typically at 40-70% below the last renewal quote.
VMware software support →Migration services
When you do decide to move, we plan and execute the migration. Your current environment stays under vendor support while your contract is active — and if the renewal lapses mid-move, our third-party support covers most issues until the last workload is off it.
Migration & hybrid cloud services →24×7 remote administration
Short on hands to run it day to day? Our NOC engineers monitor, patch and administer your environment around the clock — incident response included, at a fraction of the cost of an in-house night shift.
24/7 operations & remote administration →More EOSL Alerts
VMware Site Recovery Manager 9.0: EOL September 2027
VMware Site Recovery Manager 9.0 reaches end of life on September 17, 2027. Learn what that means for your budget, migration timelines, and third-party support
August 17, 2026
VMware Cloud Foundation 9.0 EOL September 2027
Plan your budget now: VMware Cloud Foundation 9.0 ends support Sept 17, 2027. Compare upgrade, vendor extended support, and third-party support costs to stay se
August 17, 2026
VMware ESXi 9.0 EOL September 2027
VMware ESXi 9.0 ends support Sept 17, 2027 – 13 months away. Plan next year's budget: compare migration costs with third-party support savings of 40–70%.
August 17, 2026