Skip to main content
purview glossary migrationpurview glossary termspurview classic glossarypurview enterprise glossarypurview data governance retirementbusiness glossaryPurview Unified Catalog

Purview Glossary Migration: How to Move Your Terms

Purview glossary migration is the move of your business glossary terms, with their definitions, owners, relationships, custom attributes and asset links, out of Microsoft Purview before Purview Data Governance retires on November 12, 2027. Microsoft points customers to Microsoft Fabric and the OneLake catalog, but its own guidance says Fabric has no full glossary parity, so where the terms go is a decision of its own.

The glossary is usually the most valuable thing a governance team built in Purview. Scanned metadata can be rescanned in any tool, while every term, definition and owner was agreed by people. This page shows how to tell which kind of Purview glossary you have, how to export it, what does not survive the move, and how the fields map to Fabric or to a business glossary in a data catalog.

TL;DR

Purview has two glossaries: the classic Data Map glossary with term templates, and Unified Catalog terms inside governance domains. Classic terms have a CSV export. Unified Catalog terms have no documented export button, only the Unified Catalog API in public preview. Workflows, approval history and links to assets do not travel as-is: links have to be restored once the new tool has scanned the sources. In Fabric, terms become tags, descriptions and endorsement. A data catalog keeps them as terms with owners, synonyms, hierarchy and custom attributes. When you move to Dawiso, the Dawiso customer success team runs the glossary migration with you.

What is Purview glossary migration?

A Purview glossary term is more than a name and a definition. Depending on the experience it was created in, it can carry owners and experts, acronyms and synonyms, a parent term, related terms, resources, custom attributes from a term template, a draft or published status, and links to data assets, columns, data products and critical data elements. Migration means moving all of that into a tool where it keeps its meaning, not just copying a list of words.

Microsoft's transition guidance of November 13, 2026 maps glossary terms, critical data elements and custom context to tags, descriptions and endorsement in Fabric. Its advice is to "export and preserve terms and ownership" and not to claim full glossary or critical data element parity. That is the starting point for every plan below.

Classic glossary or Unified Catalog terms?

The first step is to find out which glossary you have, because the export path depends on it. Tenants that used Purview before the Unified Catalog often have both.

Classic glossary (Data Map)Unified Catalog glossary terms
Where you edit termsThe classic data catalog in the Data MapA governance domain in the Unified Catalog; all terms are listed under Enterprise glossary
StructureTerm templates with custom attributes; parent and child terms, acronyms, synonyms and related termsTerms inside governance domains, with owners, experts, acronyms, resources and custom attributes; parent terms, synonyms and related terms
LifecycleOptional approval workflowsDraft and published states
LinksMapped to assets such as databases, tables and columnsLinked to data products, data assets, columns and critical data elements
Bulk exportCSV export of selected termsNo export documented in the portal; Unified Catalog API (preview)

If your team already ran Microsoft's classic-to-Unified Catalog migration, the classic terms are now read-only, the term templates became attributes in a staging domain that cannot be edited, and the Unified Catalog terms are the current version. Export those. If you have not run it, do not run it now just to tidy up: the Unified Catalog retires on the same date, and the migration cannot be reversed. More on that tool in Is there a Microsoft Purview migration tool?

Purview Glossary Migration - Export Paths and Targets PURVIEW GLOSSARY MIGRATION - EXPORT PATHS AND TARGETS CLASSIC GLOSSARY Term templates, hierarchy Synonyms, related terms Export: CSV UNIFIED CATALOG TERMS Governance domains, owners Links to products and CDEs Export: API, preview MAP THE FIELDS Owners to real users Templates to attributes Drop ownerless terms FABRIC ONELAKE CATALOG Tags and descriptions Endorsement on items No full glossary parity, per Microsoft DATA CATALOG GLOSSARY Terms with owners, synonyms Hierarchy, custom attributes Links restored after rescan Workflows, approval history and scanned metadata do not travel. Rebuild flows, rescan sources.
Click to enlarge

How to export Purview glossary terms

Export the classic glossary to CSV

In the classic glossary, select the terms and choose Export terms. Microsoft's import and export documentation notes that the selected terms do not need to share a term template, and that exporting requires data curator permissions. The columns depend on the templates, so a glossary with several templates produces a wide file. Keep the raw export untouched as an archive, and work on a copy.

Export Unified Catalog terms through the API

For Unified Catalog terms, Microsoft's glossary term documentation describes bulk import, bulk edit, publish and move, but no export. The way out is the Unified Catalog API, in public preview, whose Terms operations include List, Get, List Hierarchy and List Related Entities. A short script that lists every term per governance domain, then reads its hierarchy and related entities, produces a copy of everything the API exposes. Microsoft notes that the API covers only Unified Catalog features that are generally available, so compare the script's counts with the portal before you rely on it.

For a small glossary of a few dozen terms, copying from the portal into a spreadsheet can be faster than writing a script. Either way, export before the work gets urgent: maintenance mode means no fixes for gaps you discover late.

What does not migrate with the terms

  • Workflows and approval history. Microsoft does not migrate workflows even between its own two glossaries. Rebuild approvals in the target, and if a regulator expects proof of past approvals, keep the Purview record.
  • Links to assets and columns. A link points to an asset in the Purview Data Map. In the new tool, those assets exist only after the sources are scanned again, so links have to be restored by matching names after the rescan.
  • Owners who no longer exist. Owners and experts are stored as email addresses. People leave, so check every owner against your directory before import.
  • Relationships outside the CSV format. The Unified Catalog CSV format has no parent, synonym or related term columns, so relationships have to come from the API or the classic export and be loaded into the target separately.
  • Term templates as structure. The custom attributes travel as values. The target needs matching attributes defined before import, or the values have nowhere to go.

Migration is also the cheapest moment to clean up. Terms with no owner, no description and no links are usually better dropped than carried into a new tool.

Purview glossary field mapping: Fabric vs a data catalog

How each part of a Purview term lands in the two most common targets, based on Microsoft's transition guidance for Fabric and on Dawiso's documented business glossary:

Purview term fieldFabric OneLake catalogDawiso business glossary
Term name and definitionA tag name, or text in an item descriptionBusiness term with its description
Governance domainFabric domain, which scopes workspaces and itemsBusiness domain
Owners and expertsItem owners; no owner on the term itselfOwner and steward roles on the term
Acronyms and synonymsNo equivalentAcronym and synonym objects linked to the term
Parent and child termsNo equivalentHierarchy, configured per object type by an administrator
Related termsNo equivalentRelated relations, plus automatic mentions from text
Custom attributes and term templatesNo equivalentCustom attributes defined by an administrator
Draft and published statusEndorsement (promoted, certified) on itemsWorkflow states such as draft, review and approved
Links to assets and columnsTags applied to Fabric itemsRelations to scanned objects across Fabric and other sources
Critical data elementsNo equivalentModeled as a custom object type

Fabric is a reasonable home for terms that only label Fabric items. For a glossary that people read, approve and maintain, with owners and synonyms, and that also describes data in Databricks, Snowflake or SAP, the OneLake catalog is not built for that today. See Purview to Fabric for the full mapping of the other objects.

See it in action

Dawiso as a Microsoft Purview alternative

A business glossary with owners, synonyms and approval workflows, and a team that migrates your Purview terms for you.

Moving a Purview glossary to Dawiso

You do not have to migrate the glossary yourself. The Dawiso customer success team runs the migration with you and carries over business terms, descriptions and data products, including custom attributes and other custom structures.

There is no one-click Purview importer behind it, but a planned migration that the team runs with you. Under the hood, the documented steps are:

  1. Prepare the metamodel. An administrator adds custom attributes, and if needed a custom object type, for example for critical data elements, so every Purview field has a place.
  2. Sync owners. With Microsoft Entra ID synchronization, users are available in Dawiso before their first sign-in, so the import can assign them as owners straight away.
  3. Import terms. The Excel import creates or updates objects, with a recommended maximum of 1,000 per run, with attributes and owner roles, and shows the counts of added and changed objects before you confirm.
  4. Import relations. A separate Relations sheet links existing objects, for example synonyms and acronyms to their terms.
  5. Scan and link. Connect Microsoft Fabric, Power BI and the other sources, then link terms to the scanned tables, columns and reports.

The result is a glossary that keeps its owners, synonyms and approval workflow, and that describes data in Fabric and next to it. Read the full context in Microsoft Purview Data Governance is retiring, or book a demo with your own Purview glossary.

Sources

See it in action

Move your Purview glossary to Dawiso

Our customer success team carries over your terms, descriptions, owners and custom attributes.

A cookie a day keeps bad UX away.

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services. By clicking "Accept All", you allow us to use cookies for analytics and ads via Google Tag Manager. You can also customize cookies.

Customize Consent Preferences

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners. Privacy Policy

Necessary cookies allow core website functionality such as user login and account management. The website cannot be used properly without strictly necessary cookies.

Functionality cookies are used to remember visitor information on the website, eg. language, timezone, enhanced content.

Analytics cookies are used to see how visitors use the website, eg. analytics cookies. Those cookies cannot be used to directly identify a certain visitor.

We use Microsoft Clarity to see how you use our website (including heatmaps and session replays) so we can improve it. By using our site, you agree that we and Microsoft can collect and use this data. See our Privacy Policy for details.

Advertisement cookies are used to identify visitors between different websites, eg. content partners, banner networks. Those cookies may be used by companies to build a profile of visitor interests or show relevant ads on other websites.