SAP ends legacy ERP conversions after December 31, 2030; the only road left is a rebuild from scratch

The deadline arrived as a blog post

SAP's▲+1.23% — SAP, up 1.23 percent today CTO Philipp Herzig published the end date on the company's own news site on October 7↗, with no press release attached: when optional extended maintenance for Business Suite 7 closes on December 31, 2030, SAP's reselling and support agreements for third-party databases and Java expire on the same day ¹. Mainstream maintenance still ends on December 31, 2027, and that calendar has not moved since 2020 ¹. What moves is the plumbing underneath. After 2030, SAP says it will no longer route support tickets to the database vendor, ship kernel or security patches for third-party database environments, or provide database tooling at all ¹.

The cliff feeds the subscription line

Cloud revenue is the engine being fed: it rose 22% to €6.3 billion in the second quarter↗, the current cloud backlog stands at €22.9 billion, up 27%, and SAP guides 2026 cloud revenue of €25.8 billion to €26.2 billion against €21.02 billion in 2025 ⁴⁵. The remaining Business Suite base is the last tranche of feedstock, and the post tells it to finish moving, to SAP Cloud ERP and the Autonomous Suite, by the end of 2030 ¹.

The stick followed the carrot by days

The note landed days after CEO Christian Klein opened SAP Connect in Las Vegas with the Autonomous Suite: Joule Work live with SAP's own 110,000 employees, productivity gains above 20% claimed in HR, finance and procurement, more than 200 agents generally available and 400 targeted by year-end, with Novartis, Nestlé and PwC named as customers ²³. Klein joked that Joule drafts his earnings-call prep so well he asked who even needs a CEO ². The blog post carries the other half of the pitch. A system conversion from Business Suite 7 on a third-party database to S/4HANA or Cloud ERP exists only before the end of 2030; after that, only greenfield re-implementations, and NetWeaver AS Java 7.5 drops into customer-specific maintenance in 2031 with no follow-on release ¹.

The rebuild is the expensive road

Greenfield is the long road: the average greenfield S/4HANA migration runs 20.2 months against 15.8 for a conversion↗, and 68% of Americas' user group members are already live or moving, with 62% less than three years in ⁶. The exposed tail is whoever has not started, and the biggest check in every migration is written to a consultancy, not to SAP.

The escape hatches carry fine print

SAP's bridge, Transition Option for SAP ERP, runs 2031 through 2033, requires systems on SAP ERP private edition on HANA before December 31, 2030, and does not cover Java-dependent capabilities ¹⁷. Switching the database to HANA removes the third-party dependency but not the cliff: the system still falls into customer-specific maintenance, which SAP itself says is no sustainable long-term operating model for business-critical systems ¹. DSAG board member Michael Bloch wants any decision based on a comprehensive assessment of all available alternatives, wording that points at third-party maintenance; Rimini Street▲+1.59% — Rimini Street, up 1.59 percent today, listed on Nasdaq, already supports SAP ECC and Business Suite and sells "no forced migrations"↗ ¹⁸.

Watch the countdown, not the keynote

SAP reports third-quarter results on October 21↗, where backlog conversion does the talking ⁹. The trade underneath is plain: integrators book the pre-2030 wave, the database vendors lose the support annuity SAP resold, and holdouts lose the right to convert at all. SAP is no longer selling an upgrade. It is selling a countdown.