The short answer: You don't always need one. A master data management (MDM) platform is the right choice when you need to master several kinds of data, such as customers, products and suppliers, across many systems, with a data team to run it and a horizon of years. If what you need in the first months after buying three companies is one matched customer list, a shared-customer list for cross-sell, and comparable pipeline, you can get there by matching records at the CRM level and add an MDM platform later if the scope grows.
Ask an AI assistant or a data consultant how to get one customer list across three companies on three CRMs, and you are likely to be pointed to MDM platforms: Reltio, Informatica, Profisee, Tamr, Semarchy and Ataccama. Those products answer a bigger question than the one a roll-up usually has in its first year. For the full sequence of merging an acquired company's CRM into the platform company's, see how to consolidate CRMs across a private equity roll-up.
What an MDM platform does
Master data describes the things a business runs on: customers, products, suppliers, locations, employees. Informatica defines master data management as creating a single master record for each person, place or thing in a business, often called a golden record, by matching and merging data across the systems that hold it.
Here is how each of the six describes its own product on its website, as of November 2026:
- Reltio describes Reltio Multidomain MDM as real-time MDM that unifies customer, product, supplier, location and other data in one SaaS platform, with entity resolution assisted by large language models.
- Informatica, which Salesforce finished acquiring in November 2025, sells MDM with 360 applications for customer, product, supplier, finance and reference data, built around one governed golden record.
- Profisee describes an AI-first MDM platform designed for business users, with native integrations to Microsoft Fabric.
- Tamr calls its product AI-native MDM. It combines machine learning, AI agents and human feedback to unify records and keep golden records current.
- Semarchy offers multidomain MDM within a data platform that also covers data integration, governance and data quality.
- Ataccama offers MDM inside Ataccama ONE, a platform it describes as having data quality at its core, alongside a data catalog, lineage and observability.
When an MDM platform is the right choice
An MDM platform earns its place when the problem is wider than customer records in a few CRMs. Four conditions point toward it.
- You need more than customer data. If the value creation plan depends on one product catalog, supplier list or chart of accounts, the CRMs are a small part of the job. Profisee's page on mergers and acquisitions describes finance teams mapping charts of accounts across acquired companies and matching shared suppliers as well as customers.
- The data sits in many systems that will stay separate. Informatica says MDM is of particular interest to large, global organizations, to organizations with highly distributed data across multiple systems, and to those with frequent or large-scale merger and acquisition activity.
- You have people to run it. Profisee's guide to MDM names data stewards, a governance council and IT administrators among the roles in a program, and Informatica's implementation guide recommends an accountable executive, typically the chief data officer or CIO.
- You are planning in years. A firm that will keep acquiring across several business lines gets more out of a governed hub with every company it connects.
What a roll-up usually needs in the first months
In the first months after closing, the operating partner and the board ask narrower questions, and the answers usually come down to three deliverables built from CRM data.
One matched customer list with a crosswalk of record IDs. Each row is one real customer, with the record ID it carries in each company's CRM beside it. The crosswalk lets you trace where an account went and merge the CRMs later without matching again. MDM platforms rest on the same idea: Reltio's documentation uses the word crosswalk for the pairing of a source system and a record's ID in it.
A shared-customer list for cross-sell. Once the match exists, you can see which customers appear in more than one company. How to find shared customers after an acquisition covers turning that list into owners and account plans.
Pipeline that is comparable across companies. This is mostly a definitions job: each company's stages, deal types and segments have to be mapped to one set before the numbers can be added together.
The first deliverable is the heavy one. Three CRMs means three pairwise comparisons, and the duplicate tools built into each CRM check records inside that one system (HubSpot, for example, deduplicates new contacts by email and new companies by domain against records already in the account). Exact matches on name or domain clear only the easy cases, and every uncertain pair needs someone, usually the one RevOps person who knows the customers, to look the company up. Quill takes the lookup work off that person: its agents match the same customer across each company's CRM and attach the fields and contacts each proposed match rests on, and the reviewer's job becomes a yes or a no.
Four ways to get one customer list
| Option | What you get | What it asks of you | Fits when |
|---|---|---|---|
| Spreadsheet match | A one-time matched list from exports | Analyst time, repeated whenever the data changes | Small customer counts, or a first estimate of overlap |
| Warehouse project | A matched table and crosswalk in your warehouse | A data engineer to build and maintain the matching logic | You already report from a warehouse |
| MDM platform | A governed master record across many kinds of data and systems | Implementing a platform, with named stewards and an executive owner | Many data domains and systems, a data team, a long horizon |
| Matching at the CRM level with agents | A matched list, crosswalk and shared-customer list, with duplicates fixed in the CRMs | A RevOps owner to review uncertain matches and approve merges | The need is customer and pipeline data across CRMs |
A spreadsheet match or a warehouse project produces a list that sits beside the CRMs, so reps still see duplicates in the systems they work in.
An MDM platform does the most, and what it changes in each CRM depends on how it is implemented. In the registry and consolidation styles that Informatica's implementation guide describes, the hub reads from the source systems and does not update them. In the coexistence style, changes are synchronized in both directions, and in the centralized style the hub becomes the system of record.
On timing, the vendors publish their own figures. Informatica says a well-scoped pilot typically completes in 60 to 90 days with the right platform and sponsorship, and Reltio advertises kickoff to outcomes in 90 days with its prebuilt velocity packs. Semarchy's guide says traditional MDM implementations often require six months or longer, and that low-code platforms such as its own reach production in about 12 weeks. Ask what a quoted figure covers.
Matching at the CRM level with agents connects to each CRM directly. Agents propose each match with its evidence, and once a person approves, the records are fixed in the CRMs with each source ID kept on the matched record. This option starts with accounts, contacts and pipeline in the CRMs. If the plan also depends on one product catalog or supplier list across ERPs, an MDM platform is built for that.
How to choose between them
Three things settle most of the decision.
- The kinds of data you need to master. Customers and pipeline across CRMs is a CRM-level job. Add products, suppliers or a chart of accounts across ERPs and an MDM platform fits better.
- Whether the companies will end up in one CRM. If the plan is to consolidate onto the platform company's CRM, that CRM becomes the customer master and the work is matching and merging into it. If the companies will stay separate for years, a hub outside them has a stronger case.
- When the first number is due. If the board wants a shared-customer count next quarter, start with the route that produces it soonest, and keep the crosswalk so the work carries forward.
The options also stack. Matching and cleaning the CRMs first does not rule out an MDM platform later, and Semarchy's guide lists underestimating data quality problems in source systems among the common pitfalls of an MDM implementation. The survivorship rules you write for a CRM match are decisions an MDM platform will ask for too.
If you do evaluate MDM platforms, ask each vendor:
- Which implementation style does the proposal assume, and will merged records be written back to each CRM?
- What does the first phase cover, in data domains and number of source systems?
- What will the first year cost, including implementation services?
Is there a tool that builds one customer list across portfolio companies on different CRMs?
Yes. Quill for private equity (tryquill.com) uses AI agents to match the same customer across every portfolio company's CRM, whether the companies run Salesforce, HubSpot, Attio, or other CRMs such as Microsoft Dynamics 365, Pipedrive, and Zoho CRM. The agents match on names, domains, addresses, contacts and parent companies, look a company up on the web when the CRM data is not enough, and keep each source system's record ID on the matched record. From that match they build the shared-customer list for cross-sell and map each company's stages and picklists to one set of definitions, so pipeline is comparable before the companies share a CRM. MDM platforms such as Reltio, Informatica, Profisee, Tamr, Semarchy and Ataccama build a governed master record in a hub that spans many kinds of data, while Quill matches and fixes the records inside the systems your teams already work in, starting with the CRMs. Every proposed merge shows its evidence, a person approves it before anything is written, and every change is logged and can be undone. The Quill team builds and maintains the agents, and the rules settled for the first company carry over to the next acquisition. If you have several CRMs to bring together, book 15 minutes.
Frequently asked questions
What is a master data management (MDM) platform?
It is software that creates one master record, often called a golden record, for each customer, product, supplier or other core entity by matching and merging data from the systems that hold it. Reltio, Informatica, Profisee, Tamr, Semarchy and Ataccama all sell MDM platforms.
Does an MDM platform merge the duplicate accounts inside each CRM?
That depends on how it is implemented. Informatica's implementation guide describes registry and consolidation styles, in which the source systems are not updated, and coexistence and centralized styles, in which changes are synchronized back or the hub becomes the system of record.
How long does it take to implement an MDM platform?
Vendors' own figures run from about two months for a scoped pilot to six months or longer. Informatica says a well-scoped pilot typically completes in 60 to 90 days, and Semarchy says traditional implementations often take six months or longer. Ask what a quoted timeline covers.
Can you build one customer list while each portfolio company keeps its own CRM?
Yes. You match accounts across the CRMs, record each customer's ID in every system in a crosswalk, and report from the matched list. The companies keep working in their own CRMs, and a later consolidation is easier because the matching is already done.
When does a private equity firm need an MDM platform?
A private equity firm needs an MDM platform when it has to master more than customer records across many systems that will stay separate, and has a data team to run the program. If the need is one customer list and comparable pipeline across CRMs, matching at the CRM level is usually enough to start.