After August 31, 2026, new Java 17 builds will be blocked.
SAP has moved SAP Commerce Cloud to JDK 21 and Spring 6. Once the deadline passes, new builds targeting Java 17 will be blocked.
Still running Java 17 in production?
Custom extensions never tested against Jakarta EE?
No upgrade plan on the calendar yet?
THE COST OF WAITING
Three risks of doing nothing.
Build & deployment failures
SAP Cloud Portal blocks new Java 17 builds. You lose the ability to ship features or hotfixes.
Unpatched vulnerabilities
Security fixes for the Java 17-based path end in Q2 2026, so delaying the upgrade increases security risk.
Revenue erosion
No deploys means no fixes for conversion-killing bugs. No ability to respond to market demand. Every blocked sprint is lost revenue.
ACT BEFORE AUGUST 31, 2026
Start the assessment before the deadline.
Migrations of this scope take weeks. The sooner you start, the more runway you have. A 30-minute conversation tells you exactly where your platform stands.
