sitting man
2018. 03. 28.

Migrating to SAP S/4HANA: 3 myths debunked

SAP S/4HANA is a game-changer in every way. It makes your company more agile and future-proof, brings you closer to your customer, and allows you to create value in previously unimaginable ways. Many companies, however, are postponing their migrations to SAP’s in-memory business suite out of concern for potential impacts on their current infrastructures and processes. The truth: there is much more to lose by not acting, and much to gain for those who start today.
SAP S/4HANA simplifies and connects processes, provides live information and insights, and embeds your enterprise firmly into the digital world at large. In this way, it helps companies tackle some of today’s most pressing business challenges: unsupported decision-making, and increasingly complex processes and technologies.

So, why are companies so afraid to make the move? We’re debunking three major concerns: the stability and maturity of the platform, adoption of the new Fiori user interface, and the impact of migration on custom development.

1. Stability and maturity

Is SAP S/4HANA ERP suite just another fad in the quickly changing field of business solutions? The answer is clear: not by a long shot. SAP has been building on its underlying HANA in-memory data platform since 2011, and over 2700 projects have successfully been implemented over the years. The solution’s first iterations started small, and over the years, new features have been added and tested to guarantee optimum performance. In short: S/4HANA might be cutting-edge, but it is also a mature, proven solution rooted in expertise and experience.

timeline S4HANA

2. From SAP GUI to Fiori

With S/4HANA, SAP has finally exchanged its bland general user interface for Fiori, which features a tiled design that resembles that of a smartphone. But what about users who are actually used to the ‘classic’ way of working via SAP GUI? Will you need to train them all overnight? No. Those who prefer to do so can still perform their daily tasks within their trusted environment, since SAP GUI is not dead. And while they won’t benefit from all the bells and whistles Fiori offers, this gives your business the opportunity for a gradual, undisruptive transition.

3. Custom development

No two implemented ERP systems are the same, and that goes for SAP as well. Your current system is the end result of endless tweaking and custom development. Will you have to redo all those years of hard work?

The answer is... no. There are ample tools available to adjust the custom code, so you won’t have to change anything in a first phase. Taking the step towards S/4HANA can also be the perfect opportunity to get rid of the stuff you don’t really need, to refocus your ambitions, and to gear up for the inevitable future. What’s more, if you do revise your custom code, know that you won’t need to do everything all at once. SAP S/4HANA comes with a range of tools that help you assess the impact of migration on your business and processes.

Everything changes

In the end, taking the step to S/4HANA is not a leap of faith, but a gradual process that requires careful consideration. By taking the first steps today, for example by recruiting an experienced partner or performing your first test (e.g. via our S/4HANA Proof of Value), you can get a head start on your competition.

At delaware, we employ a 5-step approach that starts with technical, functional and custom development impact assessments and results in a clear roadmap that incorporates your particular goal and vision. Change is inevitable, and differentiating yourself from the pack will be increasingly difficult. SAP S/4HANA and delaware are here to help.

Ready to give it a try? Check out delaware’s S/4HANA Proof of Value

What if there was a secure environment where you could explore the possibilities of S/4HANA for your business without taking any risk? Well, that’s exactly what delaware’s S/4HANA S/4HANA Proof of Value is. It allows you to explore the suite:

• on a copy of your own PRD system;
• using your own datasets;
• without impacting your existing landscape;
• for as long as you need to;
• and for a fixed price.
Author: Pieter Lootens. You can follow Pieter on Twitter or connect with him on LinkedIn