---
title: "How to Move Purview Domains, Data Products, Glossary Terms"
url: "https://atlan.com/know/ai-agent/microsoft/move-purview-domains-data-products-glossary/"
description: "Map each Purview Unified Catalog object, export it before support ends on November 12, 2027, and validate the move before you switch off Purview."
author: "Emily Winks"
author_role: "Data Governance Expert"
published: "2026-11-18"
updated: "2026-11-19"
---

## How do you move Purview governance domains, data products, and glossary terms?

Map each object before you export it. Governance domains, data products, glossary terms, critical data elements, custom attributes, classifications, and owners each leave Purview by a different route. Export classic glossary terms to CSV, read Unified Catalog objects through its REST API, and pull lineage from the Data Map lineage API, all before support ends on November 12, 2027, then compare what landed with your plan before you switch Purview off. In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner.

The five steps:

- **Map**: decide where each governance domain lands in the new catalog
- **Export terms**: save glossary terms and their owners before shutdown
- **Export the rest**: capture lineage, classifications, and attributes
- **Move**: load the approved plan into the new catalog
- **Validate**: compare what landed with what you planned

## Key takeaways

- Support for Purview Data Governance ends November 12, 2027, so export and map your governance work before then.
- Microsoft's November 17, 2026 post announces a strategic partnership with Atlan, its preferred data governance partner.
- Learn documents a CSV export for classic terms, a Unified Catalog API, and Data Map lineage calls.
- Compare counts, owners, and links against your plan, and keep both systems running until they match.

---

Here is how to move Purview governance domains, data products, and glossary terms to a new catalog before support ends on November 12, 2027. In its [November 17, 2026 post](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035), Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner. For the end-to-end plan, start with the [Purview Data Governance retirement guide](https://atlan.com/know/purview-data-governance-retirement/) and the [five-step migration plan](https://atlan.com/know/ai-agent/microsoft/how-to-migrate-from-purview-data-governance/).

### Check Your Own Migration's Continuity Gaps

Give it the two platforms, the migration tool's documented scope, and where business definitions live. It returns the gaps ranked by what breaks first. [Read the skill](/skills/platform-migration-continuity-check.md).

*Paste into a new chat*

```
Use the skill at https://atlan.com/skills/platform-migration-continuity-check.md to check continuity gaps in our platform migration. Ask me for whatever it needs.
```

*Run once in a terminal*

```
curl -fsSL --create-dirs \
  -o ~/.agents/skills/platform-migration-continuity-check/SKILL.md \
  https://atlan.com/skills/platform-migration-continuity-check.md
```

*For an agent*

```
curl -fsSL https://atlan.com/skills/platform-migration-continuity-check.md
```


    Human
    Agent


  ClaudeChatGPTGeminiCursorOther
  Copy

If you are a data governance lead or data engineer on Purview, the glossary your stewards argued over and the data products other teams trust are on a clock, and rebuilding them later costs your stewards the rework and your AI agents the definitions they rely on. [Microsoft's November 12, 2026 announcement](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227) says support for Purview Data Governance ends on November 12, 2027. Microsoft Learn adds that existing capabilities stay in maintenance mode until that date and that you can no longer create new accounts. You have time, but every object leaves Purview by a different route. The glossary exports as a file, domains and data products come out through an API, lineage comes out one asset at a time, and custom attributes are recorded by hand. Plan the routes together and you finish with one inventory.

---

## Which Purview objects do you need to move, and how does each one leave?

Seven kinds of object carry your team's work. The table pairs what Microsoft Learn says each is with how it leaves Purview and what to check in any destination catalog.

| Object | What Learn says it is | How it leaves Purview | What to check in the destination |
|---|---|---|---|
| Governance domains | A boundary for governance, ownership, and discovery of data products and business concepts, with a name, description, and owners | Unified Catalog REST API, business domains | A domain or glossary that keeps the same owners |
| Data products | A group of data assets, such as tables, files, and Power BI reports, with a defined use case | Unified Catalog REST API, data products | The assets in each product are all present |
| Glossary terms | Business terms that give context to assets and can carry policies | CSV export for classic terms; Unified Catalog REST API for terms | Terms keep their parents, owners, and linked assets |
| Critical data elements | A logical grouping of important columns, such as a "Customer ID" that maps two column names | Unified Catalog REST API, critical data elements | Both column mappings survive |
| Custom attributes | User-defined custom metadata, in groups, applied to business concepts (preview) | Record groups and values from the Custom metadata page | Field types and values are supported |
| Classifications | Type definitions in the Data Map | Data Map type REST API, classification definitions | Equivalent tags or labels exist |
| Owners | Owner and expert contacts on terms, data products, and critical data elements | Included in the API responses and the term CSV | Emails resolve to real users |

### What to check before you trust each route

Learn labels custom attributes and critical data elements as preview features, and the [Unified Catalog API overview](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview) says features released as preview are not covered, so test what each call returns before you rely on it.

---

## Where do the OneLake catalog and Atlan fit once the export is done?

The OneLake catalog is where Microsoft is putting its data governance. In its November 17, 2026 post, Microsoft says it governs data that lives in or is connected to OneLake through native items, federated catalogs, IQ Shares, Shortcuts, and Mirrored databases.

Microsoft also calls it "a new model, not a feature-for-feature replacement for Purview Data Governance," so plan to move your work, not to find the same objects waiting on the other side. The [OneLake catalog guide](https://atlan.com/know/microsoft-fabric/onelake-catalog/) covers what it governs inside Fabric.

![OneLake native governance beside a third-party catalog, Atlan](/img/microsoft-onelake-atlan-governance-diagram.webp "OneLake and Atlan governance diagram"){width=688 height=395}

 OneLake catalog governance, extended by a third-party catalog like Atlan. Source: Microsoft 

Microsoft says OneLake and Fabric customers can use Atlan to extend governance beyond OneLake. It describes the partner as providing granular, cross-estate lineage and richer governance constructs, such as usage and popularity stats, across heterogeneous, non-Microsoft data sources. For these objects, that gives domains, data products, and glossary terms a landing spot that reaches past Fabric. Some objects may belong in the OneLake catalog and others in a wider catalog, so decide object by object. Weigh the split with [Microsoft Fabric governance](https://atlan.com/know/ai-agent/microsoft/microsoft-fabric-governance/), [how teams coexist, extend, or replace Purview](https://atlan.com/know/ai-agent/microsoft/coexist-extend-replace-purview/), and [Fabric governance evaluation questions](https://atlan.com/know/ai-agent/microsoft/fabric-governance-evaluation-questions/), and see [the partners Microsoft names](https://atlan.com/know/ai-agent/microsoft/microsoft-data-governance-partners-after-purview-retirement/) for the wider field. The [Microsoft partner page](https://atlan.com/partners/microsoft/data-governance-onelake-catalog/) covers how the two work together, and [what Microsoft Purview is](https://atlan.com/know/ai-agent/microsoft/what-is-microsoft-purview/) explains the product split.

---

## Step 1: Map your governance domains to the new catalog

Mapping comes first because it decides what you export and who approves it.

Microsoft Learn describes a governance domain as a boundary that holds data products, glossary terms, objectives and key results, and critical data elements, with named owners. Every one of those children has to land somewhere, and the domain's owners are the people who can approve where.

**How to do it:**

1. List every governance domain with its owners, its data products, its terms, and its critical data elements. Learn names five domain types: functional unit, line of business, data domain, regulatory, and project.
2. For each domain, choose a landing spot: a domain, a glossary, or both. If ownership follows business areas, a domain fits. If the domain mostly bounds a vocabulary, a glossary fits. The [data domain guide](https://atlan.com/know/data-governance/data-domain-data-governance/) helps you choose.
3. Decide what stays behind, such as draft domains and expired items. Learn says critical data elements move through Draft, Published, and Expired, so state which statuses come across.
4. Name one approver per domain, so nobody argues about a landing spot after the move.
5. Count the children of each domain, so you know where your stewards' review time goes.

The [Purview Unified Catalog guide](https://atlan.com/know/ai-agent/microsoft/purview-unified-catalog/) shows what each object held, and the [classic and Unified Catalog comparison](https://atlan.com/know/ai-agent/microsoft/purview-classic-data-catalog-vs-unified-catalog/) explains why some terms live in two places.

**Done when:** every domain has a landing spot, a list of children, and a named approver.

---

## Step 2: Export glossary terms and their owners

Export the glossary before anything else, because it is the object your stewards care about most. Microsoft Learn documents the route for classic glossaries.

**How to do it:**

1. Open the glossary in the Purview portal and select the terms you want. The Export terms button stays disabled until you select at least one.
2. Select Export terms to download a CSV file. Terms do not need to share a term template.
3. Check the owners. Learn says the email for an expert or steward should be the primary address of the user from the Microsoft Entra group, and alternate emails and user principal names are not supported.
4. For Unified Catalog, list your terms through the Unified Catalog REST API. Learn's disaster recovery article shows terms with acronyms, an owner and expert contact list, and resource links.
5. Keep the files with the plan, and note the export date. Export first if you plan to use Microsoft's [one-time migration of classic terms into Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-migrate). Learn says it cannot be reversed, and classic terms become read-only afterward.

Learn also warns that the classic import process does not update the parent of a term, so keep the hierarchy in your inventory instead of relying on a round trip. Check each term against the [glossary required fields](https://atlan.com/know/faq/business-glossary-required-fields/) of the target catalog, and a [glossary kept up to date](https://atlan.com/know/how-to-keep-a-business-glossary-up-to-date/) is easier to move than one nobody edits. Confirm each owner with the [owners and stewards guide](https://atlan.com/know/ai-agent/ai-ready-data/ai-ready-data-owners-and-stewards/), and keep [data products](https://atlan.com/know/ai-agent/data-for-ai/how-to-package-data-products-data-catalog/) whole.

**Done when:** you hold a dated export of every glossary and term, with owner emails you have checked.

---

## Step 3: Export lineage, classifications, and custom attributes

Flow maps, classifications, and attributes each need their own call. Microsoft documents a REST API for the first two and a settings page for the third.

Hand-drawn flows matter most, because crawled ones can be rebuilt.

**Lineage.** The Data Map lineage REST API has three operations. Get returns the flow for an entity by GUID. Get By Unique Attribute does the same by type name and attribute. Get Next Page returns the next page for an entity. Get takes a direction of INPUT, OUTPUT, or BOTH and an optional depth in hops, and returns the base entity, a map of entity headers, and relations that name the from and to entities. Each call covers one entity, so script it across the assets you care about.

**Classifications.** The Data Map type REST API has operations for classification definitions by GUID or name, and entity headers in the lineage response list the classifications attached to each asset.

**Custom attributes.** Learn describes business concept attributes as user-defined custom metadata, grouped, with a scope that selects domains, business concepts, and data product types. Record each group, each attribute and its field type, and the values on every object, from the Custom metadata page. Learn says attributes cannot be deleted, only expired, so record expired ones too.

Crawled flows do not need this work, because the new catalog can rebuild them by crawling the same sources, and hand-drawn flows can move only where both ends exist in the new catalog. The [migration best practices guide](https://atlan.com/know/data-catalog/migration-best-practices/) covers the order of work.

**Done when:** you hold saved responses for your priority assets, a list of classifications, and a record of every attribute group and value.

---

## Step 4: Load the approved plan into the new catalog

Loading is the step where every decision should stay reviewable. Files and API responses still need mapping to the target catalog's model, owners matched to real users, and terms relinked to assets.

A script and a spreadsheet can handle a small glossary. Domains with data products, attributes, and years of owner changes are harder to review by hand.

Whatever you load with, look for the same things in the destination catalog. It should show what would be dropped before it writes anything, let your governance lead choose where each item lands, load in batches, and leave Purview untouched. Owners should match by email, with experts and stewards recorded alongside them. Data quality rules usually need to be set up again. In its [November 17, 2026 post](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035), Microsoft says Atlan supports customers transitioning from Purview Data Governance to Fabric with tooling to carry their existing metadata forward. For the end-to-end sequence, follow the [migration plan](https://atlan.com/know/ai-agent/microsoft/how-to-migrate-from-purview-data-governance/), and keep the [retirement checklist](https://atlan.com/know/ai-agent/microsoft/purview-data-governance-retirement-checklist/) beside it for dates.

**Done when:** the approved plan is loaded, and each migrated object records its Purview ID, URI, and collection so you can trace it back.

---

## Step 5: Validate before you switch off Purview Data Governance

Validation turns an export into a migration. Run the old and new systems side by side until the numbers match, and do not switch Purview Data Governance off before then.

**How to do it:**

1. Compare counts. Domains, data products, glossaries, terms, and critical data elements in the new catalog should equal the plan.
2. Compare owners. Every owner on your list should resolve to a person in the new catalog, and the exceptions should have names beside them.
3. Compare links. Spot-check that terms sit on the assets they described and that data products hold the assets you listed.
4. Compare lineage for your priority assets against the responses you saved.
5. Rerun if something changed. Load only what is new, without duplicating what already landed, so you can take a fresh snapshot while both systems run.

Keep a validation report that compares planned and landed objects, with counts and coverage for glossaries, tags, and custom metadata.

Leave alone what stays in Purview. Microsoft says Purview Data Security and Compliance is not affected, and the [guide to what stays](https://atlan.com/know/ai-agent/microsoft/what-stays-in-microsoft-purview-after-retirement/) lists it. For the Data Map itself, see [Purview Data Map after retirement](https://atlan.com/know/ai-agent/microsoft/purview-data-map-after-retirement/). If you are weighing options, compare [Purview Data Governance alternatives](https://atlan.com/purview-alternatives/) and [data catalogs for Microsoft Fabric](https://atlan.com/best-data-catalogs-for-microsoft-fabric/), or read how [Atlan sits beside Purview](https://atlan.com/know/data-catalog/microsoft-purview-and-atlan/).

**Done when:** counts, owners, links, and lineage match your plan, and your governance lead signs off.

---

## What mistakes cost the most when you move Purview governance objects?

Four mistakes cost teams the most time, and each comes from order or ownership.

1. **Exporting terms without owners.** Learn says only the primary Microsoft Entra address works for an expert or steward, so unmatched emails surface late.
2. **Trusting the API to cover everything.** Learn says preview features are not covered, so test each call against your tenant.
3. **Migrating classic terms inside Purview first.** Learn says that migration cannot be reversed and leaves classic terms read-only, so export before you start it.
4. **Switching Purview off too early.** Run both systems until counts, owners, links, and lineage match the plan.

---

## FAQs about moving Purview governance objects

Teams ask the following questions most often when they plan the move.

### 1. How do you map Purview governance domains to a new catalog?

List each governance domain with its owners, data products, terms, and critical data elements, then choose a landing spot for it in the new catalog. A domain can become a domain, a glossary, or both, depending on how the new catalog groups ownership. Name one approver per domain before anything moves.

### 2. How do you export glossary terms from Purview before it shuts down?

Select the terms in the Purview portal and use Export terms to download a CSV file, per Microsoft Learn. That route is documented for classic glossaries. Unified Catalog terms are also listed in the Unified Catalog REST API. Check that expert and steward emails are primary Microsoft Entra addresses, then keep the files with your plan.

### 3. How do you export lineage from Purview?

The Data Map lineage REST API returns lineage for an entity you name by its GUID or its unique attributes, with a direction of input, output, or both, and an optional depth in hops. Run it for each asset you care about and store the responses. Lineage that connectors crawled can be rebuilt by crawling the same sources again.

### 4. Can you export Unified Catalog data products and critical data elements?

Yes. The Unified Catalog REST API lists business domains, data products, glossary terms, and critical data elements. It is in public preview, and Learn says features released as preview are not covered, so check what it returns for your tenant.

### 5. How do you move domains, data products, and glossary terms into a new catalog?

Move them in this order: domains first, then glossaries and terms, then data products, then critical data elements and custom attributes. Map owners to real users, relink terms to assets, and compare counts, owners, and links with your plan. Keep Purview running until they match.

### 6. Which data governance partner does Microsoft prefer?

In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner. Microsoft says OneLake and Fabric customers can use Atlan to extend governance beyond OneLake.

### 7. What stays in Microsoft Purview and does not need to move?

Microsoft says Purview Data Security and Compliance, including Information Protection, Data Loss Prevention, Insider Risk Management, and Data Security Posture Management, is not affected and continues to protect your data in Fabric. Your move covers Purview Data Governance only.

---

## Sources

1. [A next step in the evolution of the Microsoft Data Governance strategy, Microsoft Security Community Blog, November 12, 2026](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227)
2. [OneLake: the unified foundation for data, context, governance, and AI, Microsoft Fabric Community Blog, November 17, 2026](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035)
3. [Learn about Microsoft Purview Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog)
4. [Governance domains in Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-governance-domains)
5. [Data products in Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-data-products)
6. [Critical data elements in Unified Catalog (preview), Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-critical-data-elements)
7. [Business concept attributes (preview) in Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-attributes-business-concept)
8. [Import and export glossary terms (classic), Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/purview/legacy/how-to-import-export-glossary)
9. [Unified Catalog API (public preview), Microsoft Learn](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview)
10. [Disaster recovery for Microsoft Purview Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-disaster-recovery)
11. [Data Map lineage REST API, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/lineage)
12. [Data Map type REST API, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/type)
13. [Migrate classic glossary terms to Unified Catalog, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog-glossary-terms-migrate)
14. [Atlan and Microsoft: data governance and the OneLake catalog, atlan.com](https://atlan.com/partners/microsoft/data-governance-onelake-catalog/)

## Next steps

- To see Atlan's context layer in action first, watch a recorded demo: [Atlan context layer demos](https://atlan.com/context-layer-demo/)
- To see Atlan working on your own data stack, book a demo: [Book a demo with Atlan](https://atlan.com/forms/talk-to-sales-contact/)
