The business case needs a number: how much custom code, how much of it breaks, what to shed before you move. Produced by sampling and interviews, that number takes months — and moves in one direction once discovery starts.
Custom code gets scoped by sampling, or by asking the people who wrote it. A programme gets approved on that number. Then discovery starts and the number moves — in one direction, always. An estimate you cannot trace is not a business case; it is a bet.
A Level-D object that runs a thousand times a day and a Level-D object nobody has executed since 2014 are the same line in a naive count — and completely different problems. Without usage weighting, you cannot rank the work, so remediation gets sequenced by whoever argues loudest.
The conversion completes. The system is up, the SI demobilizes, and the assumption is that everything came across. Dependencies that quietly dropped surface months later as a business problem that nobody connects back to the migration.
Every custom object classified A/B/C/D against SAP’s Cloudification Repository, weighted by real usage.
Migration blockers ordered by evidence and dependency context — so sequencing is a fact, not an argument.
The quick wins quantified: what to retire and archive now, so you carry less across.
The full picture of what you are moving — business objects, processes and enterprise structure.
Process-dependency and data-flow impact zones to shape the roadmap before you sign a partner. Beta
Independent structural validation that the operating model survived — dependencies intact, nothing silently dropped. Beta
Clean Core Assessment and Pre-Migration Cleanup are available now. S/4 Migration Planner and S/4 Migration Validator are in beta with design partners.
We build the assessment from your live system rather than from interviews. That makes the number auditable — and means it was not produced by anyone with a stake in how big the programme turns out to be.
20 minutes. Tell us your landscape — we will show what a real assessment produces.