Is There a Microsoft Purview Migration Tool?
No. As of November 18, 2026, Microsoft offers no tool that moves your content out of Purview Data Governance, which retires on November 12, 2027. The Purview features that carry "migration" in their name move data into Purview, between two Purview experiences, or into Microsoft Entra ID. Leaving Purview Data Governance, whether for the Microsoft Fabric OneLake catalog or for another data catalog, is a project of exporting, mapping and importing.
This page sorts out the three tools people find when they search for a Purview migration tool, lists which Purview objects can be exported and how, and gives a step-by-step plan for the move without a dedicated tool. For the retirement itself, start with Microsoft Purview Data Governance is retiring.
Microsoft announced the retirement of Purview Data Governance on November 12, 2026, with end of support on November 12, 2027, and published no migration tool for leaving it. The DLP migration assistant moves Symantec and Forcepoint policies into Purview, the classic glossary migration moves terms into the Unified Catalog, which is retiring too, and the Role Assignment Migrator syncs security and compliance roles to Entra ID. To leave, export hand-built content (classic glossary CSV export, Unified Catalog API in public preview), rescan sources in the new tool, and rebuild what has no export, such as data quality rules and workflows.
Is there a Purview migration tool for leaving Purview Data Governance?
No. Microsoft's transition guidance of November 13, 2026 maps Purview Data Governance outcomes to the Fabric OneLake catalog and recommends moving in waves, but it names no migration tool. For the glossary, its advice is to "export and preserve terms and ownership", and it warns not to claim full glossary or critical data element parity in Fabric.
That matches Microsoft's history. When the earlier Azure Data Catalog was replaced by Purview, Microsoft's migration guide said there was no in-place upgrade experience. Customers had to plan and run the migration themselves. Planning for the same now is the realistic baseline.
Which Purview migration tools exist?
Three Purview features come up for "Purview migration tool" or "Purview migration assistant". None of them moves content out of Purview Data Governance:
| Tool | What it migrates | Direction | Helps you leave? |
|---|---|---|---|
| DLP migration assistant | Data loss prevention policies from Symantec and Forcepoint | Into Purview DLP | No. It belongs to data security, which is not retiring. |
| Classic glossary migration (preview) | Classic glossary terms, term templates and asset and column links | Classic Data Map glossary into the Unified Catalog | No. The Unified Catalog retires on the same date. |
| Purview Role Assignment Migrator | Assignments of security and compliance roles, such as Compliance Search, Export and Hold | Purview roles to Microsoft Entra ID roles | No. It covers no Unified Catalog or Data Map roles. |
DLP migration assistant
The DLP migration assistant is a Windows desktop application that converts data loss prevention policies from Symantec and Forcepoint into Microsoft Purview DLP policies. It serves the security side of Purview, which Microsoft keeps. If your search landed on it, it has nothing to do with the data governance retirement.
Classic glossary migration to the Unified Catalog
Purview has a built-in flow that migrates classic glossary terms into the Unified Catalog, started from Catalog management with the "Enable asset curation" option. It carries terms, term templates and links to assets and columns, lands the terms as drafts in a staging domain, and can take up to 48 hours. Microsoft notes that the action is one-time and cannot be reversed, that workflows are not migrated, and that classic terms become read-only afterwards.
Two facts matter now. The Learn page still marks the feature as preview, and Microsoft's message center post MC1280564 was updated on August 7, 2026 to say that Microsoft decided not to move forward with the rollout. And the target, the Unified Catalog, is retiring on November 12, 2027 with the rest of Purview Data Governance. Running this migration now moves your glossary one step sideways, not out. Details are in Purview glossary migration.
Purview Role Assignment Migrator
The Role Assignment Migrator is a Microsoft enterprise application in Entra ID. It syncs assignments of Purview security and compliance roles, for example Insider Risk Management, Compliance Search, Export, Hold and Privacy Management, to three Entra roles: Purview Workload Content Reader, Writer and Administrator. Microsoft 365 services use those roles to check permissions before long-running Purview operations such as content search and export. It does not touch data governance roles. What happens to those is covered in Purview role migration.
What can you export from Purview Data Governance?
The content people built by hand can be exported, in parts and through different paths. Scanned metadata is better rescanned, and some objects have no documented export at all. The state as of November 18, 2026:
| Purview object | Documented export path | What to plan for |
|---|---|---|
| Classic glossary terms | CSV export from the classic glossary; selected terms can span several term templates | Needs data curator permissions. Columns follow the term templates. |
| Unified Catalog glossary terms | Unified Catalog API (public preview): List, Get, List Hierarchy and List Related Entities for terms | No export button is documented in the portal, so plan a script. The bulk CSV import only creates terms. |
| Governance domains | Unified Catalog API: Enumerate and Get for business domains | Small number of objects, often faster to recreate by hand. |
| Data products | Unified Catalog API: List, Get and List Relationships | Owners, access policies and the product contract need checking in the target. |
| Critical data elements and OKRs | Unified Catalog API: List and Get | Few targets have a native object for them. Decide how to model them first. |
| Data quality rules, scores and health history | No documented export | Document the rules and rebuild them in the target or a data quality tool. |
| Workflows and approvals | No documented export | Rebuild approval and access flows. Keep evidence of past approvals if a regulator expects it. |
| Scanned technical metadata and lineage | Not worth exporting | Rescan sources with the new tool's connectors, so metadata starts current. |
| Sensitivity labels, DLP, audit | Nothing to export | These stay in Microsoft Purview, which keeps its data security and compliance products. |
Microsoft states that the Unified Catalog API covers only Unified Catalog features that are generally available, and its current version is 2026-03-20-preview. Test a full export early, on a copy of the output, and count what comes back against what the portal shows. Anything the API misses has to be copied by hand while the portal still works.
See it in action
Dawiso as a Microsoft Purview alternative
A data catalog across Microsoft Fabric and the platforms next to it, bought through Microsoft Marketplace and priced per user.
How to migrate from Purview Data Governance without a migration tool
Treat the move as a project with a fixed end date, and separate what people built from what scanners found. A plan that works for most teams, in line with Microsoft's own advice to move in waves:
- Inventory. List glossary terms, governance domains, data products, critical data elements, custom attributes, owners, data quality rules, workflows, access policies, registered sources and any integration that calls the Purview API. Microsoft's transition guidance gives the same list.
- Classify each item. Move it, rebuild it, keep it in Purview (labels and DLP), or drop it. Old, ownerless terms are cheaper to drop than to migrate.
- Choose the target. The OneLake catalog covers Fabric items, see Purview to Fabric. A data catalog covers Fabric together with Databricks, Snowflake, SAP and on-premises sources. Start procurement early.
- Export hand-built content. Use the classic CSV export and the Unified Catalog API, store the raw output, and freeze changes in Purview for the domain you are moving.
- Map and import. Map Purview fields to the target's fields, import terms with owners, then data products. Map roles to the target's permission model.
- Rescan and relink. Connect the sources in the new tool, then restore the links between terms and assets that the export carried.
- Reconcile and cut over. Compare counts of terms, owners and data products, run both tools in parallel for one domain, then switch off Purview Data Governance before November 12, 2027.
Start with one business domain end to end. A pilot exposes the fields the export misses and the owners who have left the company, while there is still time to fix both.
How the migration from Purview to Dawiso works
Dawiso has no one-click Purview importer, and we do not claim one. A member of the Dawiso customer success team runs the migration with you. Business terms, descriptions and data products, including custom attributes and other custom structures, are carried over from Purview. Connected sources such as Microsoft Fabric, Power BI and Databricks are scanned fresh, so technical metadata and lineage start current.
Underneath, Dawiso's documented Excel import loads objects in insert or update mode, with a recommended maximum of 1,000 objects per run, with attributes, owner roles and a separate sheet for relations such as synonyms and acronyms. Users synced from Microsoft Entra ID can be assigned as owners before they first sign in. The business glossary then has domains, terms, indicators and rules with approval workflows. Dawiso is available on Microsoft Marketplace, so it is billed through your Microsoft account as Purview was. See the Microsoft Purview alternative page or book a demo built around your Purview setup.
Sources
- Microsoft Analytics on Azure Blog - From Purview Data Governance to the Fabric OneLake Catalog (November 13, 2026)
- Microsoft Learn - Migrate classic glossary terms and enable asset curation in Unified Catalog (preview)
- Microsoft 365 message center via merill.net - MC1280564, Migration tool in Unified Catalog to migrate classic glossary terms (updated August 7, 2026)
- Microsoft Learn - Purview Role Assignment Migrator
- Microsoft Learn - Use the Microsoft Purview Data Loss Prevention migration assistant
- Microsoft Learn - Unified Catalog API (public preview)
- Microsoft Learn - Import and export glossary terms (classic)
- Microsoft Learn - Migrate from Azure Data Catalog to Microsoft Purview
- Dawiso Help - Object import from Excel and Microsoft Entra ID synchronization
See it in action
Moving off Purview Data Governance?
The Dawiso customer success team migrates your Purview terms, data products and custom attributes for you.