Microsoft Purview Unified Catalog is Microsoft's SaaS data governance catalog on top of the Purview Data Map, billed per governed asset and per data quality processing unit. Pages here cover moving to self-hosted OpenMetadata or DataHub.
Moving from Purview Unified Catalog to self-hosted OpenMetadata: re-ingesting Azure and other sources with OpenMetadata connectors, carrying over glossary terms, owners and classifications through the Atlas-compatible APIs, and rebuilding data products and data quality rules.
Moving Purview metadata to self-hosted DataHub: rescanning sources with DataHub ingestion, exporting curated glossary and ownership data through the Purview REST APIs, mapping domains and data products, and planning DataHub's Kafka, database and search footprint.
Comparing Purview Unified Catalog with OpenMetadata: data products, glossary and data quality, connector coverage beyond Azure, lineage, billing per governed asset and DGPU against self-hosted infrastructure, and who operates each.
For data platform teams weighing Purview against DataHub: ingestion model and integrations, column-level lineage, glossary and governance features in DataHub Core versus DataHub Cloud, deployment on Kubernetes and the operating work it adds.
Cost of ownership by component: governed asset counts and DGPU consumption for data quality and health controls, against OpenMetadata or DataHub on your own infrastructure with database, search, ingestion compute, support and staff time.
Purview has no one-click catalog export. This page covers reading entities, glossary terms and lineage through the Atlas-compatible Data Map APIs, what is cheaper to rescan than export, and how to shape the output for import into OpenMetadata or DataHub.
Existing Azure Purview customers must consent to pay-as-you-go billing to use Unified Catalog, or stay on the classic Data Catalog. This page compares that switch, its billing model and its rebuild work with moving to self-hosted OpenMetadata or DataHub instead.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.