# Import and export workspaces

### Overview

Import/export lets you move a workspace configuration between environments. Use it for backups, restores, and standardizing setups across teams.

You export a workspace configuration as a JSON file. You import that JSON into an **existing** workspace.

Import triggers a **workspace import job**. Track it from the **Saved Workspaces** panel.

{% hint style="info" %}
Import/export moves configuration only. It does not move data, generated outputs, or database credentials.
{% endhint %}

### Permissions and prerequisites

You need **Editor rights or higher** on the workspace.

Before importing:

* Create the target workspace first. See [Create a workspace](/setup-workspaces/create-a-workspace.md).
* Make sure the workspace mode matches. See [Workspace modes](/setup-workspaces/create-a-workspace/workspace-modes.md).
* Make sure the same the target workspace has the same db type for the source database.
* Make sure the same tables/columns exist in the target workspace.
* Make sure the Syntho version matches.

### When to use this

Use import/export to:

* Reuse configurations across environments
* Keep masking and synthesis settings consistent
* Back up a workspace before risky changes
* Restore previous configurations
* Review changes in Git (JSON is readable)
* Share a configuration with other teams

### Export a workspace

Export downloads a zipped JSON file with your workspace configuration.

{% stepper %}
{% step %}

#### Open the workspace

Open the workspace you want to export.
{% endstep %}

{% step %}

#### Start export

Click the **actions menu** next to the workspace name. Select **Export workspace**.
{% endstep %}

{% step %}

#### Save the JSON

Your browser downloads a `.json` file. Store it somewhere versioned if possible.
{% endstep %}
{% endstepper %}

You can also export from the **Workspaces view** by selecting **Export** in the workspace actions menu.

### Import a workspace

Workspace configurations can only be imported into an **existing workspace**.

{% hint style="warning" %}
Import **overwrites** configuration in the target workspace. Export the current state first if you may need to roll back.
{% endhint %}

{% stepper %}
{% step %}

#### Open the target workspace

Open the workspace that should receive the configuration.
{% endstep %}

{% step %}

#### Start import

Click the **actions menu** next to the workspace name. Select **Import workspace**.
{% endstep %}

{% step %}

#### Select the zipped JSON file

Browse and select the exported zipped JSON file. Click **Import**.
{% endstep %}

{% step %}

#### Confirm overwrite

Confirm the overwrite when prompted. This starts a **workspace import job**.
{% endstep %}
{% endstepper %}

Track the job status from [View workspaces](/setup-workspaces/view-workspaces.md).

### What’s included

The exported file contains all relevant workspace settings, including:

* PII status for each column
* Suggested generators
* Assigned generators
* Consistent mapping settings
* Table inclusion or exclusion
* Table and column-level configurations
* Workspace mode and default settings

The file is human-readable. You can review and edit it before importing.

### What’s not included

Import/export does **not** move:

* Source/destination connection credentials or secrets
* Actual data (source or generated)
* Job run history, logs, or reports

### How import applies changes

* Importing **overrides** the current workspace configuration.
* Only matching tables and columns are updated.
* Missing or unmatched tables/columns are ignored.
* If the workspace mode differs, import can fail or produce unexpected results.
* Import between different Syntho versions is not recommended.

### Best practices

* After upgrading Syntho to latest version, export a workspace before making major changes.
* Keep exports in Git to review diffs and audit changes.
* Import into a staging workspace first.
* Re-run the PII scanner if needed after importing. See [Automatic PII discovery with PII scanner](/configure-a-data-generation-job/privacy-dashboard/automatic-pii-discovery-with-pii-scanner.md).

### Troubleshooting

* **Nothing changed after import**: the target workspace may not contain matching tables/columns.
* **Mode mismatch**: align modes before importing. See [Workspace modes](/setup-workspaces/create-a-workspace/workspace-modes.md).
* **Settings behave differently than expected**: compare workspace defaults. See [Workspace default settings](/setup-workspaces/workspace-default-settings.md).
* **Version mismatch:** upgrade Syntho to latest before exporting. Then do the same before importing, so Syntho versions are the same.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.syntho.ai/setup-workspaces/import-and-export-workspaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.