Services
ERP work, judged on what happens after go-live
S/4HANA migration and upgrades, custom code remediation, data migration, and long-run application management – across SAP and Oracle estates.
ERP programmes rarely fail at the design stage. They fail in data migration, in the custom code nobody documented, and in the six months after go-live when the business is still working around the system. That is where we concentrate.
What we deliver
S/4HANA migration and upgrades
Brownfield conversion, greenfield implementation or selective data transition – chosen on the evidence of your estate rather than by preference. Includes readiness assessment, sizing, cutover planning and rehearsed fallback.
Custom code remediation
The unglamorous work that sinks conversions. We inventory every custom object, classify it by whether it is used, compliant and worth keeping, then remediate or retire it. Most estates carry far more dead code than anyone expects.
ERP data migration
Extraction, cleansing, mapping, load and – the part usually underestimated – reconciliation that proves the loaded data ties back to source. With a dress rehearsal before the real cutover.
Application management
Ongoing functional and technical support for live ERP: incident and problem management, enhancements, release and transport management, and month-end support when it actually matters.
Process transformation and mining
Analysing how your processes actually run, from system event data rather than from workshops. It reliably finds the variants, rework loops and manual workarounds nobody mentions in a requirements session.
Platform extensions and integration
Building extensions on the ERP vendor's platform rather than modifying the core, so upgrades stay cheap. Plus the integration work connecting ERP to everything around it.
Where we are honest with you
We do not sell ERP licences, so we have no incentive to recommend a bigger footprint than you need. Two things we say more often than clients expect:
Sometimes the answer is not to migrate
If your current release is supported, stable and the business is not blocked by it, a conversion may be the wrong use of a large budget this year. We will tell you that.
Clean core beats clever customisation
Every modification you carry is a cost at every future upgrade. We push hard for extensions over core changes, even when a modification would be faster to deliver now.
How an ERP engagement runs
- 01
Assess
Inventory of the estate: releases, modules in real use, custom objects, interfaces, data volumes and quality. Ends with a costed options paper, not a recommendation you cannot audit.
- 02
Prepare
Target architecture, migration approach, data strategy and cutover plan. Custom code remediation starts here, because it determines the timeline more than anything else.
- 03
Build and test
Configuration, extensions, interfaces and data loads, delivered in increments. Multiple migration rehearsals – the first one always finds something.
- 04
Cut over
A rehearsed runbook with named owners, go/no-go criteria agreed in advance, and a fallback that has actually been tested.
- 05
Hypercare and steady state
Intensive support through the first close, then transition to managed application support with documented runbooks.
SAP estates
S/4HANA and ECC, conversion and upgrade programmes, custom code remediation, data migration, BTP extensions, and application management.
Oracle estates
E-Business Suite implementation, upgrade and support, database administration and middleware, plus reporting and analytics on Oracle stacks.
Facing a conversion deadline?
Tell us your current release and the size of your custom code base. That is usually enough for a first useful conversation.
Start a conversation