Ataccama ONE Import Export: Data Quality Rule Migration Guide

Moving Data Quality Rules Across Environments in Ataccama ONE 

Every mature data governance framework operates across multiple environments. Teams build and refine data quality rules in sandbox environments, validate them in testing, and then promote them to production. However, this transition is often one of the most error-prone steps in any data governance workflow. 

Ataccama ONE addresses this challenge through a structured import and export framework, making it easier to manage data quality rule lifecycle management across environments. This approach creates a repeatable and controlled process for moving metadata, rules, and glossary terms without introducing risk. 

How Export Plans Work in Ataccama ONE 

Export plans are JSON-based configurations that define what metadata gets transferred between environments. They help teams standardize metadata management and ensure only the required assets are included in the migration. 

Out-of-the-box export plans in Ataccama ONE cover: 

• Business glossary terms 

• Data quality rules 

• Reference data 

• Data lineage repositories 

Teams can also create custom export plans to support specific data governance best practices and align with their internal promotion workflows. 

Step-by-Step: Export and Import Data Quality Rules 

Export from Source Environment 

1. Navigate to Global Settings → Application Settings → Import and Export 

1. Create a new export and select the appropriate export plan 

1. Choose encryption settings (use AES-256 encryption for secure transfers across environments) 

1. Run the export and download the ZIP file from the Notification Center 

Import into Target Environment 

1. Open Import and Export in the target instance 

1. Upload the exported ZIP archive 

1. Enter the password if encryption was applied 

1. Run validation before deployment to identify conflicts or missing dependencies 

1. Choose import mode: 

1. Draft (recommended for production validation) 

1. Published (for direct deployment) 

This validation-first approach supports reliable data quality rule validation and prevents errors during production rollout. 

Key Considerations for Rule Migration 

Validate Before Promotion 

Asset IDs, such as DQ dimension IDs, may differ across environments. Always validate to avoid broken references and ensure smooth data governance environment migration. 

Avoid Migrating Environment-Specific Data 

Data source connections and profiling results should remain within their original environments. Focus on migrating only data quality management configurations and metadata. 

Use Monitoring Lifecycle Instead of Direct Migration 

Monitoring projects should follow a structured lifecycle rather than direct export/import. This ensures proper mapping between development and production datasets within your enterprise data governance setup. 

Why This Matters for Data Governance 

A structured approach to migrating data quality rules is essential for maintaining consistency and trust in your data. Without it, organizations risk introducing inconsistencies, broken dependencies, and governance gaps. 

With Ataccama ONE, teams can: 

• Standardize data governance workflows 

• Improve data quality automation 

• Reduce deployment errors 

• Ensure consistent rule enforcement across environments 

Final Thoughts 

Moving rules between environments doesn’t have to be a risky process. With a well-defined import and export process in Ataccama ONE, organizations can turn environment promotion into a predictable and controlled step in their data governance strategy. 

By combining structured export plans, strong validation practices, and clear governance policies, teams can confidently manage data quality rules across environments—without compromising accuracy or control.