Upgrade Path Planner

SAP S/4HANA upgrade path planner: any release to 2023 or 2025

Pick the SAP S/4HANA release you run today and the target, on-premise or SAP S/4HANA Cloud Private Edition. The planner shows the route SAP documents (Readiness Check, Maintenance Planner, SI-Check, ATC, SUM, SPDD and SPAU, Silent Data Migration, Fiori and role follow-ups), flags when a release is too old for a direct upgrade, lists what changes in each release you cross, and sizes risk, effort and a regression test plan from your custom code, interfaces and modules.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 21 cited sources.

1Releases
EndedUpgrade Guide and What's New version 1.0 dated October 7, 2020. S4CORE 105.
CurrentUpgrade Guide and What's New version 1.0 dated October 8, 2025. FPS01 (February 2026) and FPS02 (October 2026) followed.
2Landscape
What to count in S/4HANA
customizations:
Modified SAP objects (SPDD, SPAU), enhancement implementations (SPAU_ENH) and custom ABAP objects with ATC findings for the target. Count objects you expect to touch, not every Z object.
integrations:
IDoc and ALE partners, OData and RFC consumers, SAP BTP Integration Suite or PI/PO flows, BW, EWM, Ariba, MES and CRM.
interfaces:
EDI maps, bank and payment files, flat-file uploads and batch jobs that read or write files.
reports:
Custom ABAP reports, custom CDS views and analytical queries, Adobe Forms, Smart Forms and SAPscript output.
sites:
Production systems or rollout waves upgraded separately. Plants and company codes in one system count once.
Modules in use
Integration types
SAP S/4HANA 2020SAP S/4HANA 2025 (current)

Direct upgrade: SAP supports one SUM run from 1709 or any later release to 2023 or 2025 (and from any earlier release to 2022). No intermediate release is required; check the feature package equivalence in the target's Release Information Note.

Steps
19
1 to confirm
Releases crossed
4
S/4HANA 2023 and 2025
Risk
70 / 100
High
Effort
223-599 d
about 11-30 person-months
  1. 1
    PreparationDocumented

    Run SAP Readiness Check for SAP S/4HANA upgrades

    Not mandatory but highly recommended by SAP. It analyzes the productive source system and lists the simplification items relevant to your target, a high-level custom code analysis, add-on compatibility, recommended SAP Fiori apps and app availability (successor, deprecated or obsolete apps). It applies to release upgrades such as 2023 to 2025, not to FPS or SPS updates within a release.

    SAP Readiness Check for SAP S/4HANA upgradesSimplification Item CatalogSource 1Source 6
  2. 2
    PreparationDocumented

    Confirm the start release and the feature package equivalence

    Each target release lists its supported start releases and the required feature package stack equivalencies in its Release Information Note (2025: SAP Note 3493301; 2023: 3307222; private edition 2025: 3658070). If your source system already has a higher support package than the equivalent stack of the target, the Maintenance Planner blocks the plan (SAP Note 2457423) and you wait for the equivalent target stack. Avoid applying a newer SPS to the source while a release upgrade is planned.

    Release Information NoteMaintenance PlannerSource 1Source 2Source 6
  3. 3
    PreparationDocumented

    Plan the DEV, QAS, PRD sequence, the development freeze and dual maintenance

    Upgrade the systems in transport order (development, quality assurance, production) with the same software packages, and transport only between systems on the same release and stack. SUM locks the development environment during the run (check in SE06). SAP recommends a temporary copy of the development system to deliver emergency corrections to production while the original development system is upgraded, with every correction made in both. Keep the development system where modifications were made: do not overwrite it with a production copy.

    SE06Transport Management SystemSource 6
  4. 4
    PreparationDocumented

    Run the Maintenance Planner and generate stack.xml

    Mandatory. The Maintenance Planner checks add-ons (SAP Note 2214409), active business functions and industry solutions (SAP Note 3549655 for 2025) and blocks the upgrade if any has no valid path. A business function that is on in the source but always_off in the target makes the upgrade impossible; one that is off but always_on in the target is activated during the upgrade (SAP Notes 2240359 and 2240360). Run it before the SI-Check, which needs the stack.xml as input. SPAM/SAINT patch 71 or higher is required in the source system.

    Maintenance Plannerstack.xmlSPAM/SAINTSource 1
  5. 5
    ValidationDocumented

    Run the Simplification Item-Check and clear return codes 8 and 12

    Implement SAP Notes 2399707 (report) and 2502552 (check classes through TCI, SAP Note 2187425), then run /SDF/RC_START_CHECK in SA38 for the target release, including Check Consistency for All. Return code 4 (yellow) does not block, but by default custom table appends are not retained and their data is lost. Return code 7 errors must be read and exempted. Return codes 8 and 12 are inconsistencies to fix: SUM stops at the start on 12 and just before downtime on 8 or higher.

    /SDF/RC_START_CHECKSA38Source 1
  6. 6
    PreparationDocumented

    Check custom code against the target with ATC and a baseline

    Import the Simplification Database (download CCMSIDB, import in transaction SYCM, see SAP Note 2241080). In ATC run a local series on the current release with check variant S4HANA_READINESS_<current release year> (or the _NO_FLE variant when the material number length is 18), add the result to the baseline, then run S4HANA_READINESS_2025 (or the target year) with Consider Baseline so that only findings caused by the upgrade remain. The Custom Code Migration app (F3191) does the same with usage data, which shows unused code to retire.

    ATCSYCMCustom Code Migration app (F3191)Source 1
  7. 7
    PreparationDocumented

    Check the SAP GUI version

    The new release cannot be used until a compatible SAP GUI is installed. The front end is compatible with several releases, so you may not need a new one; it can be rolled out before the upgrade (SAP Notes 147519 and 26417). NWSAPSetup packages the client for mass deployment.

    NWSAPSetupSource 6
  8. 8
    PreparationDocumented

    Java instances: check the operating system in the PAM

    If you run SAP S/4HANA Java instances, check that their operating system is supported for the target in the Product Availability Matrix; if not, move to a supported one by system copy with Software Provisioning Manager first. See SAP Note 3612338 for 2025 Java restrictions.

    Product Availability MatrixSoftware Provisioning ManagerSource 1
  9. 9
    UpgradeDocumented

    Run the Software Update Manager (SUM 2.0, latest SP)

    SUM performs the release upgrade from the stack.xml and runs the SI-Check and the custom code checks itself. Use the SUM 2.0 guide for the current SP and its SAP Note, plus the application notes for the preparation phase (2025: SAP Note 3634200) and the follow-on phase (3634222). SAP Note 2351294 lists measures to reduce technical downtime.

    Software Update Manager 2.0Source 1Source 7
  10. 10
    ConversionDocumented

    Adjust modifications and enhancements in SPDD, SPAU and SPAU_ENH

    Every modified SAP object is offered for adjustment. ABAP Dictionary objects are adjusted in SPDD during uptime in the shadow system; other repository objects in SPAU near the end of the run; enhancements in SPAU_ENH after SPAU. Keep at least one customer namespace package, since packages cannot be created during the update. Objects created from manual correction instructions of SAP Notes can be deleted passively and cause data loss if not re-created in SPDD (SAP Note 2513585). Transport the adjustment requests from the first system so later systems need no manual adjustment (SUM phase ADJUSTPRP).

    SPDDSPAUSPAU_ENHSource 6Source 7
  11. 11
    ConversionDocumented

    Let Silent Data Migration (SDMI) finish in every client

    SDMI migrates application data after the upgrade while users work. Maintain the technical user in SDM_USER (or let SUM create it) and monitor in SDM_MON. Each SDMI supports uptime for at least one release; when you skip releases, SDMIs of the skipped release run in downtime unless they support the target. From 2020 as start release, SDMIs cover three releases, so the zero downtime option (ZDO) can jump up to two releases. All SDMIs must finish before the next upgrade.

    SDM_MONSDM_USERSource 1Source 7
  12. 12
    ConversionDocumented

    Upgrade SAP Fiori and run the launchpad follow-on tasks

    Match the front-end server to the target: 2023 uses SAP FES 2023 with SAP_UI 7.58 embedded (SAPUI5 1.114 standalone), 2025 uses SAP FES 2025 with SAP_UI 8.16 embedded (SAPUI5 1.136 standalone); see SAP Note 2217489 for the hub strategy. After SUM: apply the corrections in the Fiori Release Information Note (2025: 3493254), replicate backend catalogs with /UI2/GET_APP_DESCR_REMOTE_ALL, run /UI2/INVALIDATE_CLIENT_CACHES and /UI2/INVALIDATE_GLOBAL_CACHES, and if SAP GUI for HTML apps fail, activate /sap/public/bc/its in SICF (report RS_ICF_SERV_MASS_PROCESSING).

    /UI2/GET_APP_DESCR_REMOTE_ALL/UI2/INVALIDATE_GLOBAL_CACHESSICFSource 1
  13. 13
    ConversionDocumented

    Compare default authorization values (SU25) and update PFCG roles

    The upgrade can change SAP default values (SU22). Run SU25 steps 2a and 2b to compare them with your customer values (SU24), then use the SU25 actions Update of Application Groups in Role Menu and Roles to Be Checked to adjust PFCG roles for changed defaults and new Fiori catalog content (SAP Notes 1539556 and 440231).

    SU25SU24PFCGSource 1
  14. 14
    ConversionDocumented

    If BW or other ODP consumers extract from S/4HANA: review ODQ jobs

    Technical job definitions SAP_ODQ_CLEANUP and SAP_ODQ_DAEMON_STARTER are active. If you scheduled ODQ_CLEANUP or ODQ_DAEMON with your own variants, decide whether to keep them or use the SAP definitions (SAP Note 2677355). The 2025 upgrade takes SAP BASIS to 8.16.

    ODQMONSource 1Source 14
  15. 15
    ConversionDocumented

    PP/DS only: run PPDS_DEACTIVATE_ADVN_PLN_PROD

    Handling of material plants flagged for deletion in PP/DS changed with 2022. Coming from 2021 or lower to 2022 or higher, run report PPDS_DEACTIVATE_ADVN_PLN_PROD to update the Advanced Planning status (SAP Note 3150247).

    Source 1
  16. 16
    ConversionDocumented

    Advanced Variant Configuration: follow-on activities

    From 1709 or higher, follow SAP Note 2987015. From a release lower than 1709, do the Advanced Variant Configuration follow-up activities in the Installation Guide of the target release.

    Source 1
  17. 17
    ValidationDocumented

    Validate business data with Data Transition Validation (DTV)

    Part of the standard license. Agree the comparison reports with the business and auditors, create the DTV project, extract from the source during ramp-down, and compare in the target after the upgrade (SAP Note 3117879).

    Data Transition ValidationSource 1
  18. 18
    ConversionDocumented

    Clean up obsolete data with transaction SODH

    Source data of simplified data models is not deleted during the upgrade, to keep downtime short. After testing and validation, delete it with the class-based Obsolete Data Handling tool delivered with 2023 (transaction SODH, SAP Note 3335020). The old report ODH_Data_processing should no longer be used.

    SODHSource 1
  19. 19
    CutoverVerify with vendor

    Rehearse, freeze and cut over

    Time the full SUM run at least once on a copy of production, agree the freeze and downtime window, run the DTV extraction during ramp-down, then upgrade, finish SDMIs, run the regression suite and reconcile key balances before users return.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the S/4HANA upgrade planner

  1. 1

    Pick your releases

    Choose the current SAP S/4HANA release (or SAP ECC 6.0 for a conversion) and the target release. Set the target to private cloud if the system runs, or will run, in SAP S/4HANA Cloud Private Edition.

  2. 2

    Describe your landscape

    Enter modified SAP objects and custom code with findings, integrations, file and EDI interfaces, custom reports and forms, data size, users and separately upgraded production systems. Tick the modules and integration types you use.

  3. 3

    Read the path and the drivers

    Each step shows its SAP source, tools and SAP Notes. The Changes tab lists technical and functional changes per release crossed, and the Risk tab explains every driver behind the score.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Tests are flagged critical where your path changes that area, and marked where automation pays back on every FPS and SPS update.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of SAP S/4HANA?

SAP S/4HANA 2025, released on October 8, 2025, with FPS01 in February 2026 and FPS02 in October 2026 according to the guide versions on the SAP Help Portal. Since 2023 SAP ships a new on-premise and private edition release every two years, each with three feature package stacks and then support package stacks.

Can I upgrade from SAP S/4HANA 1909 or 2020 directly to 2025?

Yes. The Upgrade Guide for SAP S/4HANA 2025 supports start releases 1709, 1809, 1909, 2020, 2021, 2022 and 2023 in any feature package or support package stack. Check the feature package equivalence in SAP Note 3493301 first: if the source is on a newer stack than the equivalent 2025 stack, the Maintenance Planner blocks the plan until SAP releases that stack.

How do I upgrade from SAP S/4HANA 1511 or 1610?

In two hops. The 2023 and 2025 upgrade guides start at 1709, while the 2022 guide still lists 1511 and 1610 as start releases. Upgrade to 2022 first, let the Silent Data Migrations finish, then upgrade to 2023 or 2025.

What is the difference between a release, an FPS and an SPS?

Moving from one release to another (for example 2023 to 2025) is an upgrade and needs thorough testing and end-user training. Moving to a higher feature package stack or support package stack within a release (for example 2023 FPS03 to SPS04) is an update. SAP's Getting Started guide says FPS updates need regression testing of existing processes plus functional testing of new features, and SPS updates recommend regression testing.

Which tools do I need for an SAP S/4HANA upgrade?

The Maintenance Planner (mandatory, it generates the stack.xml), the Simplification Item-Check report /SDF/RC_START_CHECK (mandatory, called by SUM), the Software Update Manager 2.0, and for custom code the ABAP Test Cockpit or the Custom Code Migration app. SAP Readiness Check for SAP S/4HANA upgrades and Data Transition Validation are recommended.

Who does what in a private cloud (RISE) upgrade?

In SAP S/4HANA Cloud Private Edition, SAP Enterprise Cloud Services runs the technical SUM procedure after your service request and can generate the Maintenance Planner ID. You still handle the SPDD and SPAU adjustments (unless you buy the billable package), the SI-Check results, application SAP Notes, custom code, testing and follow-on activities.

When does maintenance end for my SAP S/4HANA release?

SAP gave releases before 2023 five years of mainstream maintenance and from 2023 seven years. Public secondary sources put the end for 2020 at December 31, 2025, for 2021 in 2026, for 2022 in 2027 and for 2023 in December 2030. The extended maintenance option for 1709, 1809 and 1909 ran to the end of 2025. Confirm your dates in the SAP Product Availability Matrix.

How should we test an SAP S/4HANA upgrade, and what should we automate?

Run platform tests (logon, roles after SU25, ATC, modifications, jobs, SDMI completion, forms and reports), the business processes you use, and every IDoc, OData, RFC and file interface with saved production data, plus a DTV comparison of financial data. Each release now gets three FPS and further SPS updates that SAP says need regression testing, so the tests marked for automation pay back on every update.

Sources

  1. SAP Help: Upgrade Guide for SAP S/4HANA 2025 (version 3.0, October 2026)
  2. SAP Help: Upgrade Guide for SAP S/4HANA 2023 (version 7.0, August 2026)
  3. SAP Help: Upgrade Guide for SAP S/4HANA 2022
  4. SAP Help: Upgrade Guide for SAP S/4HANA 2021
  5. SAP Help: Upgrade Guide for SAP S/4HANA 2020
  6. SAP Help: Upgrade Guide for SAP S/4HANA Cloud Private Edition 2025
  7. SAP Help: Conversion Guide for SAP S/4HANA 2025 (version 3.0)
  8. SAP Help: Getting Started With SAP S/4HANA 2025 (release cycles, FPS and SPS)
  9. SAP Help: What's New in SAP S/4HANA 2020
  10. SAP Help: What's New in SAP S/4HANA 2021
  11. SAP Help: What's New in SAP S/4HANA 2022
  12. SAP Help: What's New in SAP S/4HANA 2023
  13. SAP Help: What's New in SAP S/4HANA and SAP S/4HANA Cloud Private Edition 2025
  14. SAP Help Portal: SAP S/4HANA product assistance (transactions WE02, BD87, MD01N, ODQMON, /IWFND/ERROR_LOG)
  15. SAP News: New SAP S/4HANA release and maintenance strategy (September 2022)
  16. SAP Support: Maintenance strategy for SAP S/4HANA and SAP Business Suite 7
  17. SAP: RISE with SAP and SAP Cloud ERP Private
  18. Wikipedia: SAP S/4HANA (release history and S4CORE versions)
  19. UpperEdge: SAP customers approaching end of support deadlines (February 2025)
  20. Rimini Street: end of mainstream support for SAP customers
  21. Zensar: SAP S/4HANA upgrade, the need of the hour

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.