End of maintenance 2030: what falls away for ECC systems on third-party databases or Java

What happened

In the SAP News Center on 7 October 2026, SAP explains that when optional extended maintenance for SAP Business Suite 7 ends on 31 December 2030, its existing agreements with major database vendors and its support arrangements for Java under SAP NetWeaver AS Java 7.5 also expire, so that systems on another vendor's database can only be supported to a limited extent afterwards.

Who is affected

Companies whose ECC system does not yet run on SAP HANA, and everyone running applications on SAP NetWeaver AS Java. According to SAP, the maintenance dates themselves are unchanged: mainstream maintenance runs until 31 December 2027, optional extended maintenance until 31 December 2030. The article clarifies what will no longer be possible in customer-specific maintenance afterwards. Among other things, the article names kernel patches and kernel security patches for environments with a third-party database, and possibly also downloads of the associated tools for administration, backup, upgrade and migration. This makes it a topic not only for IT but also for the CFO organisation, which has to assess running a core system without this safeguard.

What to do

According to SAP, a system conversion from Business Suite 7 on a third-party database to S/4HANA or SAP Cloud ERP is only available until the end of 2030; after that, only a new implementation remains. For the transition option, which SAP intends for the largest and most complex customers from 2031 to 2033, the system must have moved to SAP ERP, private edition, on SAP HANA before 31 December 2030, and further eligibility requirements apply; according to the article, it does not cover Java-dependent capabilities. We would therefore clarify three questions now: which database the production systems run on, which processes depend on Java components, and which path is realistic once testing, cut-over and stabilisation are counted backwards from the deadline. The SAP Notes linked in the article belong in this review.

Our assessment

The article comes from SAP and combines the clarification with the recommendation to move to SAP Cloud ERP by the end of 2030. The technical facts should be assessed separately from that. In our view, for systems on third-party databases the date by which a decision must be made effectively moves forward: anyone who wants to keep conversion open as a path needs not just a decision before the end of 2030, but a completed project. SAP names the move to SAP HANA as an option in select cases, explicitly without extending maintenance and not as the recommended long-term path. For programme leadership this means not leaving the platform question to IT alone, but deciding it together with the business and finance as part of the transformation plan.