SAP says customers running certain legacy Business Suite 7 and NetWeaver systems on third-party databases or Java should plan for a significant change: after 31 December 2030, some support arrangements will end and SAP will no longer provide comprehensive support for those dependencies. The deadline is more than four years away. The migration choices are not equally roomy, though, and some need to be completed before it arrives.
SAP Watch analysis
What happened
SAP says Business Suite 7 mainstream maintenance remains available through 31 December 2027, followed by optional extended maintenance through 31 December 2030. At the end of that extended period, SAP’s current reselling and support arrangements for third-party databases in the affected legacy environments are scheduled to end. Its support arrangements for Java 8/JEE5 used with SAP NetWeaver AS Java 7.5 are also scheduled to conclude.
For affected third-party database systems, SAP says the integrated support path will end, including database-specific corrections. After 2030, customer-specific maintenance will not provide comprehensive support for database or Java issues; SAP also says it may no longer provide related tools and downloads, including kernel security patches for third-party database environments. SAP says a conversion from Business Suite 7 on a third-party database to SAP S/4HANA or SAP Cloud ERP will be available only before the end of 2030. After that, it says, only new-implementation, or “greenfield”, transition scenarios will be possible.
Why it matters
This is a planning deadline with technical consequences, not simply a change to a maintenance calendar. Organisations that rely on the affected database or Java arrangements may need to choose and execute a transition before the support agreements end. SAP warns that an issue arising after 2030 may not be resolvable within the support available for those environments.
The company recommends moving towards SAP Cloud ERP and its Autonomous Suite. It also describes a time-limited transition option for some large, complex customers: eligible systems must move to SAP ERP, private edition on SAP HANA before 31 December 2030, and the option does not support Java-dependent capabilities. Moving a system to SAP HANA can remove the third-party database dependency, SAP says, but does not extend maintenance or remove its limitations.
Our read
The useful news is the detail behind a date many customers may already have on their calendars. The sharper constraint is that customer-specific maintenance is not a like-for-like replacement for the support arrangements ending in 2030, and some migration routes close at that point.
SAP is also steering customers towards its own cloud services, so organisations should treat its recommendation as the vendor’s preferred route, not as a neutral comparison of every alternative. The sensible next step for affected operators is to identify which systems depend on third-party databases or Java, then map the available transition options against their own timelines.
What to watch
- Which systems and database or Java dependencies are covered by SAP’s guidance and relevant SAP Notes.
- Eligibility and practical limits for the transition option, particularly for Java-dependent capabilities.
- Whether SAP changes the stated maintenance dates or publishes further technical transition guidance.
Discussion spark: Should companies start moving away from legacy SAP systems now to preserve their options, or wait until they have a clearer view of the alternatives and costs?
Sources and evidence
not affiliated with or endorsed by SAP