S/4HANA route planner
Where are you on the road to S/4HANA?Seven questions. Your route, against the market.
Answer as you go: the market ladder, the AgentOS pipeline and the timeline redraw with every answer. Your answers stay in this page’s address, so you can share the route.
Where is your SAP ERP today?
This places you on the market ladder on the right.
You and the market
You: Planning- No roadmap
- Planning
- Findings
- Usage scope
- Code fixes
- Conversion
- On S/4HANA
Your AgentOS pipeline
Start: Connect- 1ConnectStart hereThe /COD1/ connector on your ECC system: one abapGit package, read-only until a person allows more.
- 2FindingsNextWe start with the connector’s ATC and add SAP CCM when a check system is ready.
- 3Usage verdictNextVerdicts in days from ST03N/SWNC, job history and SUSG. SCMON starts with a person’s consent.
- 4TriageNextEach finding gets a disposition: retire, auto, pattern or manual. A person signs the list.
- 5Parallel batchesNextWaves split into batches that never share an object; agents work on them in parallel, each on its own branch.
- 6Review and transportNextA second agent reviews; a person creates the transport and approves. Nothing reaches SAP without them.
- 7VerifyNextAn item closes only when the re-run on the merged code no longer reports it.
- 8ConversionLaterFewer findings on the critical path of the conversion; the loop keeps running on S/4HANA.
Try it yourself
Run AgentOS on a sample estate.Six legacy ECC programs, fifteen real findings. You make the calls.
The findings, lines and diff are what agentos-s4 scan and codemod report on package ZKX in our sandbox. The usage history is sample data. Nothing here touches a SAP system.
Connect the ECC system
The /COD1/ connector is one abapGit package. It reads; it changes nothing until a person allows it.
Timeline
Your timeline
Indicative durations for planning a pilot, from today. Your real plan comes from the first scan of your code.
What if
Planning defaults behind the bars
- 30% of in-scope objects carry at least one finding.
- One agent lane closes 40 affected objects a week, review included.
- Greenfield carries over 30% of them.
- Triage, tests and cutover grow with the objects in scope.
- These are defaults for a first conversation; the first scan of your code replaces them.
What we would do first
Recommendations so far
- 01Scope by usage before you fix anythingUnused code is retired, not adapted. AgentOS gives a verdict per object from the history your system already has, so the first wave can start in weeks.
- 02Start without BTPThe connector’s ATC and the offline scan give the first findings on ECC. SAP’s Custom Code Migration stays the authority once you add it.
- 03Fix on ECC, before the conversionMechanical items (ORDER BY, material number types) go in codemod batches in parallel; data-model changes are planned for the S/4HANA side. SAP’s own agent needs S/4HANA 2023 or later.
- 04Close items on proof, not on promisesAn item is closed only when the re-run on merged code no longer reports it; a tester agent runs the program in SAP.
Where the market is
- ~17,000of 35,000 ECC customers will still be on ECC in 2027Gartner via CIO.com
- 54%of DACH firms still run ECC; 37% of them plan to move by the end of 2027DSAG Investment Report 2026
- 60%of S/4HANA projects run over budget and timeISG via The Register, Feb 2026
- 1,100 of 2,900executable custom reports were unused at one manufacturerabapconf 2024 (Hager Group)
- 12 monthsof SCMON and SUSG data is what SAP recommends before scopingSAP Custom Code Migration Guide 2025
- 2023+S/4HANA release SAP’s own migration agent needs; it does not run on ECCSAP Help: Custom Code Migration Agent
Pilot
Four weeks on your development system.
We install AgentOS in your environment, connect it to a DEV system and let the agents work on real items from your queue: incidents, change requests, a first wave of S/4HANA remediation or a Fiori app on BTP. You judge the result on transports.
- Week 1Installation, SAP connections, users and authorizations, your conventions as project knowledge.
- Weeks 2–3Agents work on 10–20 agreed items from your backlog.
- Week 4Review with your team: lead time, cost per item, quality, audit trail.
Bring your route to a call.We run the first scan on your own code.
Thirty minutes: your answers, the first findings from your system and a plan for the first wave.
S/4HANA route