The SAP S/4HANA Deadline

deadline

SAP’s end-of-support deadline is coming; their customers need to make a crucial decision: migrate onto the newest product, S/4HANA, or keep their current systems and be left unsupported?

A difficult enough decision in itself; but SAP’s customers may be wondering why they’re facing that decision in the first place? Why has SAP announced their deadline, where has it come from?

In this series, we’re exploring three key areas around SAP’s S/4HANA product and its deadline:

  1. What is S/4HANA?
  2. The S/4HANA deadline
  3. Your options

Want the full story? We’ve written a full guide on SAP S/4HANA, the deadline, and your options: click here to download your copy.


History of the S/4HANA deadline

2010: SAP HANA is released. SAP’s database that can host their applications. Fittingly, SAP then introduce a 2017 cut-off point, ending support for Oracle products within the SAP environment.

May 2017: The Oracle-within-SAP deadline is extended to 2025.

2019: SAP also had in place a 2019 end-of-support deadline, which applied to many of SAP’s products (not all of them).

There followed a period of slow sales, during which SAP also realised that some customers using different SAP applications would potentially have to go through an upgrade process for 2019, and then again, in 2025.

SAP declare one, universal 2025 deadline. Customers would only have to go through the process once, and SAP gained another six years to strengthen their position and prove they could deliver.

SAP move their deadline again

February 2020: Information released on SAP’s website revealed that they had decided to move the deadline once more. Their update provided the insight we all so eagerly awaited.

SAP advised they would:

  • Extend the deadline to 2027, for several products including SAP ERP 6.0 and SAP Business Suite
  • Offer extended maintenance to any organisations still in mid-transition after 2027. Their extended support model would come at a higher premium, available until the end of 2030
  • Transfer the remaining, non-migrated customers onto a customer-specific maintenance model

SAP’s decision may have come as a result of feedback from organisations who were keen to move across, but for them, 2025 was still too soon. SAP’s reschedule for 2027 will hopefully allow organisations more time to make the transition.

Interestingly, SAP also announced at the same time that they would be ‘supporting S/4HANA until at least 2040’. An odd thing to say about a new product; to then immediately give S/4HANA its own cut-off date. Perhaps this is SAP being self-aware, knowing that they plan to make “S/4HANA 2.0” (for example) and have declared 2040 as a pre-emptive strike.

Still, that is 20 years ahead; for now, customers should be concentrating on getting onto S/4HANA in the first place.

Learn more about the SAP deadline

Recently, we published a guide detailing the SAP S/4HANA story, with additional information intended to help organisations make informed decisions about the future of their SAP systems.

If you find yourself:

  • Worried about falling “out of support” if you don’t stay on the latest version
  • Feeling under pressure from SAP to move to S/4HANA
  • Unsure of what options are available to you
  • Wishing you could stick with your current, stable ERP system

…then we can help.