Live webinar · Thu 19 Nov, 11:00 CETWatch a semantic layer build itself. Save your seat →
Guides · Fabric & PurviewdScribe

Moving from Microsoft Purview to dScribe: a step-by-step migration plan

Microsoft is retiring Purview Unified Catalog and its classic data-governance capabilities. Moving your catalog to dScribe does not mean starting from scratch: the migration plan covers your assets, glossary, classifications, owners and lineage.

Why now

Microsoft’s retirement announcement covers Unified Catalog and classic data governance, not the entire Purview product family.

Many teams spent years building their Purview catalog. They registered sources, wrote definitions and assigned owners. That work is valuable, and it should not be lost when you move to a new catalog.

This post sets out a six-step migration plan using our ready-made Purview connector and migration scripts to automate most of the heavy lifting.

What moves over

The table below shows how the main parts of your Purview catalog map to dScribe.

Purview to dScribe metadata mapping
In PurviewIn dScribeHow it moves
Data assets (tables, files, reports)Assets, with an asset type per kindPurview connector reads them from the Data Map API
Columns and schemasFields (data structure elements) on each assetImported together with their parent asset
CollectionsDomainsMapped to your domain list during setup
Glossary terms and categoriesGlossary terms, linked to assets and columnsMigration script copies terms, definitions and links
Classifications and sensitivity labelsProperties such as PII and custom tagsMapped to dScribe properties
Owners and expertsAsset owner and stewardMatched to users from your Entra ID single sign-on
LineageLineage relations between assetsMigration script copies lineage, OpenLineage keeps it current
Business domains and data products (Unified Catalog)Domains and data product assetsMigration script copies them with their linked assets

dScribe also offers data contracts with quality rules, AI suggestions for descriptions, and an MCP server that lets connected AI agents query your catalog.

The migration plan in six steps

Step 1: Take stock of your Purview catalog

Start by taking an inventory of what you have. Our assessment script connects to your Purview account and counts your assets, glossary terms, classifications, owners and lineage links.

You get a short report. It shows what is ready to move and what needs cleaning up first, such as terms without definitions or assets without owners.

What you need for this step:

  • A service principal in Microsoft Entra ID
  • The Data Reader role on the Purview collections you want to migrate
  • About 30 minutes for the initial assessment

Step 2: Set up dScribe to match your organisation

Next, we prepare dScribe so your metadata has a place to land. We create the asset types you need, such as tables, reports and data products. We also set up your domains, often one per Purview collection.

You connect dScribe to Entra ID for single sign-on. With single sign-on configured, users and teams can be matched to owners and stewards during the migration.

Step 3: Export from Purview with the dScribe connector

The dScribe Purview connector reads your catalog through the official Purview APIs. It pulls in:

  • Assets and their columns, through the Data Map entity and search APIs
  • Glossary terms, categories and the assets they are linked to, through the glossary API
  • Lineage between assets, through the lineage API
  • Classifications, labels and custom attributes on each asset
  • Business domains and data products from the Unified Catalog

The connector is read-only: it does not change anything in Purview, so you can rerun the export when needed.

Step 4: Map and import into dScribe

The migration script translates Purview concepts into dScribe concepts, using the mapping in the table above. You can review the mapping before anything is written. For example, you choose which classifications become PII flags and which become tags.

The script then loads the mapped metadata into dScribe. Glossary terms are linked to the same columns and assets as before. Owners are matched to real users by email.

Step 5: Reconnect your data sources

Your catalog needs to stay up to date after the move. We therefore connect dScribe directly to your sources instead of relying on Purview scans.

dScribe has native connectors for your data stack, including SQL Server, Power BI, SharePoint and Databricks Unity Catalog. It also connects to Snowflake, BigQuery, SAP, Tableau and more. For lineage from Azure Data Factory, Fabric or Databricks pipelines, you can send OpenLineage events straight to dScribe.

For sources inside your own network, our Data Bridge agent connects to them securely without opening your firewall.

Step 6: Validate and switch over

Before you switch off Purview, check that everything arrived. The migration script produces a comparison report: counts per asset type, glossary links and lineage edges, side by side.

Ask your data stewards to review their own domains. They can mark assets as Validated in dScribe once they are happy. Once the comparison checks pass and your stewards sign off, direct your users to dScribe and retire your Purview catalog.

How long it takes, and tips for a smooth move

Plan for approximately one to two weeks from start to finish. Treat the timings below as a planning estimate: the schedule depends on the size of your catalog and how many sources you reconnect.

Estimated migration timeline
PhaseStepsPlanning estimate
Assess and prepare1 and 21 to 2 days
Export and import3 and 42 to 3 days
Reconnect, validate and switch over5 and 63 to 5 days
Total1 to 2 weeks

A few tips for a smooth migration:

  • Run a pilot first. Move one collection or domain end to end before you move the rest.
  • Clean up on the way. The move is a good moment to drop stale assets and merge duplicate glossary terms.
  • Run both catalogs side by side for a short time. Keep Purview read-only until your stewards sign off.
  • Tell your users early. Share the date of the switch and show them where to find things in dScribe.

Ready to plan your move?

If you use Purview today and want to move to dScribe, contact our team. We will assess your catalog, share a migration plan and timeline, and show you a demo with your own metadata.

We can help you plan the switch before the Purview data-governance capabilities you use are retired.

Want to see this on your own reports?

Talk it through with the team over a coffee.

Let's grab a coffee ☕