Only a minority of companies who are either current SAP customers, or plan to become SAP ERP users, have completed their migration to the company’s S/4HANA system, even though support for its ECC on-premises suite will end in 2030, according to a report from digital transformation services provider LeanIX.

Just 12% of current and intended SAP ERP users responding to a LeanIX survey have completed the transition to S/4HANA, SAP’s cloud-based ERP suite that runs on the HANA in-memory database. The survey polled 100 enterprise architects, IT managers and other IT practitioners across US and Europe.

Another 12% of those surveyed said they intend to migrate, but have postponed the start of their S/4HANA transformation, and 74% of enterprises that were polled are just at the  evaluation and planning phase of their ERP transformation journey, LeanIX reports.

SAP introduced S/4HANA in 2015, expecting its existing base of 35,000 customers (as estimated by Gartner) to convert to the new ERP system.

However, SAP’s earnings disclosure show that S/4HANA has been attracting more new users rather than existing SAP ERP customers. In the last quarter of 2021, about half of all S/4HANA were new users, and for the last two quarters, 60% of S/4HANA users were new SAP customers.

Alignment among teams the biggest challenge

Almost 66% of respondents said that alignment, especially among IT teams, is the biggest challenge when it comes to S/4HANA mirgation.

“This may be due to the size of internal SAP teams: In 63% of the companies, these teams are often made up by more than 50 people,” the report reads.

Further, it states that only very few SAP teams work closely with enterprise architects, who can provide clarity about complex ERP landscapes and their dependencies within the whole software environment in an enterprise.

Only 33% of respondents termed the collaboration between the SAP and enterprise architecture teams in their enterprise as close, and 22% of respondents said that there is no collaboration between the teams at all.

Out of all of the enterprise architects surveyed, only 38% feel sufficiently involved with a transformation project, the report shows.

ERP, software dependencies pose challenges

And due to the lack of collaboration with enterprise architecture teams, almost 50% of respondents say that they see both the definition of the target architecture or roadmap and the identification of dependencies between ERP systems and the surrounding software landscape as challenging for SAP S/4HANA migration.

When asked about the level of transparency into these landscapes, only 20% of respondents said they always have a comprehensive overview or can achieve it in under one month, with 47% of respondents saying that they would need more than three months to provide an overview of all applications and systems, including all ERP solutions and dependencies, used by an enterprise.

Uncertainty over HANA transition period

Despite time for support for SAP ECC coming to an end, there is still uncertainty over the time needed for an enterprise to move to S/4HANA, according to the report.

While Gartner estimates or prescribes a three-to-five-year period as ideal for S/4HANA transition, almost 36% of respondents said that it could take more than three years, followed by 33% respondents estimating that it would take less than two years to upgrade.

However, when asked if the time currently planned for S/4HANA transition would be enough, 37% of respondents say that they would not be able to give an estimate, with 29% saying that they have not adhered to the time planned and overshot it.

Only 33% of respondents estimate that they will be able to complete the ERP transformation according to their planned schedule, the report shows.

Business IT Alignment, Digital Transformation, ERP Systems, IT Management

The ANWR Group, a Mainhausen-based community of financial services and retailers in the footwear, sporting goods, and leather goods industries, has, until 2018, used the ERP system of its bank subsidiary DZB Bank, and as a result, banking sector regulations for financial accounting and controlling also applied to the retail area of ​​the company.

Over time, these regulations became more restrictive, and the flexibility needed for the trading industry was no longer available. “We had already started separating the IT systems a few years earlier in order to better prepare both the bank and the trading companies for the respective requirements,” recalls ANWR Group CIO Sven Kulikowsky. The ERP software was the last shared system.

Together in the greenfield

ANWR adopts a cloud-first strategy for new IT projects, and in 2018, the IT department tackled the migration to SAP S/4HANA together with the business areas of financial accounting and controlling. There was already knowledge of the solutions from the Walldorf-based software company since the previous core system was an on-premises SAP R/3 that was heavily modified. So the new environment really had to be based on a greenfield approach in the public cloud set up by SAP.

“It was extremely important to get the departments on board from the start,” says Kulikowsky. Together they determined what the new solution had to be able to do from the start. In joint workshops, mixed teams from business departments and the IT evaluated the capabilities and degree of maturity of the cloud platform.

Agile with purpose

In order to organize the change, a steering committee was formed as the highest control body. Underneath, a project board formed as a control team from Kulikowsky and his counterparts in financial accounting and controlling, which coordinated with the project manager of the external partner Camelot ITLab for two hours a week. The team received input from cross-functional working groups made up of staff and external consultants, who discussed problems with specific processes. “We were able to quickly compare different opinions and make decisions,” says Kulikowsky. As a result, departments and IT have always pulled together.

He set a goal of migrating all systems to the new environment by the end of 2021, and the 2021 annual financial statements created with S/4HANA. Plus, the 2022 financial year was to start without the old environment, and to do this, Kulikowsky defined nine waves.

Cloud Management, SAP