Executive Overview

As organizations globally race to transition from legacy SAP ECC environments to S/4HANA before upcoming support deadlines, a quieter, more insidious crisis threatens enterprise stability: the mass retirement of the baby boomer generation. This demographic shift is draining decades of institutional memory out of corporate IT shops. When veteran SAP experts depart, companies do not merely lose personnel; they lose the nuanced, deeply ingrained understanding of complex business processes that keep global supply chains, financial reconciliations, and customer service operations humming.

To unpack this looming crisis, Computerwoche sat down with Uwe Hartmann, founder of FITS-P GmbH and the former Chief Information Officer (CIO) of ABB. With years of executive experience overseeing complex enterprise systems, Hartmann offers a sobering analysis of why S/4HANA migrations alone are insufficient to solve this talent deficit. He outlines how artificial intelligence and process mining must intersect to safeguard organizational knowledge, detailing why meticulous strategic preparation trumps rushed, deadline-driven deployments.


Detailed Chronology and the Roots of the Knowledge Drain

The intersection of the S/4HANA migration timeline and the retirement wave has created a dual-front war for IT leadership. For decades, companies relied on core groups of dedicated SAP specialists who built, tweaked, and maintained custom ERP landscapes. These experts carried the architectural map of the enterprise entirely in their heads—understanding why a specific ABAP script was written in 2008, how a non-standard procurement workflow interacted with local tax codes, and which master data quirks could trigger a downstream logistics failure.

The Anatomy of Institutional Loss

According to Hartmann, viewing the retirement wave merely as a technical headache grossly misjudges the value of these departing workers.

"You have to look at the topic from different perspectives," Hartmann explains. "The knowledge of experienced employees is not limited to technical operation, but above all includes an understanding of how a company’s processes function and how they are controlled in the SAP system."

To illustrate, Hartmann points to the deceptively simple act of generating an order confirmation. On the surface, it is a straightforward transaction. However, in a mature enterprise, that single action triggers a cascade of integrated events: specialized barcode labels are printed for warehouse fulfillment, financial accounting modules are updated, and real-time receivables and liquidity planning systems are informed.

Mastering these intricate connections does not happen overnight. It requires years of tenure, operational exposure, and intimate knowledge of firm-specific customizations. Today, as these key personnel wind down their careers, companies are finding themselves facing a dangerous vacuum where successors have yet to be groomed.

The S/4HANA Pressure Cooker

Compounding this human capital crisis is the ongoing migration to SAP S/4HANA. Industry data indicates that more than half of all SAP customers are still working to complete their transitions. This tight timeframe has forced many CIOs to prioritize raw technical cutovers over knowledge transfer and process re-engineering.

The consequences of this rush are well-documented. Major analyst firms, including Gartner and McKinsey, consistently report that a staggering proportion of S/4HANA projects fail to meet their original budgetary projections or go-live timelines. When institutional knowledge walks out the door mid-migration, these risks multiply exponentially, transforming enterprise software upgrades into multi-million-dollar existential threats.


Supporting Context & Metrics: Beyond the S/4HANA "Checkbox"

A common misconception in the enterprise space is that successfully migrating to S/4HANA acts as a silver bullet, magically resolving legacy tech debt and insulating the organization against brain drain. Hartmann firmly dismisses this notion.

The Smartphone Update Fallacy

Comparing an S/4HANA migration to a mobile operating system update, Hartmann highlights the superficiality of viewing the move merely as a compliance exercise.

"Many companies see it primarily as a prerequisite for continued maintenance and support from SAP," Hartmann notes. "This is similar to a smartphone update: You have the latest version and remain technically up-to-date, but the real added value doesn’t automatically materialize. This is precisely the question many companies are asking themselves: What does S/4HANA offer us beyond the mere maintenance requirement?"

In reality, the true work begins after the green screen gives way to the modern Fiori interface. The enterprise technology landscape is shifting at a breakneck pace. Technologies that seemed futuristic just 24 months ago—such as generative AI, intelligent agents, and automated exception handling—are rapidly becoming core components of modern business architecture.

SAP has invested heavily in infusing its platform with artificial intelligence. However, Hartmann emphasizes that AI is not a magic wand. AI tools can only optimize operations if they are fed clean, well-structured data models and applied to processes that are thoroughly understood by human experts. Without internal talent capable of steering these technologies, organizations risk automating broken, inefficient workflows at scale.

S/4HANA’s hidden migration challenge: SAP expert retirement

Official Insights & Methodologies: Unlocking the Black Box with Process Mining

When veteran employees retire, can their systemic expertise be recovered, or is it gone forever? Hartmann acknowledges that the emotional component—the deep cultural memory, personal relationships, and historical context—is largely irreplaceable. However, technical know-how and operational visibility can be preserved using the right tooling.

The X-Ray for ERP Systems: Process Mining

For organizations caught off guard by departing experts, manual documentation is rarely enough. Organizations frequently underestimate the sheer volume of process variations lurking inside their SAP environments. While a standard flowchart might show three steps to process an invoice, reality often encompasses hundreds or even thousands of hidden pathways, localized workarounds, and undocumented custom extensions.

When asked how companies can bridge this gap, Hartmann is unequivocal: "The only solution then is process mining."

Process mining acts as an MRI or X-ray machine for the ERP system. By analyzing digital footprints left in system transaction logs, process mining platforms expose hidden risks, systemic bottlenecks, dependencies, and rogue customizations. This visibility is vital during an S/4HANA migration, where obscure, overlooked details routinely metastasize into catastrophic project delays.

The Reality Check on AI Agents

Addressing recent announcements from events like SAP Sapphire—where the tech giant showcased numerous AI agents designed to document and analyze migration pathways—Hartmann strikes a note of pragmatic caution. While helpful, AI cannot substitute for foundational data hygiene.

"AI can only deliver meaningful results if the underlying data models are well-structured," Hartmann warns. "You can’t just give a chatbot access to an ERP system and expect it to automatically find optimization potential. Only process mining platforms with a consistent data model create the conditions for AI to recognize patterns and identify potential improvements."

By deploying process mining platforms, incoming or junior employees can bypass the slow, step-by-step handover process. They can visually inspect how transactions flow through the system, review active customization tables, and identify in-house developments instantly, empowering them to formulate targeted, high-value questions rather than starting from absolute zero.


Strategic Pitfalls in Knowledge and Project Management

Reflecting on his extensive career leading IT transformations at ABB and consulting through FITS-P GmbH, Hartmann identifies several recurring blunders that doom SAP projects to failure.

1. Undervaluing Technical Competency in Project Teams

Many organizations staff their migration and transformation teams with well-meaning personnel who lack the requisite technical foundation. According to Hartmann, anyone who cannot read ABAP code or interpret SAP customizing tables is ill-equipped to evaluate the sprawling, custom-built extensions that accumulate in a mature ERP system over decades.

2. Relying on Superficial Documentation

Graphical process flows are helpful, but they only scratch the surface. Failing to account for thousands of real-world process exceptions guarantees that user acceptance testing (UAT) will unearth fatal flaws late in the game. Hartmann recalls a project he witnessed firsthand that was forced to grind to a halt just two weeks before its scheduled go-live because a final audit revealed core business processes had never been comprehensively tested.

3. Mismanaging Consultant Density

There is a dangerous temptation in the industry to throw bodies at a problem. Hartmann stresses that bloated consulting rosters do not guarantee success.
"What matters is not the number of consultants, but their quality," he asserts. "Companies should not hesitate to seek external expertise in the early stages of a project. This is significantly cheaper than having to correct errors shortly before go-live."


Future Outlook: Turning Migration into a Strategic Springboard

As enterprises weigh their options—some even contemplating third-party maintenance agreements to delay the inevitable S/4HANA leap—Hartmann urges cool-headed pragmatism.

While third-party maintenance and delayed migrations can buy organizations breathing room, they must not become an excuse for complacency. The long-term migration to S/4HANA is an inevitability, but speed for the sake of speed is a false economy.

Recommendations for IT Leaders:

  • Audit and Map Now: Utilize process mining immediately to illuminate blind spots, document tribal knowledge, and expose undocumented system customizations before veteran staff retire.
  • Treat Migration as Business Transformation: Do not treat S/4HANA as a mere IT upgrade checkbox. Use the migration as a strategic catalyst to rethink, streamline, and modernize enterprise workflows.
  • Nurture Internal Leadership: Involve motivated junior and mid-level staff in the migration trenches today. These individuals will form the core leadership cadre driving the enterprise over the next decade.
  • Prioritize Quality Over Deadlines: If an organization has breathing room under extended maintenance windows, use that time to systematically build internal expertise, clean master data, and shore up project governance.

Ultimately, navigating the skills shortage while executing an S/4HANA migration requires a paradigm shift. By embracing data-driven discovery tools like process mining and viewing enterprise architecture through a long-term strategic lens, forward-thinking organizations can turn a demographic threat into a historic opportunity to future-proof their operations for the decades ahead.

Leave a Reply

Your email address will not be published. Required fields are marked *