{"id":76537,"date":"2026-09-25T09:31:48","date_gmt":"2026-09-25T08:31:48","guid":{"rendered":"https:\/\/sovanta.com\/sap-s-4hana-go-live-warum-die-eigentliche-transformation-erst-danach-beginnt\/"},"modified":"2026-09-25T21:25:28","modified_gmt":"2026-09-25T20:25:28","slug":"sap-s-4hana-is-live-now-its-time-to-create-value","status":"publish","type":"post","link":"https:\/\/sovanta.com\/en\/sap-s-4hana-is-live-now-its-time-to-create-value\/","title":{"rendered":"SAP S\/4HANA Is Live. Now It\u2019s Time to Create Value."},"content":{"rendered":"\n

You made it through go-live. S\/4HANA is up and running, critical processes are stable, and the new core is in place. That\u2019s a major milestone. But it doesn\u2019t mean the transformation is finished. In fact, this is where a different kind of transformation begins. During an S\/4HANA program, plenty of valuable ideas never make it into production. Not because they aren\u2019t important, but because getting to go-live safely has to take priority. Business requirements get pushed back. Process improvements are postponed. Workarounds remain in place. And that\u2019s perfectly reasonable. But once the new system is live, the question changes from \u201cHow do we get there safely?\u201d to \u201cHow do we get more value from what we\u2019ve built?\u201d<\/strong><\/p>\n\n\n\n

In this article, Christian Heinrich<\/a>, sovanta’s Chief Solutions Officer and President at sovanta America, looks at what comes after S\/4HANA go-live \u2013 and how companies can turn their new technology foundation into measurable business value.<\/strong><\/p>\n\n\n\n

Go-live leaves a backlog. That\u2019s not a bad thing.<\/h2>\n\n\n\n

Every S\/4HANA transformation requires trade-offs. The goal is to go live safely, so teams prioritize what\u2019s essential, reduce risk, and deliberately defer everything that doesn\u2019t need to be part of day one. Over time, that creates a backlog. Some process improvements don\u2019t fit the scope. Some business requirements have to wait. And some established processes simply can\u2019t be fundamentally redesigned while a large-scale migration is underway.<\/p>\n\n\n\n

Capacity <\/strong>is another major factor.<\/p>\n\n\n\n

\n \n \n\n
\n\n
\n\n
An S\/4 transformation doesn\u2019t just consume IT capacity. Process design, migration, testing, and training require significant involvement from the business as well. That makes prioritization essential. Moving valuable improvements to the post-go-live phase is often not an oversight \u2013 it\u2019s a deliberate decision.<\/div>\n \n
\n\n
\n Christian Heinrich <\/div>\n \n
\n Chief Solutions Officer, sovanta <\/div>\n <\/div>\n \n <\/div>\n\n<\/div>\n\n\n <\/div>\n\n\n

After go-live, the priorities change<\/h2>\n\n\n\n

Once S\/4HANA is live and the technical foundation begins to stabilize, all those postponed topics start coming back into focus. Manual steps are still there. Known workarounds haven\u2019t disappeared. Business requirements that were pushed back several times are still waiting.<\/p>\n\n\n\n

The same can be true for custom code<\/strong>. Some extensions are intentionally carried over during the transformation because replacing or redesigning them would add too much complexity and risk. So while S\/4HANA may be live, the journey toward a true Clean Core<\/strong> may still be underway.<\/p>\n\n\n\n

At the same time, the new technology foundation creates opportunities that simply weren\u2019t available \u2013 or practical \u2013 before. There are also processes where teams made pragmatic compromises to get through the transformation. The process works, but perhaps not quite the way the business would ideally want it to.<\/p>\n\n\n\n

That creates a gap. The transformation program may be complete, but the business still expects better processes.<\/strong> Some of that gap is easy to see: manual work, workarounds, deferred requirements. Other opportunities are less obvious. A process may technically work while still requiring unnecessary effort. Employees may still move information between systems, maintain the same data in multiple places, search for information, or wait too long for decisions.<\/p>\n\n\n\n

Nothing is broken. But that doesn\u2019t mean the process is good. And that\u2019s often where significant untapped value sits.<\/p>\n\n\n\n

Migration got you live. Innovation creates the value.<\/h2>\n\n\n\n

It helps to think about an S\/4HANA transformation in two distinct phases.<\/p>\n\n\n\n