
I'm an SAP MDG consultant. Not a data migration consultant.
They sound similar, but they solve different problems:
- Data migration moves data once, at go-live, from the old system to the new one.
- MDG governs master data for as long as the system lives: who can create or change it, who approves it, how it's validated, and how it's replicated to every system that depends on it.
Treat MDG like a migration project and you end up with a one-time cleanup that decays within months, with no owners, no rules and no approval flow.
If your plan says "MDG is just migration with a UI", pause and ask who will own the data a year after go-live.
Migration gets your data in. Governance keeps it right.