Readiness assessment
Simplification items, custom code, add-on compatibility and data volume, measured rather than estimated.
Enterprise SAP Migration
ECC to S/4HANA, on a path built around your data.
Brownfield, greenfield or selective. Which one is right depends on how much of your history you need, how much custom code you carry, and how long the business can be without the system. We work that out before we propose a route, not after.
Reduce, then move
Data volume comes down before the conversion, so the window comes down with it.
Custom code assessed early
Remediation scoped at the start rather than discovered during a trial run.
Rehearsed cutover
Nobody finds out how long it takes on the night it matters.
The problem
The deadline is real, and the runway is shorter than it looks.
ECC mainstream maintenance ends on 31 December 2027. A full migration takes 18 to 36 months. Work backwards from a go-live and an assessment starting after mid-2026 leaves very little room for a considered decision.
The window shrinks while you decide
Every quarter spent choosing is a quarter removed from the build, and the parts that get compressed are testing and training.
Volume decides the downtime
Cutover length is a function of how much data moves. Most estates could move considerably less than they plan to.
Custom code is an unknown until it is measured
Clean Core is not an abstraction here. Every unremediated object is either rework later or a blocker to what comes after.
Brownfield carries your problems across
A conversion keeps your history and your customisations, which also means it keeps whatever is wrong with them.
The cheapest terabyte to migrate is the one you decide not to take with you.
How we open every migration
What we do
Three routes, and the work of choosing between them.
Most of the value in a migration is decided before the conversion starts. These are the pieces that decide it.
Brownfield conversion
A system conversion that keeps your history and configuration, with the cleanup done deliberately rather than inherited.
Greenfield build
A fresh implementation on standard, with only the data and the processes worth carrying forward.
Selective data transition
The middle route: a new system with chosen history, company codes or entities brought across.
Custom code remediation
Objects assessed, retired, remediated or rebuilt, so the core stays clean enough to take future releases.
Cutover and downtime planning
A rehearsed cutover with real volumes, so the window you promise the business is the window you need.
How it runs
Five stages, with the data work first.
The order is the argument. Reducing before converting shortens every stage that follows and lowers the infrastructure the target system needs.
- 1
Readiness
Measure volume, custom code, add-ons and simplification impact. Decide the route on evidence.
- 2
Reduce
Archive and retire what does not need to travel, so the conversion moves the estate you want.
- 3
Design
Target architecture, remediation plan, integration map and a cutover approach with a downtime estimate attached.
- 4
Rehearse
At least one full trial conversion with production volumes, then tune until the window fits.
- 5
Cut over
The real thing over a planned window, followed by hypercare and then decommissioning of what you left behind.
Who this is for
This is the right page if any of these are true.
- You are on ECC and have not started an assessment.
- You have a migration plan but no downtime estimate you trust.
- Your custom code footprint is large and nobody has measured it.
- You are weighing brownfield against greenfield with no evidence either way.
- A previous attempt stalled and you need an honest read on why.
What this does not do
A migration will not modernise processes on its own. A conversion in particular reproduces how you work today, faster and on newer infrastructure.
If your estate is small, clean and mostly standard, the honest answer may be a shorter greenfield build rather than the larger programme a conversion implies.
Often bought with
These usually come up in the same conversation.
Find out how long yours would take.
A readiness assessment gives you the route, the effort and a downtime estimate you can take to the business. It is the fastest way to turn the 2027 date into a plan.