If your organisation links SAP to OpenText for business workspaces, document access or archiving, there is a date worth putting in the plan now. On 1 November 2026, version 21.4 of three OpenText for SAP products reaches the end of Current Maintenance.
This does not mean the software stops working. It does change what support you can expect, and it is a good prompt to decide your next step deliberately rather than by default.
What is changing and when
According to OpenText’s own product lifecycle table, Current Maintenance for version 21.4 of the following products ends on 1 November 2026:
- OpenText Extended ECM for SAP Solutions
- OpenText Archiving and Document Access for SAP Solutions
- OpenText Core Archive for SAP Solutions
The lifecycle table does not publish any later Sustaining or Extended Support dates for these versions. Those phases are governed by OpenText’s maintenance and extended support handbooks. OpenText’s Extended Support Handbook describes Extended Support as an addition to standard maintenance fees, available for up to two years after a release enters Sustaining Maintenance, with a 12-month minimum term and cover focused on critical issues. Terms and eligibility are set by OpenText, so ask your OpenText contact early.
What Current Maintenance ending actually means
OpenText supports each release in phases. In plain terms:
- Current Maintenance. Customers paying maintenance receive technical support, software updates and defect support.
- Sustaining Maintenance. Online resources remain available, but technical support and defect support stop.
- Extended Support, and later Limited Extended Support. Paid options that keep some support in place for older releases.
So “end of maintenance”, as it is often written, means the end of Current Maintenance. Your 21.4 system will keep running on 2 November. What changes is that new problems on that version are no longer covered by the standard maintenance you may be relying on, unless you arrange something else.
For a platform that holds archived SAP documents, invoices or business workspaces, that is a risk question for operations, compliance and budget holders, not only for the technical team.
Who is affected
Any estate running version 21.4 of Extended ECM for SAP Solutions, Archiving and Document Access for SAP Solutions, or Core Archive for SAP Solutions.
These products sit on top of OpenText Content Server and Archive Center. In practice, any decision you make about them also touches the underlying platform and its database. It is worth checking the versions of those layers at the same time.
Your options
There are three broad routes. None is right for everyone, and many organisations will combine them.
1. Upgrade to a release in Current Maintenance. This keeps you on the standard support model. Check the lifecycle table for the target version before committing, because later versions have their own end dates. A short hop may only buy months, so choose the target with your wider roadmap in mind.
2. Use Extended Support as a bridge. If an upgrade cannot happen before 1 November, Extended Support may keep some support in place while you plan. As the Extended Support Handbook sets out, it is an addition to standard maintenance fees, with a 12-month minimum term and cover focused on critical issues. Terms and eligibility are set by OpenText, so ask your OpenText contact early.
3. Plan modernisation. If a larger change is coming anyway, the 21.4 date can be the trigger for a properly scoped programme rather than a series of short upgrades. That plan should cover the SAP side, the OpenText for SAP products, and the Content Server and Archive Center platform underneath.
| Route | What it buys | What it costs in effort | What to check |
|---|---|---|---|
| Upgrade | Keeps you on the standard support model. | An upgrade that also touches Content Server, Archive Center and the database underneath. | The target version’s own dates in the lifecycle table. A short hop may only buy months. |
| Extended Support | Keeps some support in place, focused on critical issues, while you plan. | An addition to standard maintenance fees with a 12-month minimum term, arranged with OpenText. | Terms and eligibility with your OpenText contact, early and in writing. |
| Modernise | One properly scoped programme rather than a series of short upgrades. | A plan covering the SAP side, the OpenText for SAP products and the platform underneath. | That OpenText dates and your ECC or S/4HANA milestones sit on one timeline. |
Two clocks: OpenText dates and your SAP timeline
Many SAP teams are focused on SAP’s own timeline: the move from ECC to S/4HANA. The OpenText products that link and archive SAP documents run on a separate clock.
SAP’s own maintenance strategy has mainstream maintenance for SAP ERP 6.0 (ECC) with enhancement packages 6 to 8 ending on 31 December 2027, with optional extended maintenance, at additional cost, to 31 December 2030. Your S/4HANA plan and your OpenText for SAP versions need to sit in one plan. Otherwise, you risk upgrading the OpenText layer twice, or finding that a supported SAP target depends on an OpenText version you have not budgeted for.
With 2027 budgets being set now, this is a good moment to put both clocks side by side.
A short planning checklist
- List your versions. Every OpenText for SAP product, plus Content Server, Archive Center and the database underneath. Our article on assessing an estate on an older version sets out what an inventory should record.
- Check each against the lifecycle table. Note which support phase each is in today and the next date that applies.
- Line up the two clocks. Put OpenText dates and your ECC or S/4HANA milestones on one timeline.
- Decide the route for 21.4. Upgrade, Extended Support as a bridge, or a modernisation plan, with a named owner.
- Ask about Extended Support early. Get terms in writing if you may need them.
- Check your licence before and after any upgrade.
For a wider look at the estate while you are listing versions, the 15 OpenText estate health checks are a self-check you can run on your own.
Need a second view?
If you would like a second view on your OpenText for SAP versions and options, book a 45-minute continuity check call.
Frequently asked questions
Related reading