Master data management (MDM)
Master data management (MDM) is the discipline of creating and maintaining a single, consistent, authoritative record for core business entities—like customers, products, or vendors—across all the systems that use them.
Overview
Master data refers to the core, shared entities that many different systems and processes depend on: customers, products, employees, vendors, locations. Unlike transactional data (an individual order, a support ticket), master data is relatively stable and referenced repeatedly across the organization. The problem MDM solves is that these entities usually exist independently, and inconsistently, in many systems at once—a customer might have a slightly different name, address, and ID in the CRM, the billing system, and the support platform, with no reliable way to know they're the same person.
MDM establishes a "golden record"—a single, trusted, deduplicated version of each entity—and a process for keeping every downstream system in sync with it, or at least reconciled against it.
Core MDM processes
- Identity resolution / matching: determining that records from different systems (e.g., "Robert Smith" in one system and "Bob Smith, same address" in another) refer to the same real-world entity.
- Survivorship / merging: when duplicate or conflicting records are matched, deciding which values "win" to form the golden record (e.g., preferring the most recently updated address).
- Data stewardship: ongoing human review and correction, since automated matching is rarely perfect for edge cases.
- Distribution: propagating the golden record back out to consuming systems, or providing a canonical reference other systems can look up against.
MDM vs. general data quality/deduplication
MDM is a specific, ongoing discipline typically focused on a defined set of core entities across an entire organization, governed by dedicated processes and often dedicated software. General-purpose deduplication (removing duplicate rows in a single table or pipeline) is a narrower, more mechanical operation and is often one ingredient used within a broader MDM program, rather than a replacement for it.
Why it matters
Without MDM, the same customer can appear as multiple "unique" customers across systems, inflating counts, fragmenting purchase history, and causing operational headaches (a customer contacts support about an order placed under a slightly different account record and the agent can't find it). MDM is foundational to reliable customer analytics, accurate reporting, and regulatory processes that require a single view of an entity, like fulfilling a data subject access request under privacy law.
Relationship to data governance
MDM is often considered a core pillar of data governance: agreeing on what a "customer" or "product" record definitively looks like, and who owns changes to it, is exactly the kind of policy and stewardship question governance frameworks are designed to answer.
Related terms
Data governance is the set of policies, roles, and processes an organization uses to manage the availability, quality, security, and proper use of its data.
Deduplication →Deduplication is the process of identifying and removing duplicate records from a dataset, keeping only one representative row per logical entity.
Natural key →A natural key is an identifier that comes from real-world business data — like an email address, SSN, or product SKU — as opposed to a surrogate key generated purely for database use.
Data quality →Data quality is the degree to which data is accurate, complete, consistent, timely, and fit for the purposes it's used for—dashboards, models, and operational decisions.
FAQS
A data warehouse stores and organizes data, including master data, for analysis. MDM is a specific discipline and set of processes for establishing one authoritative version of core entities, which might then be stored in a warehouse or distributed to operational systems—MDM is about correctness and consistency of an entity, not primarily about storage or analytics.
Customers, products, vendors/suppliers, employees, and locations are the most common categories. In general, master data is any entity that's referenced repeatedly across many different business processes and systems, as opposed to transactional records generated by a single process.
MDM problems (duplicate or inconsistent entity records across systems) can appear at almost any scale, but dedicated MDM programs and software are most commonly justified at larger organizations with many systems and a high cost of inconsistency; smaller organizations often manage the same problem more informally.
