The ECC → S/4HANA guide
Everything a CIO needs to size, de-risk, and win the move to S/4HANA.
Moving off SAP ECC before the 2027 deadline is a when, not an if. The programs that go well start the same way: they measure the estate honestly, retire the custom code that duplicates S/4HANA standard, and keep the extensions that genuinely differentiate — a clean core. This guide collects straight answers to the questions that decide that program: what a fit-to-standard assessment costs, what a Clean Core Score is, how much custom code you can retire, whether to run on RISE with SAP or on AWS, and how an AI agent can change configuration safely.
Every article leads with a direct answer, cites real SAP objects, and labels reference figures as such. Start with the three cornerstones below, or jump to any question.
All articles
What does an SAP ECC to S/4HANA fit-to-standard assessment cost?
A traditional SAP fit-to-standard assessment runs from roughly $150,000 to $500,000 and takes six to ten weeks, because a systems integrator staffs a team to inventory custom code, interview process owners, and hand-build a findings deck. An agent-led assessment collapses that: a free scan gives a calibrated clean-core estimate in under a minute from a few inputs, and a fixed-price connected assessment reads your live system read-only and returns evidence-linked findings in days, not months. The cost that actually matters is not the assessment fee — it is the avoidable custom-code carry cost the assessment uncovers, which on a reference estate reached $1.9M a year. You are buying a decision, so price it against the migration it de-risks, not by the hour.
fit-to-standardS/4HANAmigration costassessmentclean core6 minWhat is a Clean Core Score, and how do you measure one?
A Clean Core Score is a single 0–100 benchmark for how close an SAP estate is to a clean, standard core — the lower your reliance on custom code and modifications, the higher the score. It factors three things: the volume of custom objects, the age of your release, and how broadly customization spans your modules. It gives a CIO one honest number to size an ECC-to-S/4HANA migration and to track progress from the first scan through go-live.
clean coreS/4HANAfit-to-standardmetrics5 minRISE with SAP vs. S/4HANA on AWS: a CIO's decision framework
Both roads lead to S/4HANA; they end in different places. RISE with SAP is a managed subscription on SAP's terms — SAP operates your ERP and it lives in SAP's cloud. S/4HANA on AWS keeps you in control: you run the same S/4HANA in your own AWS account, choose your hyperscaler, and keep ownership of your data and your exit options. The real decision isn't infrastructure — every cloud hosts S/4 — it's what you own when the migration is done. Agent-led tooling can now cut migration effort on either path, so the tie-breaker is ownership, not hosting.
RISE with SAPSAP on AWSS/4HANAmigration strategy6 minCan an AI agent safely change SAP configuration?
Yes — as long as it never changes production directly. A safely-governed agent does not write to your live system; it drafts the change as a customizing transport and hands it to the change process you already run. The pattern that makes it safe: a human issues a single-use, time-boxed approval token, the agent applies the change in a development client through SAP's own BC Set mechanism, it re-reads the changed rows to verify field by field, and every attempt is logged immutably. Your CTS, QA gate, and change board still decide whether anything reaches production — the agent does the analyst and consultant labor, but your governance stays exactly where it is.
governanceconfigurationSAP securityclean coreagentic SAP6 minHow much custom code can you retire moving from ECC to S/4HANA?
More than most teams expect — often a third to a half of the custom estate — because a large share of custom ABAP either re-implements capability S/4HANA now delivers as standard or is simply dead and unused. On a reference estate (a live ECC system, not a specific customer's result), an evidence-weighted read found that 44% of custom objects were retirement or standardization candidates. The key is reading the business rule inside the code, not just its syntax: an MV45AFZZ exit that enforces a static credit limit is a credit-check policy that S/4HANA FSCM performs as standard, so you retire the exit instead of converting it. Every object you retire with a documented reason is testing you never run and license and maintenance cost you stop carrying.
custom codeS/4HANAclean corefit-to-standardmigration6 minWhat is SAP's agent-led transformation from Sapphire 2026?
At Sapphire 2026, SAP announced agent-led transformation tooling that automates system analysis, code remediation, configuration, and testing to reduce ERP migration effort by more than 35% (attributed to SAP News, Sapphire 2026), with general availability starting in Q3 2026 and delivered inside RISE with SAP. It introduces named assistants across the SAP Activate lifecycle — system analysis, data management, custom code, configuration, and test management. The practical meaning for a CIO is that the market now assumes AI agents do migration work; the open question is no longer whether to use them, but whether to get that capability only inside RISE, or on your own estate with your data and ownership intact.
agent-led transformationRISE with SAPSapphire 2026S/4HANAmigration5 minWhat happens to SAP ECC after 2027, and how urgent is the migration?
SAP ECC mainstream maintenance ends in 2027, with optional extended maintenance available to 2030 at a premium. After maintenance ends you stop receiving standard support, legal and regulatory updates, and patches, which makes moving to S/4HANA a matter of when, not if. But the deadline is a planning constraint, not a reason to panic-migrate: the correct response is to size your estate now so the business case can close, then sequence the move deliberately rather than rushing a program you have not scoped. The most expensive mistake is not missing 2027 — it is committing to a multi-year migration you cannot size.
SAP ECC2027 deadlineS/4HANAmigration strategy5 minWhat is a clean core strategy for S/4HANA, and how do you achieve one?
A clean core strategy keeps the standard S/4HANA system standard and moves the extensions you genuinely need to a governed, upgrade-safe layer instead of modifying the core. The payoff is cheaper, faster upgrades, lower risk, and quicker adoption of new SAP capability. You achieve it in three moves: measure how far your estate is from clean (a Clean Core Score), retire or standardize the large share of custom code that duplicates standard capability, and re-platform the extensions worth keeping onto released APIs and extension points — side-by-side on SAP BTP, in-app with released enhancements, or with key-user tools. Clean core does not mean zero customization; it means customization that survives the next upgrade.
clean coreS/4HANASAP BTPextensibilityfit-to-standard6 minWhat happens to MV45AFZZ and SD user exits in S/4HANA?
MV45AFZZ and the classic SD user exits still technically function in S/4HANA, but clean core says stop relying on them. The better move is to read what each exit does and map it to standard capability: a static credit-limit check maps to S/4HANA FSCM (credit management), output logic maps to output management and BRF+, and pricing logic maps to the condition technique or a released BAdI. In practice many exits turn out to re-implement capability S/4 now delivers as standard and can be retired outright, while the few that encode genuine differentiation move to released extension points. The decision is not really technical — it is a business-logic question about what each exit is for.
MV45AFZZSD user exitsS/4HANAclean corecustom code6 minHow does governed agentic configuration write-back into SAP work?
Governed agentic write-back means an AI agent produces a real SAP configuration change through SAP's own mechanisms, under human control, with a full audit trail — not a raw database write. The chain is: a human issues a single-use, time-boxed approval token; the agent applies the change as a BC Set into a customizing transport in a development client; it re-reads the changed rows to verify field by field; and every attempt is recorded immutably. It has been proven live — an order type (ZWE2) was created with all 18 control fields and recorded in transport S4HK903527. The agent never touches production; whether a transport is released is decided by your existing change process.
governed configurationagentic SAPcustomizing transportBC Setclean core6 min
The short version
What is SAP fit-to-standard, and why does it matter for an S/4HANA migration?
Fit-to-standard is the analysis of how much of your custom SAP estate can move to standard S/4HANA versus what must be retired or rebuilt. It sizes the whole migration — budget, timeline, testing, and risk — so the business case can close. It is the first, cheapest, and most decisive step of an ECC-to-S/4HANA program.
What is a clean core, and do I need one for S/4HANA?
A clean core keeps the standard S/4HANA system standard and moves real extensions to a governed, upgrade-safe layer. It is strongly incentivized because the cost and risk of every upgrade scale with how heavily you have modified the core. It does not mean zero customization — it means customization that survives the next upgrade.
Should I run S/4HANA under RISE with SAP or on AWS?
Both host the same S/4HANA, so the infrastructure comparison is a tie. The real decision is ownership: RISE is a managed subscription where SAP operates your ERP and holds your data, while S/4HANA on AWS keeps you in control of your estate, your cloud, and your exit options. Agent-led migration is now available on either path, so the tie-breaker is ownership.
Can an AI agent safely change SAP configuration?
Yes, if it never touches production directly. A safely-governed agent drafts the change as a customizing transport that your existing change process approves; it applies in a development client, verifies field by field, and audits every attempt. The agent proposes; your change board disposes.