Budget Planning: VMware SRM 8.8 End of Life October 11, 2025

What the October 2025 Date Means for Your Budget Cycle

If your organization runs VMware Site Recovery Manager (SRM) 8.8, October 11, 2025 is a date you need to account for in the next fiscal year. That is the official end-of-life (EOL) for version 8.8—and the last day you can receive any active support from VMware for this particular release. Because SRM 8.8 is not a long-term support (LTS) release, there is no extended support window built in. After that date, VMware will no longer provide bug fixes, security patches, or technical assistance for 8.8.

For most IT teams, this EOL lands squarely in the upcoming budget cycle. If you want to remain on a supported version, you will need to either upgrade to a newer SRM release or make an alternative support arrangement before October 2025. Planning now means you can include the cost—whether it is an upgrade project or third-party support—in the next budget request.

What Upgrading SRM 8.8 Typically Involves

Upgrading VMware Site Recovery Manager is not a trivial patch. Depending on your environment, it may require:

• Updating or upgrading your vCenter Server version to one that is compatible with the target SRM release.
• Upgrading ESXi hosts if the new SRM version requires newer hypervisor versions.
• Coordinating with any array-based replication partners, storage snapshots, or third-party adapters that integrate with SRM.
• Testing and re-validating recovery plans across your protected sites.

At typical enterprise scale—multiple sites, hundreds or thousands of VMs—these projects often take 6 to 12 months from planning to full cutover. That timeline is especially tight when the EOL is about 13 months away. Many teams find they cannot complete the migration before the deadline, either because of competing priorities, resource constraints, or the need to coordinate storage and network upgrades first.

Comparing the Costs: Upgrade, Extended Support, and Third-Party Support

When building your budget request, you have three main paths to consider:

1. Upgrade to a supported SRM version This is the vendor-recommended route. Besides the software itself, factor in:

• Internal engineering time for planning, testing, and deployment.
• Possible infrastructure upgrades (vCenter, ESXi, storage adapters).
• Training for your DR team if the new version changes workflows.
• Any professional services fees if you bring in VMware or a partner.

2. VMware extended support (if available) Because SRM 8.8 is not an LTS release, VMware does not offer an official extended support option. However, some vendors provide custom support agreements for specific customers—typically at a premium of 20-50% above the original annual maintenance cost. Securing this requires separate negotiations well before the EOL date. For most organizations, this is not a realistic path given the lead time.

3. Third-party support Third-party maintenance providers can cover SRM 8.8 for months or years past the vendor EOL. The benefits in a budget context:

• Cost is usually 40-60% less than current VMware support fees.
• No forced upgrade timeline—you stay on a known, stable version.
• Security patches and technical support are still provided (via the third party, not VMware).
• The contract structure is predictable and can be built into multi-year budgets.

What to Put in the Budget Request Now

For a budget request that covers the next fiscal year (starting before October 2025), include these elements:

• An upgrade scenario line item — estimated costs for software, labor, and infrastructure changes if you choose to move to a newer SRM version. If you have internal estimates from past upgrades, use those; otherwise, a benchmark of $X per protected VM or $Y per site is a reasonable placeholder.
• A third-party support scenario line item — the cost of a third-party support contract for SRM 8.8, typically priced as a percentage of your current VMware maintenance spend. This lets leadership see the financial trade-off clearly.
• A contingency line — if you opt to upgrade, add a buffer for unexpected delays or scope creep. If you choose third-party support, this contingency can be smaller.
• A timeline note — explicitly state that the EOL date is October 2025, and that beginning the upgrade after Q1 FY2026 may lead to an unplanned gap in support coverage.

Keep the request simple: two or three options with cost ranges, not a detailed project plan. Leadership wants to see that you understand the risk and have a cost-efficient path forward.

Get a Third-Party Support Quote Before Renewal Talks

Before you enter into renewal negotiations with VMware—or commit to a complex upgrade project—obtain a third-party support quote for your SRM 8.8 environment. This gives you a concrete benchmark to compare costs.

A third-party support contract covers all your current SRM deployments at any stage in the product lifecycle, including versions past EOL. The quote is typically fixed for the contract term, so it removes the uncertainty of annual price increases.

To get a no-obligation benchmark for your SRM environment, contact us for a quote. You can use the number to finalize your budget request, or to negotiate better terms on an upgrade path with VMware. Either way, the data helps you make an informed decision before the October 2025 deadline.