Skip to main content
Diverse business team in a modern office during a meeting, discussing artificial intelligence strategy. Concept of AI innovation, teamwork, leadership, corporate planning, professional collaboration.
Applications

Beyond the S/4HANA deadline: How to prepare SAP systems for scalable AI

Nov 20, 2025 Read time: 1 min

For many organizations, the driving force behind SAP modernization is a date: the December 2027 deadline for moving from SAP ECC to S/4HANA. But as the date approaches, CIOs are finding the migration timeline is more a starting point than a finish line for their transformation activities.

SAP environments now extend deeper than finance and HR. AI is transitioning from pilots to production. As these areas evolve, the measure of success shifts from achieving modernization milestones to creating a clean foundation for scalable growth.

Brice Alibert, SAP director for Kyndryl in France, champions a straightforward approach to SAP transformation: simplify the core, preserve business differentiators and standardize everything else. Here, he discusses the current state of SAP modernization and offers tips for reducing complexity today to prepare AI environments for tomorrow.

letter-Q-thin-everett-cloud2

What key trends are you seeing in the SAP modernization space?

I’m seeing acceleration across the board. S/4HANA migration started with back-office processes like finance and controlling. Now, it’s expanding across the enterprise to include sales, procurement, manufacturing, warehouse management and quality.

There’s also a strong appetite for new functionality, especially around AI and agentic AI. Customers are very interested in understanding how these technologies can help them run their business better, not just as experiments but as capabilities embedded directly into their processes.

letter-Q-thin-everett-spruce

Do pressures change when SAP transformation moves beyond internal finance functions?

Yes. The stakes are a lot higher. If there’s a problem when you’re transforming the financing and controlling processes in a company, it remains an internal issue. It may cost more money or time, but the problem stays inside the company.

Once SAP moves beyond finance, it changes how people experience the business. Issues don’t just impact your company. They affect the relationships you have with your customers and the relationships your customers have with their own customers and employees. Since you’re touching the heart and core of the business, you must be even more deliberate and get things right from day one.

letter-Q-thin-everett-cloud2

How do AI and agentic AI factor into this process?

I tend to look at AI in two areas. The first is AI for customers and how they use AI features and agents to run their businesses. That’s where most of the focus is today and where expectations are growing very quickly.

The second area is how we use AI ourselves during transformation. AI changes the way we analyze landscapes, understand custom developments and make decisions. It’s not just about the end state or outcome. AI plays a key role in how we modernize systems in the first place.

letter-Q-thin-everett-spruce

What technical requirements are needed for AI to perform optimally?

AI only works if the foundation is clean. It’s very difficult to use AI in a responsible and scalable way if processes aren’t standardized and the core is overloaded with custom code. That’s why standardization is so important. It’s what allows you to move AI and agents beyond isolated use cases and really support the business.

Data quality is also essential. AI is only as good as the data behind it, so moving everything without discipline doesn’t help. You should migrate only the data that makes sense. Targeted migration eliminates non-essential data, which gives you a cleaner foundation for AI and better insights and helps manage costs in subscription models.

letter-Q-thin-everett-cloud2

How does that foundation apply to agentic AI?

Agentic AI needs a predictable environment. When the core is clean and processes are standardized, agents can operate much more effectively. That’s why we spend a lot of time identifying the IP or customizations that truly differentiate a customer. You keep those elements and standardize everything else. Simplifying the landscape is what allows AI to do something useful.

letter-Q-thin-everett-spruce

Are customers’ wants and needs changing as technology and modernization evolve?

Absolutely. Many companies are on their second SAP transformation, so they’ve seen where things get complicated and what slows a program down. These experiences give them the comfort and confidence they need to move faster.

Expectations are also changing. Customers are looking for less lifting and shifting and more original thinking. They want a simpler core and fewer extras that don’t provide real value. And they’re searching for partners to help them on their journey, not just sell them products or services.

letter-Q-thin-everett-cloud2

How does this maturity influence the way customers approach traditional transformation models?

Customers are much more pragmatic now and want to understand the trade‑offs. A greenfield approach (starting from scratch) can feel fresh, but it’s costly, difficult and time-consuming. Moving everything as-is (brownfield) can be cheaper and faster, but it carries technical debt forward and can make it harder to access AI.

More and more SAP customers are finding our Clean Field approach strikes a good balance. They don’t have to throw everything away, but they can avoid carrying unnecessary complexity forward. With Clean Field, they can select the right data to migrate, apply a clean core approach to custom developments, and adopt standards and industry best practices.

letter-Q-thin-everett-spruce

What does modern transformation look like in practice?

Kyndryl itself is a good example. As part of our ongoing transformation, we set out to modernize two SAP applications that contained more than 33,000 lines of custom code. We used Nova Intelligence’s AI solution and our Clean Field approach to simplify the core, remove direct table access and align with SAP best practices from the start.

The results were significant. The transformation took just 10 days and required 75% less manual effort. It also cut costs by 50% and, most importantly, created a cleaner foundation for AI and future innovation.

In the end, the success of SAP transformation isn’t defined by meeting a deadline but by how well the organization is prepared for what follows. As AI and agentic become part of everyday operations, choices about what to simplify, what to preserve and what to standardize made during modernization will shape the next phase of SAP and the company’s ability to adapt over time.