Search “MDM tool” and the results split into two useless piles. Vendor pages that describe everything and price nothing, and listicles that rank the same five names in a different order depending on which affiliate program is running that month. I run one of the tools in this category, so take the following with whatever grain of salt that requires — but the framework below is the one I would actually use, and it does not start with a feature comparison.
Master data management, at its narrowest, means one governed source of truth for the data multiple systems need to agree on — a customer record, a supplier code, a cost centre, a unit of measure — enforced at the point where someone tries to enter a bad value, not caught afterward in a report. Every product on the shortlist below claims to do that. They do not all mean the same thing by it, and they very much do not cost the same to find out.
The shortlist is five different categories wearing one label
Most evaluations start by putting Informatica, Reltio, Profisee, Semarchy and a couple of others on the same spreadsheet and scoring them against the same feature list. That comparison is the first mistake, because these are not five competitors. They are five categories that happen to use overlapping marketing copy.
Enterprise multidomain suites
Informatica (Salesforce), Reltio, SAP MDG, Stibo Systems
Govern customer, product, supplier and finance data in one platform, with match-and-merge entity resolution built in. Priced and implemented like enterprise software: a partner-led project measured in months.
Mid-market cloud MDM
Profisee, Semarchy xDM
A real step down in price and timeline from the suites above. Still cloud-first, still usually sold with an implementation partner attached. Where most mid-market shortlists actually land.
PIM sold as MDM
Stibo STEP, Akeneo, Salsify, inriver
Very good at publishing product content to many channels. Not built to govern a cost centre, a supplier record or a location hierarchy — a different job in similar-sounding marketing copy.
Open source
Pimcore, CluedIn
Free licence, real cost is developer time and the maintenance that never stops. Fine if you already have the engineering capacity in house, a second product to run if you do not.
SQL Server-native, on-premise
Primentra
Reference and structured master data on infrastructure you already run. Narrower scope than the enterprise suites by design — no match-and-merge, no product catalog — priced accordingly.
A lot of wasted evaluation time is really a category mismatch. A team with a product catalog problem takes three PIM demos before anyone notices none of them touch the supplier master. A team that needs one governed list of GL account codes ends up quoted for match-and-merge entity resolution it will never use. Sorting the category first saves more time than any scorecard does — the PIM versus MDM distinction and the MDM versus data catalog distinction cover the two mismatches I see most often.
Six questions that actually separate these tools
Once you know the category, this is the list I would work through before booking a single demo. None of it is on the comparison grids the vendors hand out.
1. Where does the data have to live. Reltio is cloud-only, full stop — no self-hosted tier at any price. If a compliance or data-residency requirement rules out cloud, that eliminates part of the field before you look at a feature list.
2. Do you actually need matching. Match-and-merge entity resolution — finding that “Acme Corp” and “ACME Corporation Ltd” are the same supplier — is the expensive part of the enterprise suites, and most mid-market teams never touch it. If the real problem is a country-code table with three spellings of Germany, that is reference data governance, not multi-domain MDM, and it is a fraction of the cost.
3. What the all-in first-year number actually is. The licence quote is never the project cost. Implementation and data migration routinely add 50 to 200 percent on top in year one, delivered by a certified partner who is not free. Ask for that number in writing before you compare it to anything.
4. Who does the implementation. Self-service in days, or a partner-led project in months. This is not a quality signal either direction — it is a staffing and timeline decision your organisation has to be honest about before it signs anything.
5. What happens to the price at renewal. Enterprise MDM contracts are not famous for capped increases. Ask directly what the year-two and year-three numbers look like, in writing, and compare that against the day-one quote rather than trusting the day-one quote alone.
6. What leaving costs you. Can you export your model and your data in a format the next tool can read, or is two years of configuration trapped in a proprietary schema. Nobody asks this on the way in. Everybody who has switched platforms wishes they had.
What it actually costs in 2026
None of the enterprise or mid-market platforms below publish a list price, so every figure here is either a publicly referenced entry point or a third-party benchmark — a shape your own quote will land inside, not a number you can hold anyone to.
Informatica MDM (Salesforce)
€100,000–500,000+/yr
Priced on record volume or capacity. Implementation runs 3–12 months with a systems integrator, and that first year commonly costs more than the licence itself.
SAP Master Data Governance
€80,000–300,000/yr
Only makes sense if you already run SAP — licensed through SAP agreements and built to sit inside an existing SAP landscape. Not really a standalone purchase.
Reltio
$20,000–50,000+/yr, scales with volume
Cloud-only, no self-hosted option at any tier. Purpose-built for Customer 360 with ML-based entity resolution — strong when that is the actual problem.
Profisee
€30,000–150,000+/yr
Deep Microsoft integration and real data stewardship depth. Per-user or per-record licensing, with a 2–6 month partner-led rollout the norm rather than the exception.
Semarchy xDM
€20,000–80,000+/yr
The closest of the enterprise-adjacent field to a mid-market budget. Cloud-first, so hosting and an implementation partner sit on top of the licence figure.
Primentra
€7,500/yr flat
Unlimited users, no per-record or per-seat scaling, renewal increases capped at Dutch CPI. Self-hosted on the SQL Server you already run, live in about a day.
The enterprise names share a shape, not a size: quote-only pricing, a licence that is a fraction of the true first-year cost, and a renewal structure nobody mentions until year two. A multi-month evaluation with a named account executive works better for the vendor when the number stays soft until the relationship is established. Most buying guides skip past that entirely and rank the field by feature checklist, which is the wrong place to start.
Where Primentra fits, and where it plainly does not
We built Primentra for one slice of the categories above: SQL Server shops that need governed reference and structured master data — entities, hierarchies, domain values, business rules, approvals, a field-level audit trail — without paying enterprise-suite prices for match-and-merge capability they will never exercise. On your own SQL Server, installed in about a day, €7,500 a year flat with unlimited users, renewal increases capped at Dutch CPI rather than whatever the account team negotiates that year.
It is not the right pick in a few specific situations, and I would rather say so here than have you find out after a 60-day trial. If you need cloud-native multi-region deployment, Primentra is on-premise only and that is not changing. If your core problem is entity resolution at scale — deduplicating millions of customer records with machine-learning-based matching — Reltio is built for exactly that and we are not. If you are not a SQL Server shop, the entire pitch stops applying, since the product is deliberately native to that platform rather than portable across databases. And if the actual need is a product catalog with channel syndication, that is a PIM problem, not an MDM one, and no amount of reference data tooling fixes it.
Where it does fit: a mid-market team, usually one that has just found out Microsoft removed Master Data Services from SQL Server 2025, that needs one governed source for the data feeding its ERP, its reporting and its integrations, on infrastructure it already runs, without a six-figure line item or a partner-led project measured in quarters. The full 2026 alternatives comparison puts the wider field side by side with pricing attached, and the individual comparisons against Profisee and Semarchy go feature by feature.
Figure out which of the five categories you actually need before anyone shows you a screen. Get the all-in first-year number and the renewal terms in writing. And if a vendor cannot answer either question plainly, that tells you something too.
Common questions
How do I choose an MDM tool?
Answer three questions before any demo. Where must the data live — cloud-only, or does it need to stay on-premise? Do you need multi-domain matching to merge duplicate records, or is the real problem a handful of reference values that disagree between systems? And what does the true first-year cost look like once implementation and migration sit on top of the licence. Those three answers cut most shortlists in half.
How much does an MDM tool cost in 2026?
Enterprise platforms — Informatica, SAP MDG, Reltio — run roughly €80,000 to €500,000+ a year before implementation, which is often as large again in year one. Mid-market cloud tools like Profisee and Semarchy land between about €20,000 and €150,000. Primentra is a flat €7,500 a year, unlimited users, because reference data governance is a narrower problem than the enterprise suites are priced to solve.
What's the difference between an MDM platform and a data catalog?
An MDM platform creates and enforces the one correct value — the golden record — at the point of entry. A data catalog indexes and documents data that already exists elsewhere so people can find it. Buying a catalog to fix a data quality problem is a common mismatch: it describes the mess in detail without cleaning any of it up. The full breakdown is in the piece on MDM versus a data catalog.
Do I need multi-domain MDM, or just reference data governance?
If two systems hold slightly different versions of the same customer or supplier and you need automated matching to find and merge the duplicates, that's multi-domain MDM with match-and-merge — Informatica, Reltio, Profisee territory. If a country code, unit of measure or status value just diverges between systems and needs one governed source, that's reference data: narrower, cheaper, and a lot faster to stand up.
Is on-premise MDM still realistic in 2026?
Yes, and for a SQL Server shop it often removes a whole category of question from the evaluation. Reltio, for one, is cloud-only with no self-hosted tier at all, so a hard data-residency requirement ends that conversation on its own. Infrastructure you already run, already back up and already secure is frequently the simpler procurement, not the dated one.
What should I ask on the first MDM demo?
Ask for the all-in first-year number in writing, not the licence figure alone. Ask what happens to price at renewal — plenty of enterprise contracts carry uncapped annual escalators nobody mentions in the first call. Ask what happens to your data and configuration if you leave after year two. A vendor who answers that third question without flinching is usually the one worth shortlisting.
If the answer is reference and master data, not entity resolution
One number, €7,500 a year, unlimited users, on the SQL Server you already run. The 60-day trial is the full product, not a limited demo, which will tell you more in an afternoon than a fourth sales call will.