For certain SAP systems, 2030 marks not only the end of a maintenance phase: support and database tools may also be affected. It is crucial to assess your own system landscape in a timely manner
SAP Business Suite 7: What Food Companies Should Consider by 2030
A date on the calendar does not yet constitute a roadmap. Only once it is clear which systems are affected will this translate into a concrete need for action.
On October 7, 2026, SAP explained the potential consequences of the end of certain support agreements for SAP Business Suite 7 and SAP NetWeaver. Companies with specific third-party databases or Java dependencies, in particular, should review their system landscape. This is because, starting in 2031, not only may support terms change, but important database tools could also be affected.
The known maintenance data remains unchanged
The maintenance terms for SAP Business Suite 7 remain unchanged: Mainstream Maintenance runs through December 31, 2027. After that, Extended Maintenance is available as an option through December 31, 2030.
At the end of 2030, SAP’s current reseller and support agreements for certain third-party databases, as well as the support agreements for Java, will also expire.
The consequences will vary depending on the specific SAP landscape. The key factor is which systems and technical dependencies are actually in use.
Starting in 2031, access to database tools may also be restricted
For affected legacy SAP environments using third-party databases, SAP will no longer provide database-specific support once the agreements expire— not even for customers who originally licensed their database through SAP. Currently, SAP forwards tickets regarding database issues internally and directly to the database vendor’s team. This integrated support channel will be discontinued.
The restrictions may extend beyond this: SAP notes that support and downloads for related database tools may no longer be available for affected environments. These include, among others, database, administration, backup, upgrade, and migration tools.
This is important for planning. If a system is to be updated, migrated, or moved to a different technical platform at a later date, missing or unsupported tools can limit the options available.
For affected third-party databases, the system conversion process will end in 2030
According to SAP, for SAP Business Suite 7 running on an affected third-party database, a system conversion to SAP S/4HANA or SAP Cloud ERP is only available before the end of the corresponding support agreements in 2030. After that, SAP will only offer greenfield migration scenarios for these systems.
Therefore, anyone wishing to use the system conversion path must complete the migration before the end of 2030. This is an important restriction, but it does not constitute a blanket requirement for all SAP companies to adopt a greenfield approach.
Also check Java dependencies separately
SAP’s current support agreements for Java 8/JEE5 in connection with SAP NetWeaver AS Java 7.5 are also scheduled to expire at the end of 2030. Once they expire, even customer-specific maintenance cannot replace the associated support services and rights. According to SAP, starting in 2031, SAP NetWeaver AS Java 7.5 and its add-ons will transition to customer-specific maintenance, with no subsequent releases.
For SAP solutions based on AS Java, SAP provides solution-specific transition recommendations. Details on the product implications can be found in the respective SAP notes (e.g., 3464370). The Transition Option for SAP ERP does not cover Java-dependent functions.
What does "customer-specific maintenance" mean?
Once Extended Maintenance ends, on-premise SAP Business Suite 7 systems generally run under customer-specific maintenance. However, for systems with affected third-party databases or Java dependencies, the scope of services is further limited. SAP can no longer provide comprehensive support for issues related to third-party databases or Java. This includes, among other things, kernel and kernel security patches for third-party database environments. SAP also warns that issues may no longer be resolved within the available support framework, particularly for third-party databases or Java.
SAP therefore recommends that customers not view customized maintenance for mission-critical, affected systems as a sustainable long-term model. This does not mean that a system will be automatically shut down on January 1, 2031. However, it does mean that companies must plan with a limited support and tooling framework.
What approaches does SAP suggest?
The appropriate option depends on the specific system environment. SAP lists the following methods, among others:
- Transition to SAP Cloud ERP: This is SAP’s strategic recommendation. SAP advises completing the transition to SAP Cloud ERP, including the appropriate solutions from the SAP Autonomous Suite, by the end of 2030.
- Migrating the database to SAP HANA (in select cases): Customers who wish to continue operating Business Suite 7 on-premise can eliminate their dependence on a third-party database by migrating the affected system to SAP HANA before the end of 2030. This does not extend either Mainstream or Extended Maintenance. The system will continue to be covered by customer-specific maintenance, with its associated limitations. SAP does not recommend this approach as a long-term strategic solution.
- Transition Option for SAP ERP: A time-limited subscription offer for eligible customers whose transformation is already underway. It is designed for the largest and most complex Business Suite 7 customers and is intended to ensure business continuity from 2031 to 2033, providing a structured path to SAP Cloud ERP. The system must be migrated to SAP ERP, Private Edition on SAP HANA by December 31, 2030; additional requirements apply. Java-dependent functions are not supported.
Companies should address these questions now:
Which SAP Business Suite and NetWeaver systems are in use?
Which databases and Java components are associated with these systems?
Which add-ons, interfaces, and business-critical processes depend on them?
Which transformation options are best suited to the company’s current situation, time constraints, and business processes?
Special technical cases—such as additional database connections or specific lifecycle tools—should also be reviewed based on the relevant system landscape and the applicable SAP notes. They should not be applied across the board to every SAP system based solely on a general overview.
Would you like to know whether the new SAP information affects your system landscape?
With a GQS SAP Readiness Check 2030, companies can assess their third-party database and Java dependencies, evaluate potential paths from both a technical and business perspective, and develop a timeline for the next steps.
We’d be happy to discuss your current situation with you and work together to identify the key questions for your next SAP roadmap.
