01 What the engagement covers
One scope, five phases, delivered in order. They match our methodology exactly, because the commercial engagement and the execution are the same thing described twice.
- 01 · Audit: full extraction and profiling of the source data. Volumes, duplicates, orphaned objects, diverging reference data, accumulated exceptions. Deliverable: a quantified risk map, and an estimate that finally rests on measurement instead of assumption;
- 02 · Build: a configurable, traceable, repeatable migration chain. Every record carries its own status and its own error. Not a set of scripts written for the big day;
- 03 · Run / Fix: execution on real scopes, correction of every discrepancy, loop until stable. This is where most of the effort actually goes, and where fixed-price bids usually break;
- 04 · Dry run: the dress rehearsal at real volume, across the complete chain, with the cutover clock running;
- 05 · Go-live: cutover once everything has already been proven. A controlled step, not a bet.
02 Systems we migrate
We work on industrial ERP and PLM estates. The target system matters far less than the state of the sources, but the target model has to be known in detail to shape data for it.
Source and target coverage | Domain | Systems | Typical move |
|---|
| ERP | SAP ECC, SAP S/4HANA, IFS, homegrown legacy systems | ECC to S/4HANA, homegrown to packaged ERP, multi-instance consolidation |
| PLM | PTC Windchill, Dassault 3DEXPERIENCE, Siemens Teamcenter, PDM and file shares | Windchill to 3DEXPERIENCE, PDM to PLM, on-premise to cloud tenant |
| Data families | Master data, bills of materials, CAD and documents, lifecycles, open transactions | Qualification, deduplication, restructuring to the target model |
03 What we do not do
A service page that only lists strengths is not informative. Here is where we are the wrong call:
- We do not implement the ERP or the PLM. Configuration, functional design and training belong to your integrator. We take the data workstream, and we work alongside them;
- We do not do fast or simplified migrations. If the plan is to load a clean extract into a new tenant over one weekend, the methodology is oversized and you will pay for rigour you do not need;
- We do not sell a migration product. There is no licence at the end of the engagement. The chain we build is yours, and it stays readable by your teams;
- We do not validate on samples. If the programme cannot give access to the real data at real volume, we cannot commit to an outcome, and we will say so before signing rather than after.
04 Engagement model and budget
The audit is sold separately and first. It is short, it is bounded, and it is what makes everything after it estimable. Committing to a full migration price before the audit means pricing an unknown, which is how programmes end up renegotiating mid-flight.
Beyond the audit, engagement is time and materials against a phased plan, with the scope reviewed at each phase gate. Dedicated migration expertise typically runs between €200,000 and €1 million depending on scope, volume and source quality. That range comes from our own engagements and from published programme costs, not from a rate card.
For context on the other side of the equation: documented migration failures run into tens of millions. The expertise is well under 1% of that. We do not present this as a guarantee, it is a ratio, and it is the honest reason the line item is worth defending in a steering committee.
05 Why a specialist rather than the integrator
Your integrator is measured on the new system going live. That is the right incentive for configuration and training. It is the wrong incentive for source data, where the honest answer is often "this is worse than the plan assumed, and the date has to move".
An independent data workstream has no reason to soften that finding. It is also the only party whose sole deliverable is data that behaves in the target model. Read the long form in the ERP data migration guide or the PLM data migration guide.