Import Organization Export via CLI
This guide explains how to re-import an Entropy Data organization export (zip file) using the Entropy Data CLI.
Export
To export your organization data, navigate to Settings > Export in the left sidebar of your organization. This page is only available to organization owners.
The export page shows a preview with counts of each resource type. Click the download button to generate a zip archive containing all your organization's resources as YAML files:
- Data products
- Data contracts
- Teams (including members and roles)
- Tags
- Definitions
- Assets
- Source systems (deprecated)
- Access agreements
Import
entropy-data --api-key your-api-key --host https://app.entropy-data.com import zip export.zip
The CLI handles dependency ordering, team hierarchy resolution, and member stripping automatically.
Prerequisites
- Entropy Data CLI installed via
uv tool install entropy-data-cli - An API key with organization-level scope for the target Entropy Data instance
- The export zip file from Entropy Data
Configuration
Set your API key and host as environment variables or in a .env file to avoid passing them on every command:
export ED_API_KEY="your-api-key"
export ED_HOST="https://app.entropy-data.com"
Then simply run:
entropy-data import zip export.zip
What Gets Imported
The export zip contains the following resources, which are imported in dependency order:
| Directory | Resource Type |
|---|---|
teams/ | Teams |
tags/ | Tags |
definitions/ | Definitions |
dataproducts/ | Data products |
datacontracts/ | Data contracts |
assets/ | Data assets |
access/ | Access agreements |
Known Issues
- Team members: Exported teams may reference users (email addresses) that don't exist in the target organization. The CLI strips members automatically during import.
- Access agreements: Some access agreements may reference deleted data products (marked as
'unknown'), which will fail during import. These are typically rejected/cancelled agreements that can be safely skipped.