Keep the core clean.
Move the complexity outside it.
We modernise SAP and Oracle estates without recreating twenty years of custom code in a new place. Standard processes in the core, differentiation in a composable layer around it, and a cutover you have rehearsed before the weekend it matters.
- Platforms
- S/4HANA · Fusion
- Approach
- Clean core
- Integration
- Event-driven
- Cutover
- Rehearsed, reversible
The five things that sink ERP programmes — and what we do about each
None of these are surprises. They are simply expensive to discover late, so we open every engagement by proving where you stand on all five.
Custom code nobody can account for
We inventory every modification against actual usage telemetry, then retire, re-platform or rebuild each one on the record — before the migration plan is signed.
A cutover that cannot be rehearsed
Every wave is dry-run against a production-shaped copy, with reconciliation reports and a rollback that has been executed at least once, not merely written down.
Master data that disagrees with itself
Data quality gates run continuously from week one, so duplicate vendors and orphaned cost centres surface early rather than during finance sign-off.
Integrations discovered late
Traffic on the existing landscape is captured and mapped to named interfaces, so no third system appears in UAT for the first time.
The business stops trusting the numbers
Parallel reporting runs across old and new for a full period close, with variances explained line by line before the legacy system is switched off.
One drawing every stakeholder can point at
Channels on top, a versioned API layer beneath them, an asynchronous bus in the middle, and a core kept deliberately standard. Identity, observability and controls run the full height — they are not a later phase.
Four waves, each one rehearsed before it counts
Durations below are typical for a mid-size, multi-site estate. Yours is sized during the blueprint, against your actual interface and modification inventory.
| Wave | Scope | What it delivers | Typical duration |
|---|---|---|---|
| Wave 0 | Foundation | Landscape, identity, transport routes, environments and the CI/CD path for ERP objects. | 6–8 weeks |
| Wave 1 | Finance core | General ledger, AP/AR, asset accounting. Parallel close against legacy for one full period. | 12–16 weeks |
| Wave 2 | Supply chain | Procurement, inventory, production. Phased by site, with each site rehearsed then cut over. | 16–24 weeks |
| Wave 3 | Analytics & retirement | Governed reporting model, decommission of legacy interfaces, archive with audit access. | 8–12 weeks |
What earns its place in the new core
- Processes where you genuinely differ from the market
- Integrations carrying real transaction volume
- Controls your auditors already rely on
- Historical data with a statutory retention duty
- Modifications that reproduce standard behaviour
- Reports nobody has opened in two years
- Interfaces whose consumer no longer exists
- Workarounds for constraints the new platform removes
Get the drawing before you commit the budget
A blueprint engagement returns your modification and interface inventory, the target architecture, a costed wave plan and the named risks — in four to six weeks, and yours to keep.