What is master data management?
Master data management (MDM) is the practice of maintaining one authoritative, governed record for each core business entity and distributing it to every system that needs it. Master data describes the nouns of the business: customers, products, suppliers, employees, locations, and the chart of accounts. It changes slowly compared with transactions, and nearly every transaction refers to it.
An MDM program combines a data model, matching and merging rules, a stewardship process, and software that holds the “golden record”. When the ERP, the CRM, and the e-commerce platform each hold a slightly different version of the same customer, the MDM hub matches those versions, resolves the conflicts by rule or by a steward’s decision, and publishes the surviving record back to all three.
Why master data management matters
Most reporting arguments trace back to master data. If two plants code the same part differently, inventory totals are wrong. If a customer exists three times in the CRM, revenue by account is wrong and two sales representatives call the same buyer. AI makes the problem sharper. A model trained on duplicated customers learns duplicated patterns, and an agent that looks up a supplier in two systems gets two answers. Master data management is the groundwork for a single source of truth and for data quality metrics anyone can trust.
Master data management in practice
A building products distributor grew by acquiring four regional competitors, each with its own ERP. The same manufacturer appeared as five supplier records with different payment terms. The MDM team defined a canonical supplier schema, set survivorship rules (the latest verified address wins, negotiated contract terms win over defaults), and assigned a procurement steward to review unmatched records weekly. Purchase orders now reference one supplier identifier, and spend analysis by supplier became possible for the first time.
What to watch for
- Start with one domain, usually customer or product, and prove the matching rules before adding more.
- Decide early which system is allowed to create a new master record, because uncontrolled creation brings the duplicates back.
- Budget for stewardship as an ongoing role with time set aside, since the software only proposes matches.
- Ask vendors how the hub handles records that match on some fields but conflict on others, and who makes the final call.
- Expect the hardest work to be organizational, because each department believes its version of the record is the right one.