Skip to main content

S/4HANA

The core your business runs on, and the foundation for everything else.

S/4HANA is the digital core of a modern SAP estate. The move off ECC has a deadline, and a clean conversion is only half the work. The other half is the part most firms skip: making S/4HANA something your people actually want to use. That means keeping the core clean enough that the next upgrade, the next Fiori app, and the next AI agent all land smoothly. Mindset has done this since before S/4HANA had a name. With SAP's Autonomous Suite now embedding agents across finance, spend, and supply chain, a clean core stopped being hygiene and became the prerequisite for the autonomous enterprise.

S/4HANA sketch
“The Core,” by Gemini 3 Pro ImageJun 20261,993 tokensthe story →
Why now

The conversion is easy to schedule and easy to get wrong

The reality

  • ECC mainstream maintenance ends in 2027. Extended support to 2030 costs a premium, and waiting only compresses the runway for testing, cutover, and adoption.
  • A technical conversion can go live on time and still strand the business. NPPD upgraded to S/4HANA, rolled out roughly 100 Fiori apps, and watched long-tenured staff keep working in the old SAP GUI while the launchpad sat unused.
  • Most conversions carry the old technical debt across the river. Over-customized code that was painful on ECC is just as painful on S/4HANA, and it breaks the next upgrade the same way.
  • A clean, well-governed core is what SAP's AI agents read and act on. A messy S/4HANA limits what Joule and the autonomous enterprise can ever do for you.

What changes

  • A conversion plan that starts with your code

    We analyze custom code and data first, then choose a brownfield, greenfield, or selective approach. The path follows from what we find.

  • Fit-to-standard before custom

    We pressure-test what really needs to be custom and route the rest to standard. Clorox ran its S/4HANA program with fit-to-standard as a ground rule, helping the system stay maintainable.

  • Clean core that survives the next upgrade

    Extensions live on BTP, the core stays standard, and future updates stop being a fire drill. Merit Energy co-presented its Clean Core S/4HANA work at SAP Sapphire.

  • An experience layer people adopt

    We put Fiori, roles, and design thinking on top of the core, so go-live becomes daily use instead of a quiet retreat to the GUI.

  • A core that is AI-ready

    Clean data and standard processes are the prerequisite for Joule agents to act on S/4HANA safely. We build the foundation now so the agents have something solid to stand on.

  • RISE without the lift-and-shift trap

    If RISE with SAP is your route, we keep it from becoming a hosting change with the same old problems. The point of the move is a cleaner core.

Our view

The companies that get value from S/4HANA aren't the ones that finished the conversion first. They're the ones that treated the conversion as the moment to clean up the core and make the system usable. Everything after that (Fiori, analytics, AI) could build on a foundation that was actually solid.

Capabilities

From conversion through the value nobody captured the first time

We work both ends of S/4HANA: the migration itself, and the clean core and experience work that turns a live system into one the business runs on.

Conversion strategy and readiness

A clear-eyed read on where you stand against the 2027 deadline and which path fits your estate.

  • Custom-code and data readiness analysis against S/4HANA simplification items
  • Brownfield vs greenfield vs selective decision, scoped to your code and data reality
  • Migration roadmap with cutover, testing, and adoption sequenced together

Clean core and code remediation

Move extensions off the core so the next upgrade is routine instead of a project.

  • Identify and remediate custom code that creates upgrade friction
  • Relocate customizations to BTP side-by-side extensions
  • Governance model that keeps the core clean after we leave

Fit-to-standard and process design

Decide what truly needs to be custom before a single object gets built.

  • Process workshops that separate genuine differentiation from inherited habit
  • Standard-first configuration with custom reserved for real edge cases
  • Signavio process intelligence to ground the decisions in actual data

Fiori and experience on S/4HANA

The reason adoption sticks. We make the live system one people choose to use.

  • Role-based Fiori launchpad cleanup and targeted app enablement
  • Custom Fiori and UI5 for the workflows standard apps do not cover
  • Design thinking to find the high-impact UX gaps before building

RISE with SAP advisory

Use the move to RISE to clean up the core.

  • RISE readiness and landscape planning alongside the conversion
  • Clean-core discipline carried into the managed environment
  • Integration and extensibility patterns that fit the RISE model

Analytics and data on the core

Turn S/4HANA transactional data into reporting the business can run itself.

  • Embedded analytics and CDS views on live S/4 data
  • Datasphere and SAP Analytics Cloud for cross-system reporting
  • BW-to-cloud transition planning where legacy reporting is in the way

AI readiness and Joule on S/4

Lay the clean-core foundation the autonomous enterprise needs to act.

  • Data and process cleanup so AI agents have a reliable core to read
  • Joule enablement scoped to your real S/4HANA processes
  • Practical automation pilots that prove value before a wide rollout
Real impact

When the S/4HANA investment finally pays off

Nebraska Public Power DistrictNebraska Public Power District

NPPD's technical S/4HANA upgrade left roughly 100 Fiori apps unused and staff back in the old GUI. Mindset launched 72 apps in 5 weeks for Accounts Payable, cleaned up roles, and trained the team, with an estimated 5 to 20% productivity gain from fewer errors and easier wayfinding.

~8 months of planned build 5 weeks

Fiori optimization turnaround after a technical S/4HANA upgrade

Merit EnergyMerit Energy

Building on Merit's S/4HANA, MDG, and BTP investment with clean-core discipline, Mindset delivered a vendor management portal that cut approval clicks 60%, gave back 57 hours per user a year, and saved an estimated $113.5K annually across 60 users.

60% fewer clicks

on vendor approval tasks, on a clean-core S/4HANA and BTP foundation

How we engage

Scope the path before you commit to the program

We start small. A readiness read tells you the real path, then delivery keeps the core clean and the people on board the whole way.

  1. Phase 1

    Readiness and path

    2 to 4 weeks

    We run a custom code and data analysis, plus a fit-gap read. You leave with a clear recommendation on brownfield, greenfield, or selective conversion, with the trade-offs spelled out.

  2. Phase 2

    Conversion and clean core

    Program-dependent

    We execute the conversion while remediating code and routing extensions to BTP, so you land on S/4HANA without dragging the old technical debt across.

  3. Phase 3

    Experience and adoption

    5 to 12 weeks per wave

    We deliver Fiori cleanup, role-based launchpads, and the apps people actually need, in waves, so adoption is real before the next one starts.

  4. Phase 4

    Run and extend

    Ongoing

    We add analytics, automation, and AI readiness on the clean core, plus AMS so the system keeps earning its keep instead of drifting back to where it was.

Common questions

What teams ask us about S/4HANA

When do we actually have to move off ECC?
Mainstream maintenance for SAP ECC ends in 2027. Extended support runs to 2030, but at a premium, so the practical window for planning, testing, and a calm cutover is now, not 2029. The later you start, the less room you have to do it well.
Should we pursue a brownfield conversion or a fresh greenfield build?
It depends on how much of your ECC configuration and custom code still serves the business. Brownfield carries your history forward and is faster. Greenfield is a clean slate but a bigger lift. A selective approach mixes both. We make that call after looking at your code and data.
We already went live on S/4HANA, and nothing improved. Now what?
You are not alone. A technical conversion can finish on time and still leave people working the way they always did. That was exactly NPPD's situation. The fix is post-go-live optimization: clean up roles, enable the Fiori apps that matter, and rebuild the experience so the system you paid for is the system people use.
Does clean core mean we cannot customize anything?
No. It means custom logic lives on BTP as side-by-side extensions instead of inside the core. You still build what your business needs. The difference is that the next upgrade doesn't break it, so customization stops being the thing that traps you on an old release.
How does S/4HANA connect to all the AI everyone is talking about?
A clean, well-run S/4HANA core is the foundation SAP's Joule agents act on. The autonomous enterprise runs on top of the digital core, so the cleaner your data and processes are now, the more AI can safely do for you later. Doing S/4HANA right is the prerequisite.
Recent thinking

From our Insights.

All Insights

Talk to a S/4HANA partner.

Our first call is a working session, not a pitch. Bring a real problem and let’s whiteboard it together.