Safran Aircraft Engines
Cleaning up customer and third-party reference data ahead of the Dynamics 365 rollout, across SAP, MDM and the sales databases.
Over 4,000 customers and third parties consolidated and adjudicated before go-live.
Enterprise
You can change an ERP; you cannot replay the data
On a go-live project, the integrator owns the schedule and IT owns the budget. But what derails the go-live is almost always the quality of the migrated data. Duplicates, reference systems that disagree, history sitting in files: that gets handled before the switch, not after.
Aerospace and defenceInsurance and employee benefits
Sound familiar?
If two of these sentences get said in your organisation, the problem is no longer technical: it is organisational.
- The go-live date is set, but nobody knows how many customer records are duplicates.
- The CRM, the ERP and finance do not agree on the same accounts.
- The history sits in Excel files nobody dares to take on.
- The person who knew the transformation chain has left.
How we do it
We look at the data before we talk about the tool
Counting duplicates, gaps and inconsistencies across source systems. Without that starting picture, the project plan is a bet.
Rules get settled with the business, not among ourselves
Which record wins when there are two, which field is authoritative, what gets archived. Every call is documented: in an audit, the why matters as much as the outcome.
We rehearse the go-live, several times
Successive runs, quality indicators on each one, anomalies fixed between rehearsals. The real day should hold no surprises.
We stay on after go-live
The following weeks decide whether the business adopts the tool or builds its own parallel spreadsheet. That is where you have to be, on the ground.
Where we have already done it
Each line is a real engagement, with what was measured at the end. Where there is no figure, nothing was measured: we do not invent one.
Safran Electronics & Defense
Migration of SAP objects across maintenance, repair and overhaul, with key users supported after go-live.
Anomalies fixed before the switch, and operational continuity held in production.
Safran Electronics & Defense
Quality control of transitional data on the S/4HANA migration, along with the views and feeds behind the reporting.
A verification setup that takes the loss-of-traceability risk out of the project.
Malakoff Humanis
Taking over a pre-transformation chain on a savings migration programme, after the person who ran it had left.
Chain recovered, runs restarted on schedule, and rules documented for the next team.
The other subjects
Knowing what data you hold, and who may see it
A living catalogue, classified data, and access rules that survive an audit.
See the subjectA data platform the business actually uses
One foundation for reporting, big data and models, with autonomous teams on top of it.
See the subjectWhen nobody believes the reporting figures any more
Reports nobody opens, an obsolete platform, and teams quietly going back to Excel.
See the subjectBetween the database and the business, a layer is missing
The technical foundation is delivered, and the end user still has nothing they can use.
See the subjectDetecting what must be detected, without drowning the team
A regulatory alert engine running every day, and analysts working on cases, not noise.
See the subjectTell us where it is stuck.
Thirty minutes to lay out the subject and tell you frankly whether it is one for us. You leave with an opinion, whether you sign or not.
Book a slot30 minutes · no commitment