Skip to main content

Enrichment Migrator
App

You can automatically migrate metadata enrichment such as descriptions, owners, terms, tags, and custom metadata between assets in Atlan. This helps preserve business context and reduce manual rework when rebuilding connections, moving assets across environments, or replatforming data systems.

This reference provides complete configuration details for the Enrichment Migrator app. Use this page to look up property definitions, valid values, and configuration formats when setting up automated enrichment migration between source and target connections.

Access​

The Enrichment Migrator app isn't enabled by default. To use this app, contact Atlan support and request it be added to your tenant.

Credentials​

This section defines the core configuration properties required to identify and authenticate the workflow.

Workflow name​

Specifies a unique and descriptive name for the migration workflow. The name appears in the workflow list and helps identify different migration configurations.

Example:

atlan-prod-enrichment-migrator

Assets​

Defines the source and target assets involved in the enrichment migration.

Source​

Specifies the connection from which enrichment is copied. This connection serves as the source environment containing existing metadata enrichment such as descriptions, owners, terms, tags, and custom metadata.

The workflow extracts enrichment from assets in this connection that match the filters defined in Limit to (prefix).
Make sure that the user configuring the workflow has permission to access the source connection and view its metadata.

Example:

Snowflake Connection - Old

Limit to (prefix)​

Narrows down assets within the source connection using a qualified name prefix.
Use this field to restrict the migration to specific databases, schemas, or tables within the connection.

This setting helps control the migration scope and avoid unnecessary data transfer by targeting only relevant subsets of assets.

Example: If you want to migrate enrichment for a single database and schema:

DB1/SCH2

Example: If you want to migrate enrichment only for a specific schema across multiple databases:

*/ANALYTICS

Example: If you want to migrate enrichment for a specific table within a schema:

DB1/SCH2/SALES_DATA

Target database pattern​

Defines a regular expression pattern to map enrichment from one source database to one or more target databases.
This property enables flexible migration patterns when target databases follow consistent or predictable naming conventions.

This setting enables the workflow to copy enrichment from a single source database to all target databases whose names match the provided regex pattern. The workflow uses the pattern in a .where(Asset.NAME.regex(sourcePrefix)) clause, where sourcePrefix is the configured target database pattern.

When a value is specified, the workflow replaces the source database name (from Limit to (prefix)) with all matching target database names according to the provided regex pattern.

  • Example: To copy enrichment from SALES_DB to all databases that begin with SALES_DB_ (such as SALES_DB_US and SALES_DB_EU):
SALES_DB_.*
  • Example: To copy enrichment from DB1 to any database that ends with DB1 (such as NEW_DB1 or ARCHIVE_DB1):
.*DB1

If no pattern is provided, enrichment is only copied to the database specified in the Target connection.

Target​

Specifies the connection that receives the copied enrichment. This connection serves as the destination environment where metadata enrichment from the source connection is applied.

The target connection must already exist in Atlan and contain assets that match those in the source by qualified name structure. The workflow updates only existing target assets, it doesn't create new ones, so alignment between source and target asset hierarchies is required for successful migration.

Example:

Snowflake Connection - New

Include archived?​

Determines whether archived assets are included in the migration process.

  • Yes: Include archived assets (for complete metadata parity).
  • No: Skip archived assets to focus on active metadata only.

Options​

Controls how the workflow handles errors and exceptions during migration.

  • Default: Continues processing even when non-critical validation errors occur. Logs warnings for review.
  • Advanced: Stops the migration when any data inconsistency or invalid value is encountered.

Attributes​

Defines which enrichment attributes are migrated from source to target.

Limit to​

Specifies whether the migration must include only selected attributes or exclude specific ones.

  • Only the following: Migrate only the listed attributes (for example, description, owners).
  • All enrichment except: Migrate all enrichment except those specified (useful when excluding a few attributes).

Attributes​

Specifies which enrichment attributes to include or exclude during migration, based on the selection made in the Limit to option. Use this field to control which types of metadata enrichment are copied from the source assets to the target assets.

Common enrichment attributes include:

  • Descriptions: Both system and user-provided.
  • Owners: Users or groups responsible for the asset.
  • Assigned terms: Glossary terms attached to the asset.
  • Assigned tags: Classification or governance tags.

Limit custom metadata to​

Specifies how custom metadata attributes are filtered and migrated from the source to the target connection.
Use this setting to control whether all, some, or specific custom metadata attributes are included in the migration process.

Custom metadata fields often capture business-specific information, such as data quality ratings, sensitivity levels, or ownership notes that you may want to migrate selectively depending on the target environment or governance policy.

Available options:

  • Only the following: Migrate only the custom metadata attributes explicitly listed in the Custom metadata field. Use this option when you want to copy only a subset of enrichment that's relevant to the target environment (for example, key business attributes or compliance tags).

  • All custom metadata except: Migrate all custom metadata enrichment except the attributes listed in the Custom metadata field. Use this when you need to exclude environment-specific metadata such as deprecated classifications or internal annotations.

Example:

  • If you want to migrate only key business metadata fields like Data Quality::Completeness and Business::Criticality, select Only the following and specify those attributes.

  • If you want to exclude temporary or deprecated fields like Migration::MigrationStatus or Legacy::LegacyOwner, select All custom metadata except and list those attributes.

Custom metadata​

Specifies the list of custom metadata fields to include or exclude during migration, based on the selection made in the Limit custom metadata to option.
Use this field to define exactly which business-specific metadata attributes must be transferred between connections.

Each entry must match the display name of an existing custom metadata field in Atlan.
For the migration to succeed, these custom metadata fields must exist in both the source and target environments with identical configurations—including name, data type, and structure.

Example:

Data Quality::Completeness, PII Classification::Sensitivity Level

Need help?​

If you have any issues related to configuring the app, contact Atlan support.