DataGalaxy is recognized in the Gartner® Value Management for Data, Analytics & AI Hype Cycle™ Report

Recognized in the Gartner® Value Management Hype Cycle™ Report

Get your copy

Microsoft Purview migration: how to export, map and validate your governance work

20 November 2026 │ 12 mins read │ Data Governance by Max Faivre, Product Marketing Manager
Microsoft Purview migration: how to export, map and validate your governance work
    Summarize with AI

    Latest update: November 20, 2026

    Microsoft Purview Data Governance reaches end of support on November 12, 2027. If you’re still deciding what to do, start with what the Purview retirement means and how to choose what comes next.

    This guide is for the next stage. You’re preparing a move and need to know how to transfer your glossary, owners, and lineage into a new catalog while preserving the work your teams have already done.

    Why a metadata re-scan isn’t enough

    Take a metric like Net Revenue. Your team spent a year documenting it in Purview. They defined the calculation, assigned a business owner, identified the tables behind it, and connected it to the reports that use it.

    Reconnect your data sources to a new catalog and you can recover their technical metadata. But what about the business definition, approval status, ownership assignments, and relationships documented in Purview?

    That information needs to be part of your migration plan, too.

    A successful migration preserves three things:

    • Technical metadata: What data exists, where it’s stored, and how it moves between systems.
    • Business context: What that data means, which definitions apply, and how business terms relate to technical assets.
    • Governance responsibilities: Who owns the data, who maintains its documentation, and how it gets reviewed.

    These elements may require different extraction and import methods.
    Start by identifying where each one lives.

    Step 1: Identify what to export from Microsoft Purview

    First, check whether your organization uses classic Microsoft Purview Data Governance, Unified Catalog, or both. Their governance models and extraction methods differ.

    Then build an inventory of the information you want to preserve.

    Purview componentWhat to preserveExtraction approach
    Business glossaryTerms, definitions, synonyms, hierarchies, custom attributesClassic CSV export or glossary APIs
    Governance domainsDomain structure, descriptions, responsibilitiesUnified Catalog API
    Data productsDescriptions, ownership, associated assetsUnified Catalog API
    Technical metadataDatabases, schemas, tables, columns, descriptionsRe-scan sources and extract Purview-specific metadata
    Asset relationshipsAssociations between technical and business objectsData Map relationship APIs and relevant catalog endpoints
    ClassificationsClassification definitions and assignmentsClassic Data Map APIs
    OwnershipAsset contacts, owners, experts, stewardship assignmentsAsset contacts and governance resource APIs
    WorkflowsApproval stages, reviewers, governance processesDocument existing configuration and retrieve supported workflow information

    Microsoft provides extraction and migration guidance for classic Purview and a separate Unified Catalog API.

    The Unified Catalog API is in public preview and provides access to resources including governance domains, glossary terms, data products, critical data elements, assets, and columns.

    Your inventory becomes the reference for the rest of the migration. It helps you identify which information to export and which technical metadata can be collected again directly from the source systems.

    Step 2: Export your Purview glossary and metadata

    Microsoft provides CSV exports and APIs for retrieving governance information. The method depends on the Purview experience you’re using and the objects you’re extracting.

    Export glossary terms from classic Purview

    For classic business glossaries, Microsoft supports exporting terms to CSV.

    1. Open the Microsoft Purview Data Catalog.
    2. Navigate to the relevant glossary.
    3. Select the terms you want to export.
    4. Click Export terms to download the CSV file.

    You’ll need Data Curator permissions. The exported fields depend on the glossary term templates used in your environment.

    See Microsoft’s glossary export documentation.

    Extract metadata through the Purview APIs

    For classic Purview, the Data Map APIs provide access to technical assets, relationships, classifications, glossary information, and asset contacts.

    For Unified Catalog, Microsoft provides a separate REST API. Its supported resources include business domains, data products, glossary terms, critical data elements, data assets, and columns.

    Microsoft also documents API-based backup and recovery procedures for Unified Catalog, including examples of governance resources and their associated contacts.

    Keep the original object identifiers throughout the extraction process. These identifiers help match glossary terms, technical assets, and their relationships when preparing the import into your new catalog.

    For larger environments, API-based extraction also provides a structured way to collect metadata and prepare it for transformation.

    Step 3: Preserve ownership and stewardship separately

    Copying your user directory doesn’t copy who is responsible for what.

    A dataset may have a technical administrator, a business owner, and a data steward. These are different responsibilities, and your migration should preserve the distinction.

    SSO handles authentication, while SCIM can support user and group provisioning in compatible systems. Ownership and stewardship assignments belong to the governance model and need to be mapped separately.

    Microsoft’s Purview APIs provide access to asset contacts and, for supported Unified Catalog resources, associated ownership information.

    For each critical business concept or asset, build a record like this:

    InformationExample
    Business termNet Revenue
    Business ownerFinance Director
    Data stewardFinance Data Steward
    Technical assetfinance.revenue.net_revenue
    Governance statusApproved
    Related usageRevenue Performance Dashboard

    Keep the identity references associated with each responsibility. You’ll use them to match the corresponding users and ownership fields in the destination catalog.

    Preserving an owner’s name in a description isn’t the same as assigning ownership to that person. The goal is to keep responsibilities visible and usable in the new governance environment.

    Step 4: Map Purview objects to your new catalog

    Every catalog has its own way of organizing business concepts, technical assets, attributes, and relationships.

    Before importing anything, define how the extracted information will be represented in the destination platform.

    Example: mapping Purview information to DataGalaxy

    DataGalaxy supports CSV imports for business glossary objects, technical Dictionary objects, and linked objects.

    For glossary imports, the CSV contains the object’s Path and Type, followed by the attributes you want to populate. The import interface lets you map fields and validate the file before importing.

    Here is how common Purview information can be organized in DataGalaxy:

    Purview informationDataGalaxy representation
    Glossary termBusiness Term or relevant glossary object
    DefinitionSummary or configured description attribute
    Business ownerDataOwners attribute
    Technical table or columnDictionary object
    Business term-to-asset associationImplementation link
    Related business termsGlossary relationship
    Custom attributesCorresponding configured attributes
    Governance statusConfigured status or lifecycle attribute

    Start with the glossary. Prepare your CSV using the object paths, types, and attributes defined in your DataGalaxy environment.

    This allows you to recreate two important types of connections:

    Glossary relationships connect business concepts to one another, such as related terms or synonyms.

    Implementations connect glossary objects to their technical representations in the Dictionary, including databases, tables, and fields. These implementation links can also be explored through DataGalaxy’s lineage views.

    For example, Net Revenue can be represented as a business term and linked to the technical column where it is implemented. Users can then navigate from the definition to the underlying technical asset.

    Test your mapping with a small group of objects first. Once the attributes and relationships are correctly represented, apply the same import structure to the rest of your catalog.

    Step 5: Rebuild technical lineage and preserve existing relationships

    Lineage deserves its own migration step because technical dependencies and business relationships aren’t collected in the same way.

    Start by separating them.

    Technical lineage describes dependencies between data sources, processing activities, tables, columns, and downstream usages. Your destination catalog can reconstruct supported dependencies by collecting metadata from the original systems.

    Manually maintained relationships describe connections added by governance teams. These can include associations between business concepts and technical assets, as well as documented dependencies. Extract the relevant information from Purview and recreate those relationships using the appropriate destination objects and import mechanisms.

    Microsoft’s classic Data Map APIs provide ways to retrieve relationships and lineage information. DataGalaxy, meanwhile, supports lineage and impact analysis across connected technologies, including table-level and column-level relationships where the source metadata provides that detail.

    For a critical metric such as Net Revenue, trace the journey from its underlying tables through processing activities to the reports that consume it.

    Check both the technical dependencies and the business relationships. The result should help users understand where the data comes from, how it is connected, and what could be affected by a change.

    Step 6: Test the migration on one critical metric

    Object counts don’t tell you enough.

    A catalog containing 10,000 assets isn’t particularly useful if people can’t find the right definition or tell who is responsible for it.

    Choose a critical business use case and test it end to end. Back to Net Revenue:

    1. Can a business user find the metric and understand its definition?
    2. Is the correct business owner assigned?
    3. Can users identify the technical assets implementing the metric?
    4. Can the team explore the relevant upstream and downstream dependencies?
    5. Can the responsible steward review and maintain its documentation?

    Compare the result with your original Purview environment and check that the relationships, attributes, and responsibilities have been preserved.

    Once the use case is validated, repeat the exercise with a representative selection of critical assets before extending the migration.

    This gives you a much more meaningful measure of success than simply checking whether an import completed.

    What can you automate in a Microsoft Purview migration?

    Several parts of the migration can be handled through documented exports, APIs, and import tools. Others involve adapting your governance model and reviewing the result.

    Migration activityAvailable approach
    Glossary extractionClassic CSV export and glossary APIs
    Asset metadata extractionPurview Data Map APIs
    Unified Catalog extractionREST API for supported governance resources
    Metadata transformationScripts to map exported information into destination import formats
    DataGalaxy glossary importCSV import with field mapping and validation
    Technical metadata collectionConnectors for supported technologies
    Glossary relationshipsLinked-object CSV imports
    Ownership assignmentsIdentity matching and destination ownership attributes
    Lineage reconstructionSource connectors and appropriate relationship mapping
    Governance validationReview of definitions, owners, dependencies, and critical use cases

    The approach is straightforward: extract the information you need, organize it according to the new catalog’s model, import it, and validate the business use cases that depend on it.

    For organizations moving to DataGalaxy, the platform’s CSV imports, connectors, business glossary, and relationship management capabilities provide the building blocks for this process.

    FAQ: Microsoft Purview migration

    Can you export a business glossary from Microsoft Purview?

    Yes. Classic Purview supports CSV exports of glossary terms with Data Curator permissions. Unified Catalog provides a separate API for retrieving supported glossary resources.

    Can you export data lineage from Purview?

    Microsoft provides APIs for retrieving relationships and querying lineage in classic Purview. When moving to another catalog, technical lineage can be reconstructed from supported source systems, while relevant documented relationships can be extracted and mapped to the destination.

    Why keep Purview object IDs during migration?

    Original object identifiers help match exported terms, assets, and relationships to their counterparts in the destination catalog. They’re also useful for checking the consistency of the imported information.

    Should you migrate the whole catalog at once?

    Start with a representative set of critical assets and business concepts. Validate their definitions, ownership, and dependencies before extending the import to the remaining catalog.

    Before you switch, know what you’re keeping

    A successful migration isn’t measured by how many objects you import. It’s measured by whether your teams can still find the right definitions, identify the right owners, and understand how their data is connected.

    The technical transfer matters, but so does preserving the governance knowledge your organization has built around its data.

    Planning your Microsoft Purview migration?

    Talk to our experts about your current environment, the governance information you want to preserve, and the available options for your transition to DataGalaxy.

    Talk to a DataGalaxy expert