Life after Microsoft MDS
Microsoft Master Data Services (MDS) is reaching end of life as a strategic option. If your organisation still relies on it, now is the time to plan what comes next — and why that is actually a good thing.
Let’s be fair: Microsoft Master Data Services has been a good-enough solution for many organisations managing reference data and limited master data management use cases. But all good things come to an end. Microsoft explicitly states that MDS is removed in SQL Server 2025 (17.x) and that Microsoft continues to support MDS in SQL Server 2022 (16.x) and earlier versions. Microsoft’s lifecycle page for SQL Server 2022 states that mainstream support ends on January 11, 2028, and extended support ends on January 11, 2033. When the end does come, it pays to have a clear plan for what life looks like on the other side.
From workaround to proper MDM
Over the years, MDS has helped organisations build varying levels of capability around reference data management and master data management. For some, it has worked quietly and reliably for years, doing exactly what it was asked to do. For others, projects have evolved over a very long period, with increasing customisation and operational complexity.
What these projects share is a common assumption: that a low-cost or already-included MDM tool is good enough for now, and that any missing capabilities can always be built in-house when needed. Custom, artisan-crafted MDM logic, one stored procedure at a time.
Regardless of where your MDS setup falls on that spectrum, the need to modernise is unavoidable. MDS will not provide a path to full-scale MDM — not now, not in the future. Microsoft’s documentation is explicit that MDS is removed in SQL Server 2025, and supported only in SQL Server 2022 and earlier versions. That makes this a timely moment to think seriously about MDM strategy and choose a path that both protects what you already have and opens up new capabilities.
The end of MDS isn’t just a migration project — it is an opportunity to build master data management the way it should have been done from the start.
MDM is a cornerstone of the modern data platform
Master data management is not just a technical concern — it is a business-critical one. Without trusted, well-governed master data, everything built on top of it is on shaky ground: analytics can produce misleading results, AI models can learn from flawed inputs, and reporting becomes harder to rely on.
In a modern data platform, MDM is the foundation everything else is built on. Investments in data lakes, semantic models, real-time analytics, and AI all depend on the quality of the underlying master data. Getting MDM right is not always a precondition for starting — but it is a precondition for scaling with confidence.
What modern MDM actually delivers
Through work with clients migrating off MDS — and off MDS-like homegrown solutions — the same themes come up again and again when teams move to a modern master data platform:
- speed and ease of delivery — things that took weeks in MDS take days on a modern platform
- multi-domain MDM capability out of the box — customers, products, suppliers, cost centres, all in one place
- flexible hierarchy management and cross-system record matching and survivorship
- granular privacy controls and access governance that meet today’s compliance requirements
- systematic data quality improvement — and visibility into just how much poor data quality has been costing the business
That last point often comes as a revelation. Proof-of-value exercises frequently make visible the real cost of bad data — wrong addresses, duplicate records, inconsistent product hierarchies — and show what a systematic fix looks like in practice.
But MDS is free — why pay for MDM?
It is the first question many organisations ask: Why would we pay for an MDM platform when MDS is included with SQL Server?
It is a fair question, and the honest answer is that MDS has never truly been free. It carries real costs in implementation effort, ongoing maintenance, and the hidden price of the workarounds it requires.
More importantly, the cost comparison should not be framed as a license-fee question. The right frame is business-wide:
- what does it cost when a communication goes to the wrong address?
- when it does not arrive at all?
- when the same customer appears seven times in a CRM?
- when an AI model is trained on product data that is inconsistent?
A question worth asking
Master data programmes are business initiatives, not IT projects. The people who should be in the room when evaluating MDM are the ones who own business processes and feel the cost of data errors — not just the ones who manage infrastructure.
When the conversation shifts from license cost to business value, the case for modern master data management becomes significantly easier to make.
How Epical can help
Epical has hands-on experience with both MDS environments and master data management more broadly. Internal Epical material explicitly shows migration work from Microsoft Master Data Services (MDS) to Profisee, including model redesign, full data transfer, stronger integration support, and maintained traceability during migration. Separate consultant profiles also show senior MDM consulting capability across Profisee, TIBCO EBX, and Informatica MDM, alongside expertise in data governance, data migration, and data quality improvement.
That means Epical can help organisations:
- assess the current MDS landscape
- define an MDS migration path
- select the right target MDM platform
- carry out migration in a controlled way
- and strengthen governance models, data quality frameworks, multi-domain design, and integration with the wider data platform
Whether your MDS setup is a clean, well-maintained installation or something that has grown organically over many years, the migration can be approached pragmatically.
Planning your MDS migration?
If you are thinking about what comes after MDS — or just starting to map out the scope — now is the right time to assess the current setup and explore what the right path forward looks like.
For organisations across Sweden, Finland, and the wider Nordic market, the question is no longer whether Microsoft MDS end of life matters. The real question is how to turn that lifecycle milestone into a stronger master data management strategy and a more modern data platform. Epical’s public positioning describes the company as a Nordic data consultancy, which makes that regional context directly relevant.
Contact us
Ulrika Bjurinder
Business Development Executive, Epical
WE HELP YOU
Data Management & Platforms
Epical helps you build modern, scalable data platforms that support your entire organisation. By simplifying complex environments and enabling trusted data, we reduce complexity and create a strong foundation for analytics, AI, and continuous change.
