These higher maintenance costs should inevitably be taken into account for all business case considerations and future plans to move to SAP S/4HANA.įrom our experiences over the past years, it is very difficult to create a business case with a high ROI purely based on technology promises.

Does this mean that you, as an SAP user, can sit back and relax? Not at all! As from 2027, it will definitely cost more to maintain your SAP system if you are not yet on SAP S/4HANA. The deadline pressure for a move to SAP S/4HANA before 2025 is now officially off the table. How the deadline postponement for SAP ECC support impacts your own SAP S/4HANA strategy The “early adopters” of SAP S/4HANA usually have big problems with their existing SAP ECC system and/or business processes, meaning that we’re currently mostly seeing greenfield approaches (or variations thereof) to convert to SAP S/4HANA.

So far, PIKON has migrated four big customers to SAP S/4HANA, including only one with a classic conversion ( brownfield) approach. Up to now, especially costs and Change Management were the biggest reasons for organisations not to move to S/4, meaning they needed to have a clear business case. With their decision to extend support for SAP ECC 6 until 2027, SAP provide customers with more time and greater certainty to plan their own move to SAP S/4HANA. The number of SAP S/4HANA migrations is still rather modest, and it is completely impossible that every existing customer will have converted to SAP S/4HANA (either through a greenfield or a brownfield approach) by 2025. The German software giant is facing reality. A commitment was also made to keep SAP S/4HANA support until at least the end of 2040! ( SAP News) Why SAP extended their support for SAP ECC 6 until 2027 Optional extended support until the end of 2030 is also possible (for a two percentage-point increase in the maintenance cost). The SAP community knew it was coming: SAP has delayed the end in support for SAP Business Suite 7 (incl.

SAP ECC EHP6 vs EHP7