Summary
SAP MDG is a mature product built for organizations that run SAP. If you don't run SAP, evaluating it is a waste of time. For teams migrating away from Microsoft MDS — which is SQL Server native, not SAP native — Primentra is the direct replacement: same infrastructure, built-in migration tooling, at a fraction of the cost.
What is SAP Master Data Governance?
SAP Master Data Governance (MDG) is a master data management solution built and sold by SAP. It is designed to centralize and govern master data across an SAP landscape — primarily materials, vendors, customers, and financial data objects within SAP ERP environments. The product is deeply integrated with SAP workflows, change request management, and approval processes native to the SAP platform.
SAP MDG runs on either SAP BTP (Business Technology Platform) in the cloud or on-premise SAP systems. It is not a standalone product — it is part of the SAP ecosystem. The data model, integration points, and governance processes it supports are designed around SAP's own master data structures: SAP material numbers, vendor master records, customer master records, and GL account hierarchies. This tight coupling is what makes it powerful for SAP shops and largely irrelevant outside them.
Implementation typically requires certified SAP consultants. The configuration surface is substantial — SAP MDG covers change request workflows, consolidation rules, mass processing, data replication across SAP systems, and governance framework configuration. For an organization with a mature SAP practice, this capability is meaningful. For an organization without one, it represents months of engagement before any value is realized.
SAP MDG is a serious product. It handles real governance challenges at scale for enterprises with complex SAP landscapes. This post is not a criticism of what it does — it is a practical guide to whether it applies to your situation.
What is Primentra?
Primentra is a reference data management platform built to run on SQL Server. It is designed as a direct replacement for Microsoft Master Data Services (MDS) — same infrastructure, different product, without the MDS limitations. You model your entities, define domains and hierarchies, and manage records through a grid-based UI. Data lives in your SQL Server. There is no third-party cloud dependency and no SAP involvement.
Setup is self-service. You connect Primentra to an existing SQL Server instance, import your MDS models or start from scratch, and you are operational the same day. Pricing is €7,500/year flat for unlimited users. No professional services are required to get started, and no per-seat fees accrue as your team grows.
Feature comparison
| Dimension | SAP MDG | Primentra |
|---|---|---|
| Self-service setup (no consultants) | ✗ | ✓ |
| MDS migration wizard | ✗ | ✓ |
| Flat pricing, unlimited users | ✗ | ✓ |
| Works without SAP | ✗ | ✓ |
| On-premise SQL Server | ✗ | ✓ |
| SAP ERP integration | ✓ | ✗ |
| Excel-like grid editing | ✗ | ✓ |
| Approval workflows | ✓ | ✓ |
| Business rules engine | ✓ | Roadmap |
| Hierarchy management | ✓ | ✓ |
| Audit trail / compliance | ✓ | ✓ |
| API access | ✓ | ✓ |
The ecosystem question
SAP MDG is not a general-purpose master data management tool that happens to integrate well with SAP. It is an SAP tool, full stop. The data it governs is SAP data. The workflows it manages are SAP change requests. The systems it replicates to are SAP systems. Evaluating it as a standalone MDM option is a category error — like evaluating Salesforce as a general-purpose CRM when your entire operation runs on Microsoft Dynamics.
If your organization does not run SAP ERP, there is no layer of SAP MDG that benefits you. The product has no mechanism to govern reference data stored in SQL Server, no connection to non-SAP systems, and no data model that maps to generic master data structures. You would be licensing a sophisticated governance layer for a platform you do not own.
This is not a subtle distinction. It is the first question to answer before spending any time on an SAP MDG evaluation: does your organization run SAP? If the answer is no, close the tab.
Why MDS teams end up looking at SAP MDG (and why they usually don't choose it)
When Microsoft announced the end of active development for Master Data Services, teams evaluating replacements ran the obvious searches. SAP MDG appears on most MDM vendor lists. Analyst reports and comparison matrices include it alongside products like Informatica MDM, Semarchy, and others — for a side-by-side of all the main options, see our MDS alternatives roundup. It looks like a reasonable candidate if you are scanning a category shortlist without filtering by ecosystem first.
Most teams figure out the problem quickly once they get into the details. The infrastructure requirements alone — SAP BTP or on-premise SAP — eliminate the option for any organization running SQL Server without an SAP estate. The ones that take longer are typically those that have partial SAP exposure (a single SAP module, for instance) and wonder whether it qualifies. In nearly every case, the answer is no: SAP MDG is built for organizations where SAP is the system of record, not for organizations that have a single SAP integration alongside a broader Microsoft or Azure stack.
Pricing and total cost of ownership
SAP MDG pricing runs through SAP's licensing model, typically between €80,000 and €300,000 or more per year depending on scope, modules, and deployment model. That figure assumes you already have the underlying SAP platform licensed — the MDG layer sits on top of an existing SAP investment. If you are not already an SAP customer, the real cost of SAP MDG includes the cost of becoming one. For most non-SAP organizations, that makes the total cost comparison academic.
Primentra is €7,500/year, flat, with no user limits and no additional platform dependency. It runs on the SQL Server instance you already have. Implementation is self-service — there are no professional services required to go live. Over a three-year horizon, the difference between the two products for a non-SAP organization is the difference between several hundred thousand euros and a few tens of thousands. The comparison matters most when teams are trying to justify the evaluation effort itself.
Deployment and setup
SAP MDG deployments are substantial projects. Whether on SAP BTP or on-premise SAP, the configuration involves setting up the SAP governance framework, defining change request types, mapping the SAP data model to your organizational structure, configuring replication rules, and integrating with SAP approval processes. Certified SAP consultants are a practical requirement, not an optional add-on. Go-live timelines are measured in months.
Primentra deploys in a day. You point it at a SQL Server instance, run the schema setup, and connect to the UI. From there you define your models, configure domains, and start loading data. There is no certification requirement, no middleware, and no prerequisite platform to stand up first. For teams whose current challenge is finding a working MDS replacement before a deadline, the deployment timeline difference is significant.
MDS migration path
Microsoft MDS stores its data in SQL Server. Models, entities, domains, hierarchies, and member records all live in a SQL Server database. Any migration path that takes that data somewhere useful needs to understand that structure. Primentra includes a built-in migration wizard that reads directly from an existing MDS database, maps entities and attributes, and imports members and hierarchies into the Primentra schema. The process is guided and does not require manual export/import scripting. For the full step-by-step process, see How to Migrate from Microsoft MDS.
SAP MDG has no equivalent path from MDS. There is no SAP tooling designed to ingest SQL Server MDS exports, and the SAP data model does not map naturally to MDS entity structures. A migration from MDS to SAP MDG would require custom extraction, transformation, and loading work — built from scratch, by SAP consultants, into a platform that was not designed for the source data. For most MDS migrators, this rules SAP MDG out at the technical level before pricing or ecosystem fit even enters the conversation.
When SAP MDG is the right choice
SAP MDG is genuinely the right tool for organizations where SAP is the primary system of record and master data governance needs to happen within the SAP landscape. If your material master, vendor master, and customer master all live in SAP, and your governance processes need to be embedded in SAP change request workflows, SAP MDG is a natural fit. It is a mature product with a long track record in large enterprise SAP environments.
The organizations for whom SAP MDG works well have usually already made the SAP commitment — they have licensed SAP, they have an internal SAP team or a trusted SAP partner, and they are extending their SAP investment into the governance layer. For those organizations, this post is not relevant. For everyone else, it is.
Choose SAP MDG if...
- Your organization runs SAP ERP and needs to govern master data across the SAP landscape
- SAP is your primary system of record for materials, vendors, or customers
- You already have SAP consultants and a licensed SAP environment in place
- You need native integration with SAP workflows and approval processes
Choose Primentra if...
- You are not a SAP shop — SAP MDG has no practical value outside SAP environments
- You are migrating from Microsoft MDS, which runs on SQL Server, not SAP
- You want to be live in a day without SAP consultants or SAP licensing
- You need on-premise SQL Server as your data store
Verdict
SAP MDG is native to the SAP ecosystem. If your organization runs SAP ERP and needs to govern master data across your SAP landscape, it is the obvious choice. It handles real complexity for large SAP deployments and has a long track record in that specific context.
Outside of SAP environments, it is impractical. There is no infrastructure to run it on, no data model it connects to, and no migration tooling for SQL Server sources. The cost of becoming an SAP customer in order to use SAP MDG exceeds the cost of the MDM problem you are trying to solve by a wide margin.
For teams migrating from Microsoft MDS — which runs on SQL Server, not SAP — SAP MDG is the wrong tool entirely. Primentra is the closer replacement: same SQL Server foundation, built-in MDS migration wizard, self-service setup, and flat pricing at €7,500/year with unlimited users. If you are not a SAP shop, stop evaluating SAP MDG and use that time to run a real MDS replacement trial instead.
Frequently asked questions
Common questions about SAP MDG and Primentra.
Should I use SAP MDG if I am migrating from Microsoft MDS?
Almost certainly not. Microsoft MDS runs on SQL Server. SAP MDG runs on SAP BTP or on-premise SAP. They serve different ecosystems. Unless your organization is already committed to SAP and your goal is to bring MDS-style governance into the SAP landscape, SAP MDG is not a natural migration target. Primentra is the closer replacement — same SQL Server foundation, built-in MDS migration wizard.
What does SAP MDG do that Primentra does not?
SAP MDG provides native governance for master data within the SAP ecosystem — materials, vendors, customers, financial objects. It integrates deeply with SAP workflows, approvals, and change documents. Primentra does not integrate with SAP. For non-SAP environments, SAP MDG offers nothing you need.
How much does SAP MDG cost compared to Primentra?
SAP MDG uses SAP licensing, typically running €80,000–300,000+/year — and that assumes you already have the underlying SAP platform licensed. Primentra is €7,500/year flat with unlimited users and no additional platform dependency. If you are not already a SAP customer, the comparison is not even close.
Can SAP MDG work outside of SAP environments?
No. SAP MDG is designed for SAP shops. It runs on SAP BTP or on-premise SAP systems and is tightly integrated with the SAP data model. Using it without SAP is not a supported or practical configuration.
What is the best MDS alternative for a non-SAP organization?
Primentra is the closest replacement for Microsoft MDS in non-SAP environments. It runs on the same SQL Server infrastructure, includes a built-in migration wizard, and covers the reference data management use cases most MDS teams relied on — at €7,500/year with unlimited users.
If you are not a SAP shop and are evaluating MDM options after Microsoft MDS end-of-life, Primentra is worth 60 days of your time. Try it free →
- Runs on your existing SQL Server — no SAP required
- No professional services required — self-service from day one
- No credit card for the trial