Extended Maintenance to 2030: A Bridge, Not a Destination

SAP has floated one further option for a narrow slice of its largest, most complex customers: a program called “SAP ERP, private edition, transition option,” announced in Q1 2025, that can push support out toward 2033 for select customers who sign a RISE with SAP agreement and commit to a joint roadmap. This is not a general-purpose escape hatch — it is aimed at organizations with landscapes complex enough that even 2030 isn't realistic, and it comes with real commercial commitments attached, not a quiet extension for anyone who asks.

The organizations most likely to misuse extended maintenance are the ones who buy it as a strategy rather than a bridge — electing the extra three years with no migration program actually running underneath it. That is the scenario SAP's own language is clearly trying to discourage: extended maintenance is explicitly positioned as a bridge for customers who cannot complete their transition in time, not as a long-term alternative to moving to S/4HANA or SAP's cloud ERP at all. An organization that treats 2030 the way it once treated 2027 — as a deadline that will surely get pushed again — is repeating the exact mistake the industry has already made once.

There is also a cost dimension worth being honest about. A roughly 2-percentage-point surcharge sounds modest in isolation, but layered on top of several years of existing maintenance fees, on a system that is still not generating any of the efficiency or AI-enabled benefits SAP is now building exclusively into S/4HANA, it is money spent standing still rather than money spent moving forward. The better use of extended maintenance, for most