SAP S/4HANA release upgrades
Staying current on S/4HANA keeps you on supported releases and gives you access to new functionality. We plan and run upgrades so that the business sees new features, not new incidents.
An upgrade is smaller than a migration, but not small
Moving between S/4HANA releases keeps the data model largely intact, so the work is very different from an ECC conversion. The risk sits in what you have built on top: modifications, enhancements, Fiori apps, interfaces and add-ons, all of which need to work on the new release.
SAP's on-premise release cycle moved to a two-year rhythm after S/4HANA 2023, with feature pack stacks in between. Each release has its own maintenance window, so planning when to upgrade is part of the job.
Upgrade phases
01Upgrade readiness
Target release and feature pack chosen against your maintenance dates, business calendar and the features you actually want.
02Version compatibility
Add-ons, industry solutions, interfaces and third-party products checked for support on the target release. Maintenance Planner used to define the stack.
03Technical remediation
Modification adjustment (SPDD and SPAU), custom code checks, and changes to deprecated APIs and simplification items introduced since your current release.
04Functional regression assessment
Release notes reviewed per module to find changed behaviour, so testing targets the processes most likely to break.
05Integration validation
Interfaces, middleware and connected systems tested end to end, including authorisations and background jobs.
06Testing strategy
Risk-based regression testing with business testers, and a sandbox or copy of production to rehearse the upgrade and measure downtime.
07Cutover execution
Upgrade run with the Software Update Manager in a planned window, with validation steps and business sign-off.
08Post-upgrade stabilisation
Support through the first period-end close after the upgrade, when most issues surface.
Upgrade questions
How often should we upgrade?
Often enough to stay inside maintenance and avoid skipping several releases at once, which makes each upgrade harder. Many customers plan an upgrade every one to two releases.
Can we upgrade and introduce new functionality at the same time?
It is possible, but we usually recommend a technical upgrade first and switching on new functionality afterwards, so you can tell upgrade issues apart from design issues.
Explore the SAP practice
S/4HANA and ERP transformation
Platform, AI and data
Finance and revenue
Supply chain, manufacturing and assets
People, spend and customers
Plan the next step with us
Share what you're working on. We'll tell you how we'd approach it and who would do the work.