OpenText for SAP 21.4 maintenance ends 1 Nov 2026: ADA, Core Archive and Extended ECM

Oct 13

OpenText's public Product Support Lifecycle page gives three SAP-side releases the same Current Maintenance end date, 1 November 2026:

Archiving and Document Access (ADA) for SAP Solutions 21.4
Core Archive for SAP Solutions 21.4
Extended ECM for SAP Solutions 21.4

All three were released on 1 November 2021, so this is five years to the day. They're three different products, usually with three different owners. Don't let a shared date turn them into one project.

Nothing switches off on 2 November. The support terms change.

What changes after Current Maintenance. OpenText's Protect Software Maintenance Program Handbook describes Current Maintenance as a fixed period from the release date, in most cases 60 months from general availability. During it you get support requests, product patches and releases, and error reporting. After it, a release moves to Sustaining Maintenance, where "no new Product Patches and Releases are released for general use." The handbook also says OpenText has no obligation to deliver a resolution unless you're on a Current Maintenance release with the latest relevant updates, and that "migration to a Current Maintenance Release may be required in order to address an issue."

There is a paid bridge. OpenText's Extended Support Handbook offers Extended Support for most solutions, for up to two years from the date a release enters Sustaining Maintenance, with a 12-month minimum term. It covers new production-down bugs and critical patches, security included, delivered only on the most recent update of that release. It adds no new functionality.

Where each product can go next. The same lifecycle page shows the landing spots:

ADA for SAP: 26.4, released 1 October 2026, runs to 31 October 2031. 26.2 runs to 30 April 2031.
Core Archive for SAP: 26.2, the newest row, runs to 30 April 2031.
Extended ECM for SAP: the newest row under that name is 22.4, to 1 December 2027. OpenText lists the product's later releases under the OpenText Content Management name, so a horizon past 2027 means planning against that entry.

Look at the 22.x rows before you settle on one. For all three products they end during 2027: ADA 22.2 and 22.4 on 1 June and 1 October, Core Archive 22.2 and 22.4 on 1 April and 1 November, Extended ECM for SAP 22.2, 22.3 and 22.4 in June, September and December. A move from 21.4 to 22.x buys about a year. That can be the right call for a short bridge. It shouldn't happen by accident.

SAP's clock runs alongside. SAP gives mainstream maintenance for SAP Business Suite 7 core applications, ECC 6.0 included, until the end of 2027, with optional extended maintenance to the end of 2030 at a premium of two percentage points. A company still on ECC with 21.4 archiving underneath now has two clocks fourteen months apart, and the OpenText one ends first. We keep both sets of dates side by side on our OpenText for SAP maintenance calendar.

Who runs the check. We'd give it to the SAP Basis or content platform lead, with finance's renewal owner in the room. That pairing is our recommendation, not OpenText's. The check is short:

Which release and patch level of ADA, Core Archive and Extended ECM for SAP is in production today?
Does any of them carry the 1 November 2026 date?
If so, is the plan an upgrade, an Extended Support term, or a documented decision to run in Sustaining Maintenance for a while?
Which target release, and what is its Current Maintenance date next to your ECC or S/4HANA plan?
Any of those three plans can be defensible. The one that hurts is learning the release number during a severity-one ticket.
If you want a second pair of eyes on that check, we're glad to be them.