Master data is the core reference data an organization shares across systems - customers, products, suppliers, accounts, locations. Master Data Management (MDM) is the discipline of creating and maintaining a single, authoritative version of that data so every system agrees on who a customer is and what a product is. It exists because the same customer ends up represented five different ways across a CRM, a billing system, a support tool, and a warehouse, and reconciling them by hand doesn't scale.
The golden record
The central output of MDM is the golden record: one trusted, de-duplicated, complete representation of each master entity, assembled from the fragments scattered across source systems. Building it means matching records that refer to the same real-world entity (the "Bob Smith" in the CRM and the "Robert Smith" in billing), merging them under survivorship rules that decide which source wins for each attribute, and assigning a stable master key that downstream systems reference. The golden record is what lets a "customer 360" view actually be about one customer.
Master data vs. transactional data
The distinction matters for warehouse design. Transactional data records events - an order, a payment, a click - and is high-volume and append-heavy. Master data describes the entities those events involve and changes slowly. In dimensional terms, master data is what populates the dimension tables, while transactional data fills the fact tables. Clean master data is therefore the foundation of clean dimensions - and the same customer or product entity reused across many facts is exactly what conformed dimensions formalize.
Styles and governance
MDM is implemented in several styles: a registry that leaves data in source systems and just maps the matches, a consolidation hub that pulls copies together for a golden record used in analytics, or a centralized hub that becomes the system of record other applications write to. Whichever style, MDM is as much governance as technology - it depends on data stewards to resolve match conflicts and define survivorship rules, and it underpins compliance, since you can't honor a "delete my data" request if you don't know all the records that are the same person.
Frequently asked questions
What is a golden record? A single trusted, de-duplicated representation of a master entity (customer, product) assembled by matching and merging records from multiple source systems.
How does master data differ from transactional data? Master data describes slowly-changing entities (and populates dimension tables); transactional data records high-volume events (and fills fact tables).
What are the main MDM styles? Registry (map matches in place), consolidation (build a golden record for analytics), and centralized (a hub that becomes the system of record).
Why is MDM also a governance problem? Matching and survivorship require human judgment from data stewards, and MDM underpins compliance - you can't fulfill an erasure request without knowing every record that is the same individual.