> Source: https://builder-docs.ema.ai/administration/persona-export-import
> Title: AI Employee Export & Import

# AI Employee Export & Import

The Export & Import feature allows you to copy an AI Employee's complete configuration and data from one environment (the **source**) into another AI Employee (the **target**). This is useful for promoting configurations from staging to production, duplicating a proven setup across tenants, or restoring a previous state.

* * *

## How This Agent Works

The import process runs as a managed, multi-step workflow. The platform handles all the complexity of data replication, workflow copying, and configuration transfer automatically.

### Workflow Steps

1.  **Backup** -- The target AI Employee's current state is backed up before any changes are made. This backup is used for rollback if any subsequent step fails.
2.  **Tag structure sync** -- Tag dimensions and tags from the source AI Employee are ensured to exist in the target's database so that data replication can reference them.
3.  **Data replication** -- All widget data (knowledge bases, files, indexed content) is replicated from the source to the target. Each widget is replicated independently, and progress is tracked per widget.
4.  **Poll for completion** -- The platform monitors replication progress for each widget. You can track overall progress (completed nodes vs. total nodes) during this phase.
5.  **Workflow copy** -- The source AI Employee's workflow canvas (nodes, connections, and configuration) is deep-copied and associated with the target AI Employee.
6.  **Configuration update** -- The target AI Employee's configuration is updated to match the source, with widget name mappings applied to reflect the new data locations.
7.  **Cleanup** -- Old resources (the previous workflow and widget data) are removed from the target.
8.  **Finalize** -- The import request status is updated to reflect success or failure.

* * *

## Rollback on Failure

If any step fails during the import, the platform automatically rolls back the target AI Employee to its pre-import state:

-   The backed-up configuration is restored.
-   Any newly created resources (new workflow, new widget data) are deleted.
-   The import request is marked as **FAILED** with a detailed error message.

> [INFO]
> The rollback process ensures that a failed import never leaves the target AI Employee in a broken or partially-updated state.

* * *

## Progress Tracking

During the data replication phase, you can monitor progress through the import request status. The platform reports:

-   **Total nodes** -- The total number of data nodes across all widgets that need to be replicated.
-   **Completed nodes** -- The number of nodes that have been successfully replicated so far.

Progress updates are written to the database after every polling cycle, so you see near-real-time status even for large imports.

* * *

## Timeouts and Limits

Parameter

Value

Maximum replication poll duration

1 hour per widget

Maximum consecutive poll errors

5 (before the import is marked as failed)

Poll interval

10 seconds between status checks

* * *

## Requirements

-   Both the source and target AI Employees must belong to the **same tenant**.
-   The user initiating the import must have appropriate permissions on both AI Employees.
-   Integrations used by the source AI Employee should be available and configured in the target environment. The platform validates integration availability during the import process.

* * *

## Related Pages

-   [AIE Audit Log](/legacy-docs/administration/audit-log) -- Import events are recorded in the audit log.
-   [Workspaces & Tenants](/legacy-docs/administration/workspaces-tenants) -- Understanding tenant boundaries for import operations.