Microsoft MDS to CluedIn: a technical migration guide for SQL Server, Fabric and Purview

First, what does Microsoft actually say?

Microsoft's current position on Master Data Services is straightforward.

Microsoft also confirms that MDS remains supported in SQL Server 2022 and earlier versions.

That distinction is important. There is time to migrate properly. There is considerably less justification for designing new architecture around MDS.

And where does CluedIn appear?

This is where the history becomes useful. Microsoft's Architecture Center repository contains a reference architecture titled:

The live Architecture Center has evolved since then, but the original MicrosoftDocs architecture metadata remains publicly visible. That matters because it establishes that the CluedIn/MDS relationship did not appear only after Microsoft removed MDS from SQL Server 2025.

A Microsoft-hosted presentation from 2022, End-to-end Data Estate Lineage with Purview and CluedIn, also includes that same MDS migration architecture in its resource material.

Source: Microsoft-hosted presentation

The Microsoft references did not disappear with the old MDS architecture

The current material has moved on from MDS migration specifically and into the wider MDM architecture. Microsoft Learn currently has a dedicated page titled Microsoft Purview and CluedIn integration for master data management.

That page covers ingestion, data quality, mastering, governance, graph relationships and downstream data delivery.

Microsoft also publishes a current guided project for building a complete master data management and data governance stack using Microsoft Purview and CluedIn.

The training walks through Azure Data Factory, CluedIn ingestion, streaming data back to ADLS, deduplication, cleaning, enrichment and Purview scanning.

Source: Microsoft Learn guided project

What does an MDS migration actually involve?

This is where migration projects often underestimate the problem. MDS is rarely just a database.

Three technical paths from MDS into CluedIn

There is no requirement to switch MDS off before CluedIn comes online.

How MDS concepts map into CluedIn

Some concepts map cleanly. Others should change.

Technical mapping: CluedIn MDS migration playbook

Do not copy MDS business rules line for line

An MDS business rule can do several different jobs.

It might validate a value. It might set a default. It might determine whether a record is valid enough to publish. It might trigger something operational.

Years later, all of those behaviours can be buried inside the same rule estate.

In CluedIn, validation, data quality, survivorship, workflow and publishing logic can be separated into the controls that actually own those responsibilities. That is more useful than recreating old coupling because "that is how MDS did it."

Subscription views deserve special treatment

In many MDS environments, subscription views are where the real operational dependency lives.

That is why CluedIn's adoption guidance recommends starting with consumers and contracts rather than attempting to perfect the whole model first. In CluedIn, mastered data is typically distributed using Streams and Export Targets.

What happens to hierarchies?

Do not flatten them because it makes migration easier. Parent-child structures, product hierarchies, customer ownership structures and organisational relationships often contain genuine business meaning.

CluedIn's graph-native model treats relationships as first-class elements rather than forcing all that context back into denormalised tables.

What about the MDS Excel experience?

This deserves attention because many people experience MDS through Excel rather than through architecture diagrams.

CluedIn's technical guidance does not assume every manual maintenance process should simply be reproduced. Modern stewardship may use forms, governed workflows, application interfaces, controlled ingestion patterns or Power Platform experiences depending on the use case.

The steward's role changes too. Instead of becoming the person through whom every correction must pass, stewardship increasingly becomes exception handling, approval, policy definition and oversight.

Where Microsoft Fabric fits

Fabric does not turn into MDS because MDS disappeared. A solved Microsoft Fabric Community discussion from 2025 made the architectural point succinctly: Fabric does not contain a built-in replacement for legacy Master Data Services.

Community source: Microsoft Fabric Community

That is community guidance rather than Microsoft product documentation, but the distinction is technically useful. Fabric is extremely capable at data engineering, analytics and AI workloads. Master Data Management still has to deal with identity, mastering, relationships, survivorship, quality, stewardship and controlled distribution.

 

 

And where does Purview fit?

Purview is equally important, but for a different reason. It is not simply "new MDS". Microsoft's current Learn architecture documents Purview and CluedIn working together across governance, lineage and operational MDM.

A practical migration sequence

A complicated MDS estate becomes much less frightening when the unit of migration is a consumer contract rather than the entire platform.

The 90-day version

CluedIn's adoption playbook proposes a useful shape for proving the migration early.

So, is CluedIn actually recognised outside CluedIn for this?

Yes. The important thing is to describe the evidence accurately.

What this evidence does not mean

It does not mean Microsoft has designated one universal successor to Master Data Services. It has not. It does not mean every MDS deployment requires an enterprise MDM platform. Some do not. And it does not mean a historical Azure reference architecture should be treated as the current implementation guide for CluedIn in 2026.

The migration is finished when MDS is no longer a dependency

Not when all the records have been copied. MDS has not really been retired if:

• A nightly job still reads one subscription view
• Finance still maintains a hierarchy through an old process
• An undocumented Excel workbook still depends on it
• Change notifications still originate there
• An application still expects an MDS-generated identifier
• Nobody knows whether an old business-rule job can safely be switched off