---
title: "Purview Glossary Migration: How to Move Your Terms | Dawiso"
description: "Purview glossary migration step by step: classic vs Unified Catalog terms, how to export them, what gets lost and how fields map to Fabric or a data catalog."
url: "https://www.dawiso.com/glossary/purview-glossary-migration"
language: "en"
---

November 18, 2026

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](https://www.dawiso.com/glossary/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](https://www.dawiso.com/glossary/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](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) 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 terms | The classic data catalog in the Data Map | A governance domain in the Unified Catalog; all terms are listed under Enterprise glossary |
| Structure | Term templates with custom attributes; parent and child terms, acronyms, synonyms and related terms | Terms inside governance domains, with owners, experts, acronyms, resources and custom attributes; parent terms, synonyms and related terms |
| Lifecycle | Optional approval workflows | Draft and published states |
| Links | Mapped to assets such as databases, tables and columns | Linked to data products, data assets, columns and critical data elements |
| Bulk export | CSV export of selected terms | No export documented in the portal; Unified Catalog API (preview) |

If your team already ran Microsoft's [classic-to-Unified Catalog migration](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-migrate), 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?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool)

## 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](https://learn.microsoft.com/en-us/purview/how-to-import-export-glossary) 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](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-create-manage) describes bulk import, bulk edit, publish and move, but no export. The way out is the [Unified Catalog API](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview), 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](https://www.dawiso.com/product/business-glossary):

| Purview term field | Fabric OneLake catalog | Dawiso business glossary |
| --- | --- | --- |
| Term name and definition | A tag name, or text in an item description | Business term with its description |
| Governance domain | Fabric domain, which scopes workspaces and items | Business domain |
| Owners and experts | Item owners; no owner on the term itself | Owner and steward roles on the term |
| Acronyms and synonyms | No equivalent | Acronym and synonym objects linked to the term |
| Parent and child terms | No equivalent | Hierarchy, configured per object type by an administrator |
| Related terms | No equivalent | Related relations, plus automatic mentions from text |
| Custom attributes and term templates | No equivalent | Custom attributes defined by an administrator |
| Draft and published status | Endorsement (promoted, certified) on items | Workflow states such as draft, review and approved |
| Links to assets and columns | Tags applied to Fabric items | Relations to scanned objects across Fabric and other sources |
| Critical data elements | No equivalent | Modeled 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](https://www.dawiso.com/glossary/purview-to-fabric) for the full mapping of the other objects.

[See it in action](https://www.dawiso.com/microsoft-purview-alternative)

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](https://www.dawiso.com/connectors/microsoft-fabric), [Power BI](https://www.dawiso.com/connectors/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](https://www.dawiso.com/blog-post/microsoft-purview-data-governance-retirement), or [book a demo](https://www.dawiso.com/book-a-dawiso-demo) with your own Purview glossary.

## Sources

- Microsoft Analytics on Azure Blog - [From Purview Data Governance to the Fabric OneLake Catalog](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) (November 13, 2026)
- Microsoft Learn - [Business glossary in the classic data catalog](https://learn.microsoft.com/en-us/purview/legacy/concept-business-glossary)
- Microsoft Learn - [Import and export glossary terms (classic)](https://learn.microsoft.com/en-us/purview/how-to-import-export-glossary)
- Microsoft Learn - [Create and manage glossary terms in Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-create-manage)
- Microsoft Learn - [Migrate classic glossary terms and enable asset curation in Unified Catalog (preview)](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-migrate)
- Microsoft Learn - [Unified Catalog API (public preview)](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview)
- Dawiso Help - [Business Glossary](https://help.dawiso.com/actual/business-glossary/), [Object import from Excel](https://help.dawiso.com/actual/object-import-excel/), [New attribute](https://help.dawiso.com/actual/new-attribute/), [New object type](https://help.dawiso.com/actual/new-object-type/) and [Microsoft Entra ID synchronization](https://help.dawiso.com/actual/microsoft-entra-id-synchronization/)

[See it in action](https://www.dawiso.com/microsoft-purview-alternative)

Move your Purview glossary to Dawiso

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

### Table of contents

What is Purview glossary migration?Classic glossary or Unified Catalog terms?How to export Purview glossary termsWhat does not migrate with the termsPurview glossary field mappingMoving a Purview glossary to DawisoSources

## Related Terms

### [What Is the Microsoft Purview Unified Catalog?](https://www.dawiso.com/glossary/microsoft-purview-unified-catalog)

The Microsoft Purview Unified Catalog explained: domains, data products, CDEs, how it differs from the Data Map, and what its retirement means for you.

Read more →

### [Is There a Microsoft Purview Migration Tool?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool)

There is no Microsoft Purview migration tool for leaving Purview Data Governance. See what the three Purview migration tools do and how to export your content.

Read more →

### [Microsoft Fabric vs Purview: What Each One Does](https://www.dawiso.com/glossary/microsoft-fabric-vs-purview)

Microsoft Fabric vs Purview explained: an analytics platform and a security and compliance suite, and what changes as Purview Data Governance retires.

Read more →

### [Purview Role Migration After the Retirement](https://www.dawiso.com/glossary/purview-role-migration)

Purview role migration explained: what the Role Assignment Migrator does, and how Unified Catalog and Data Map roles map to Fabric or a data catalog.

Read more →

### [Fabric IQ vs Purview: Ontology or Business Glossary?](https://www.dawiso.com/glossary/fabric-iq-vs-purview)

Fabric IQ vs Purview glossary: what a Fabric IQ ontology is, whether it replaces your Purview business glossary terms, and how the two work together.

Read more →

### [Microsoft Purview Pricing for Data Governance Explained](https://www.dawiso.com/glossary/microsoft-purview-pricing)

Microsoft Purview pricing: governance is billed per asset until it retires in 2027, security per user via Microsoft 365. Rates, examples and E5 answers.

Read more →
