--- title: "Export project to file" slug: "export-project-to-file" tags: ["Task topic"] status: "update" updated: 2026-10-05T12:09:46Z published: 2026-10-05T12:09:46Z canonical: "docs.staedean.com/export-project-to-file" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Export project to file To exchange a configuration, you can export a project. All elements that are related to the project are exported. Transactions and history are not exported. For example, the related messages and web service actions are exported, but the message history and web service history are not exported. Which settings are included in the export is defined by the **Export options** parameter in the **Connectivity studio parameters**. If you export a project and the export option is: - All, the full project configuration is exported, including the not encrypted secrets. - Encrypt environment secrets, the full project configuration is exported, but the secrets are encrypted. To encrypt the secrets, you must define the **Encryption key** in the **Connectivity studio parameters**. - Skip environment, the project configuration is exported except for the environment-specific properties of connectors and web service actions. As a result of the export, an XML file is created with the project configuration. This topic explains how to export a project configuration to a file. ### Steps 1. Click **Connectivity studio Integration Design**. 2. Click **Export** **project to file**. > [!NOTE] > **Note** > > - The current active project is exported. To export another project, on the **Connectivity studio - Integration design** workspace, in the **Project** field, select the desired project. > - For several project entities, number sequences are used. Only the references to the number sequence are included in the export. So, the number sequences itself are not exported. Therefore, before you import the project in another environment, make sure the referenced number sequences exist in that environment. The number sequences that are used in the project are shown in the export dialog. 3. In the **Download file** field, you can change the default file name as desired. 4. You can include environment-specific properties in the project export. Environment-specific properties are, for example: Select **Yes** in the **Including environment specific properties** field. > [!NOTE] > **Note** > > If you import a configuration with environment-specific properties in another environment, it is not guaranteed that these properties work properly. - **Passwords** - **Shares on connectors** - **File actions** 5. You can run the export of a project in the background. Usually, you do so if you export a project with many elements. While the project is exported, you can continue with other activities in the environment. Select **Yes** in the **Run in background** field. 6. Click **OK**. > [!NOTE] > **Notes** > > - You can also export a project from the **Project** page. On the **Action** Pane, on the **Deploy** tab, click **Export project to file**. > - If you run the export of a project in the background, you can monitor the status of the export transaction. The export transaction is only shown during the export. To monitor the export status, on the **Connectivity studio - Integration Design** workspace, click **Projects**. On the **Project** page, on the **Action Pane**, click **Deploy**, and click **Status of the transaction**. When a project export is finished, the transaction and created XML file are stored in the **Download transactions**. > - If you do not run the export in the background, when the export is finished, the XML is automatically downloaded to your local download folder.