How does SAP S/4HANA improve on legacy SAP systems?

SAP S/4HANA improves on legacy SAP systems — primarily SAP ECC — by replacing a decades-old database architecture with an in-memory platform (SAP HANA) that processes data in real time, simplifies the data model, and removes many of the technical workarounds that accumulated over years of customisation. The result is faster performance, a cleaner system landscape, and a foundation built for modern business demands. Below, we answer the most common questions organisations ask when evaluating or preparing for this move.

What are the core architectural differences between SAP S/4HANA and SAP ECC?

The most fundamental difference is the database layer. SAP ECC was designed to run on third-party databases and used a highly normalised data model with aggregation tables to compensate for slower processing speeds. SAP S/4HANA runs exclusively on the SAP HANA in-memory database, which eliminates the need for those aggregation tables and significantly simplifies the underlying data structure.

In practical terms, this means fewer tables, less data redundancy, and a system that can handle large transaction volumes without the performance bottlenecks that ECC users often experienced. The simplified data model also makes reporting more straightforward, because you query live transactional data rather than pre-aggregated summaries.

Beyond the database, S/4HANA introduces the SAP Fiori user interface as the standard front end, replacing the older SAP GUI for most everyday tasks. Fiori is role-based and designed for both desktop and mobile use, which changes how end users interact with the system day to day.

How does SAP S/4HANA handle real-time data processing differently?

SAP S/4HANA processes data in real time because it stores and reads data directly from memory rather than from disk. In SAP ECC, many reports and financial postings relied on batch jobs and pre-calculated aggregate tables that were updated periodically. In S/4HANA, those aggregates no longer exist — calculations happen on the fly against live data.

This changes how finance teams, supply chain managers, and operations staff work in practice. A financial close that previously required overnight batch runs can now be completed much faster. Inventory levels, open orders, and profitability figures reflect the current state of the business rather than the last time a batch job ran.

For organisations that rely on timely data to make decisions, this shift is genuinely significant. It also opens the door to embedded analytics directly within business processes, so users can see relevant figures without switching to a separate reporting tool.

What happens to existing SAP customisations during an S/4HANA migration?

Existing SAP ECC customisations do not automatically carry over to S/4HANA. Some custom code will need to be reviewed, adjusted, or retired entirely, because the simplified data model in S/4HANA removes or restructures tables that older custom developments may have relied on. SAP provides tools such as the Custom Code Migration Worklist to help identify which custom objects are affected.

This is one of the more time-consuming aspects of an S/4HANA migration and one that organisations often underestimate. The volume of custom code built up over years of ECC use can be substantial, and each piece needs to be assessed individually: keep it, rewrite it, replace it with standard S/4HANA functionality, or retire it altogether.

The good news is that S/4HANA’s standard functionality covers significantly more ground than ECC did at launch. In many cases, what was once a custom workaround is now available out of the box. This makes the migration a useful opportunity to review whether existing customisations still serve a business purpose or whether they have outlived their usefulness.

Thorough test management is important here. Every customisation that survives the migration needs to be tested against the new system to confirm it behaves as expected before go-live.

What’s the difference between a greenfield and brownfield S/4HANA migration?

A greenfield migration means starting fresh — building a new SAP S/4HANA system from scratch, without carrying over the existing ECC configuration, master data, or custom code. A brownfield migration means converting the existing ECC system in place, preserving historical data, configurations, and many existing processes while upgrading the technical foundation to S/4HANA.

Each approach carries different trade-offs:

Greenfield gives you a clean slate. It is a good fit for organisations that want to redesign their processes, adopt SAP best practices, and reduce technical debt. The downside is that it requires more upfront design work and typically takes longer to implement.
Brownfield preserves continuity. It is faster to implement and keeps historical data accessible in the new system. The trade-off is that you carry forward existing configurations, including any inefficiencies or workarounds that have built up over time.

There is also a third path — sometimes called a selective data transition or “bluefield” approach — where organisations migrate specific parts of the business to a new S/4HANA system while leaving others in place temporarily. This can work well for large multinationals with complex landscapes, but it requires careful programme coordination across workstreams.

The right choice depends on your organisation’s appetite for change, the state of your current ECC system, and how much of your existing process landscape you want to carry forward. You can explore our full range of services to see how we support both approaches across the full programme lifecycle.

When should an organisation start planning its move to SAP S/4HANA?

The short answer: earlier than most organisations think. SAP has set the end of mainstream maintenance for SAP ECC at the end of 2027, with extended maintenance available through 2030 for an additional fee. That timeline sounds comfortable, but the planning, preparation, and execution of an S/4HANA migration typically take anywhere from one to three years depending on the size and complexity of the organisation.

In 2026, many organisations are already mid-programme or finalising their migration roadmaps. Organisations that have not yet started are not too late, but they are working with a narrowing window — particularly if they want time to run a thorough assessment, design phase, and pilot before committing to a full rollout.

One of the most useful starting points is a structured maturity assessment that evaluates where your organisation stands today: the state of your ECC system, the volume of custom code, the quality of your master data, and the readiness of your teams. This gives you a realistic baseline before any budget or timeline is committed, and it helps avoid the common mistake of underestimating the effort involved.

How Optinus helps with your SAP S/4HANA migration

We work with organisations at every stage of the SAP journey, from the first assessment through to post-go-live support. Here is what that looks like in practice:

Maturity assessment: We start by mapping where you are today — your processes, your data, your system landscape, and your team’s readiness. This gives you a clear starting point before any roadmap or budget is set.
Programme and project management: Our consultants have hands-on experience from real SAP migrations at leading multinationals, not just theoretical frameworks. We manage greenfield and brownfield programmes, coordinating workstreams, stakeholders, and timelines from start to finish.
Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to prevent data loss and errors during migration, protecting the integrity of your master and transactional data throughout the transition.
Cutover and go-live support: We plan and manage the cutover end-to-end, including hypercare and aftercare, so that operational continuity is never at risk during the most critical phase of the programme.
Change management: We address both the technical and human side of the transition, helping your teams adopt new ways of working rather than just completing a training programme.

We are active across SAP, Microsoft Dynamics 365, and other ERP platforms, available both on-site and remote, in the Netherlands, Belgium, and internationally. If you are planning an S/4HANA migration or want to understand where your organisation stands before committing to a roadmap, get in touch with our team or learn more about what we do.

home|

blog|