S/4HANA migration: the master data decision you make too late
Every S/4HANA programme says data migration is a workstream. Few treat it as the critical path it is. The cutover date will not move because the data is not ready.
Nexolve TechnologiesDelivery team
The discovery that arrives in month nine
The blueprint is signed, configuration is underway, and then someone profiles the vendor master. Duplicates across entities, bank details of uncertain provenance, materials described in free text by plant. The migration workstream triples in size overnight, and the cutover date does not move.
This is predictable. Master data quality is invisible until you profile it, and most programmes profile it late because early attention goes to process design.
Profile in week two, not month nine
Run data profiling in the first fortnight of the programme: business partner, vendor, material and purchasing views, across every entity in scope. The output is not a cleansing project yet — it is a scope statement. You now know what the migration will actually cost.
Governance design comes next: who owns a vendor record, who can create a material, what validation runs at creation. Cleansing without governance is re-done within a year.
Why this matters double for procurement
Procurement platforms inherit the core's data. An Ariba rollout on top of unprofiled vendor masters produces duplicate suppliers, broken catalogues and matching exceptions — and the platform gets blamed for the data underneath it.
Sequence it honestly: profile early, govern before you cleanse, and align the MM scope with the platform design above it. Boring, dated, and the difference between a cutover that holds and one that slides.
