> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/export-and-import-workflows.md).

# Export and Import Workflows

**AI Workflow Studio** supports a new job-based export and import process for workflows, powered by App Sync. Resource connections and mappings are handled automatically, and dependencies are configured before an import is finalized.

### **To export Workflows:**

1. In the **Aisera Admin UI**, navigate to **AI Automation > AI Workflow Studio**.
2. Do one of the following:
   1. Open a specific Workflow, select the **More Options** menu, then select **Export**.

      <img src="https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FuA0pmdxWb9JNMvWUmbfk%252Funknown.png%3Falt%3Dmedia%26token%3Dc6fba5cd-7edb-47aa-8d39-437f729f080f&#x26;width=768&#x26;dpr=3&#x26;quality=100&#x26;sign=296f64a9&#x26;sv=2" alt="" height="322" width="438">
   2. Select one or more Workflows from the list view, then select **Actions > Export**.
3. Navigate to **Settings > Jobs**, then and wait for the export job to complete.
4. Select the **Link to download** in the **Output** field of the completed export job to download the exported workflows

### **To import Workflows:**

1. Switch to the target app and navigate to **AI Automation > AI Workflow Studio**.
2. From the Workflows list page, open the **Import** dropdown and select **Import**.
3. Select the exported workflow file from your local machine. A Pre-Import job will start automatically.
4. Navigate to **Settings > Jobs** and wait for the Pre-Import job to complete.
5. Navigate back to **AI Automation > AI Workflow Studio** and select **Configure Imported Resources** at the top of the page to open the Resource Configuration Mapping Wizard.
6. Review and configure any integration or data source mappings, then select OK to confirm.
7. Monitor the final import job in the **Job List** page.
8. Once complete, navigate back to **AI Automation > AI Workflow Studio** to verify the imported workflows.

If no mappings appear in the Resource Configuration Mapping Wizard, select OK to proceed directly to the final import job.

Imported workflows are set to Published status by default. Testing and any additional configuration should be completed before putting them into use.

### **Workflow Export/Import Includes Sub-Flows**

The Workflow Export/Import feature now allows you to include sub-flows within your export/import package.

{% hint style="info" %}
After importing, you must publish each sub-flow before publishing the parent flow.
{% endhint %}

### Import validation for 1.0 to 2.0 applications

When you import workflows from 1.0 applications, metadata validation runs to ensure they import and function correctly. Required metadata fields include **Description** and **Category**. Workflows missing either field cannot be published. Add the missing metadata to publish the Workflow.

{% hint style="info" %}
Tenant-level workflows are exempted from this validation as they are not tied to a specific application.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/export-and-import-workflows.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.