VMware SRM 8.7 EOL October 2025: Your 3 Options

Understanding the Deadline and What It Means

VMware Site Recovery Manager (SRM) 8.7 reaches end of life (EOL) on October 11, 2025. This is a hard stop: end of active support coincides with the EOL date. SRM 8.7 is not a long-term support (LTS) release, and the latest available patch-level is 8.7.0.4.

With roughly nine months remaining, procurement leads and infrastructure managers should begin assessing which of the three standard paths fits their environment. Each path has distinct cost, timeline, and operational implications.

---

Option 1: Migrate or Upgrade to a Supported Version

Best for: Environments under active development or where new features justify the migration cost.

Cost Profile

• Software licensing: You likely already hold licenses for SRM (it is bundled with VMware vSphere Enterprise Plus or sold separately). An upgrade to a supported version may require a new support contract or subscription if your current plan expires.
• Labor: Migration labor is moderate to high. You will need to plan downtime, test DR procedures in the new version, and possibly validate compatibility with your vCenter and ESXi versions.
• Risk: Moderate. Upgrades within the same major product line are generally safe, but SRM upgrades require careful sequence (vCenter first, then SRM, then re-register protection groups). Test in a non-production environment first.

Timeline

Given nine months, you can comfortably complete a migration if you start the planning phase now. A typical upgrade project for a mid-size environment takes 6–10 weeks from requirements to cutover. Factor in at least two months for testing, including a full failover drill.

Suitability

• High-change environments that need the latest SRM features (e.g., improved orchestration, cloud-integrated recovery).
• Compliance-driven organizations that mandate vendor-supported software for audit requirements.

---

Option 2: Purchase Vendor Extended Support (If and When Available)

Best for: Environments on a strict no-migration mandate, where the cost of extended support is accepted as a temporary bridge.

Cost Profile

• Pricing: VMware has historically offered a limited extension for some products (typically a post-EOL support program), but SRM 8.7 may not qualify. As of this writing, no official extended support option has been announced for this version. Relying on this path carries execution risk.
• Costs: If an extension becomes available, it is usually priced at a premium (125–150% of annual support). Premium support does not include new features or bug fixes — only security patches for critical vulnerabilities.
• Risk: High uncertainty—if VMware does not offer an extension, you have wasted time planning for it.

Timeline

If you choose to wait for an extension announcement, you compress the remaining time to execute fallback options (upgrade or third-party support). Should no extension materialize, you will have less than six months to choose an alternative.

Suitability

• Stable, air-gapped environments where SRM 8.7 is working reliably and no new software changes are planned.
• Stopgap measure for teams that need another 12 months while planning a broader DR architecture refresh in 2026.

---

Option 3: Move to Third-Party Support

Best for: Stable workloads that need to keep running safely past EOL, without the cost or disruption of an upgrade.

Cost Profile

• Pricing: Third-party maintenance typically costs 40–60% less than an extended vendor support contract. Vendors such as 3rd Party Support provide coverage for security patches and break-fix support without requiring an upgrade.
• Labor: No migration labor is required. Teams continue managing SRM 8.7 as they do today.
• Risk: Low. Third-party support covers the same run-book scenarios as vendor support (incident resolution, critical patch backports). However, you cannot call VMware—support comes from the third-party provider.

Timeline

You can transition to a third-party support provider immediately; no preparation beyond signing a contract and establishing a support contact is needed. Coverage starts on October 12, 2025 seamlessly.

Suitability

• Mature environments that function well on SRM 8.7 and have no feature requirements from newer versions.
• Budget-sensitive organizations that want to defer a costly vSphere or SRM upgrade for another 1–3 years.
• Multi-vendor shops already using third-party maintenance for other hardware or software, who can consolidate support vendors.

---

Decision Checklist

Use this short list to determine which path fits your environment:

Question	Upgrade?	Vendor EUS?	Third-Party?
Are you planning a vSphere/DR architecture change in 2025?	Yes	No	No
Do you need new features from a newer SRM version?	Yes	No	No
Is your team allowed to run unsupported software (with vendor waiver)?	No	Yes	Yes (with third-party)
Do you have a strict no-migration policy for the next 12 months?	No	Maybe	Yes
Is cost the primary driver?	No	No	Yes

---

Your Next Step

Nine months is sufficient time to execute any of the three options — but only if you decide now. For teams leaning toward third-party support, we can help you transition smoothly before the October deadline.

Contact us to discuss coverage for your SRM 8.7 environment or visit our VMware lifecycle page for more details on the product's end-of-life dates.

Lifecycle data sourced from endoflife.date/vmware-srm.