Manage asset lifecycle
Use these workflows to assess the downstream impact of deprecations and migrations before taking action. Deprecating an asset that still has active consumers, or migrating a schema without knowing what depends on it, can cause unplanned failures in downstream pipelines and dashboards. These workflows surface consumer counts, ownership, and certification status so you have a complete picture before any changes are made.
Make sure Atlan MCP is configured before running these workflows. For setup, see Set up Atlan MCP.
Safely deprecate unused assets
Deprecating an asset without checking lineage first is risky—pipelines and dashboards that depend on it break silently. This workflow surfaces every active consumer of an asset, notifies their owners, and marks it as deprecated only after the communication is done.
I want to deprecate the legacy_orders_v1 table. Show me every downstream table and dashboard still consuming it and their owners. Then add a deprecation notice saying it will be removed in 30 days and mark the table as deprecated.
Triage assets for migration
Migrations fail when teams discover mid-execution that a 'low priority' table has 20 downstream consumers, no owner, and no documentation. This workflow evaluates every asset in the source environment—by consumer count, ownership, and certification—and assigns a migration priority before the work begins.
We're migrating all tables in the legacy_dwh schema to the new warehouse. For each table, show me how many downstream consumers it has, who owns it, and whether it's certified. Then classify each one as high, medium, or low migration priority and write that to the Migration Priority custom metadata field.