Skip to main content

Revamped dbt experience

Migration timeline

Atlan recommends migrating to the revamped dbt experience for improved product capabilities. All dbt fixes and new product capabilities are supported on the revamped version only. Atlan no longer supports the old experience starting February 15, 2026.

This FAQ explains the revamped dbt experience, highlighting what’s changing, why it matters, and what to know before migrating.

What is changing in the revamped dbt experience?​

Atlan now creates a separate dbt asset for each environment run. For example, if your customers model runs in both Production and Staging, you see two assets in Atlan: customers (Production) and customers (Staging).

What are the benefits of migrating to the revamped experience?​

Separating assets into environment-based assets provides several benefits:

  • Environment-specific metadata: Each environment asset has its own metadata. Previously, Atlan used metadata from the last run across all environments to enrich a single asset, which resulted in incorrect or missing metadata.

  • Environment-specific lineage: Each environment asset has its own lineage. The previous experience resulted in incorrect or missing lineage.

  • Enhanced capabilities: The revamped experience includes:

    • View the last 5 runs of a dbt asset in a given environment
    • View detailed error messages for failed runs
    • Table-level dbt sources (previously grouped all tables into one source, resulting in incorrect or missing metadata and lineage)
    • Improved dbt workflow performance
    • View both compiled and raw SQL for assets

What changes after migration?​

The first time after upgrade, the workflow takes longer than normal because Atlan deletes old assets and publishes new assets. Instead of updating a few assets that were modified, all assets are deleted and new assets are created.

Since old assets are deleted, the following changes occur:

  • Asset FQN and GUIDs change: This affects:

    • Any playbooks or code that manually update asset metadata or lineage won't work properly as the FQN/GUID equivalent asset no longer exists
    • Existing access management policies that depend on FQN won't function properly
    • You need to manually add new dbt assets to favorites
    • You need to manually add dbt assets used in data products

  • Manually updated metadata or lineage is deleted: If you have manually updated metadata through the UI or API, this metadata or lineage isn't retained.

If you have any of the previous cases, note them down to update them after migration.

How do I migrate to the revamped experience?​

Migration details are shared once the changes are released. Migration is as simple as clicking a button, or you can contact Atlan support for assistance.

See also​

Need help​

If you can't find the answer you're looking for, contact Atlan support: Submit a request.