> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/web-interface/help-and-tools/export/powershell-script-export-type.md).

# PowerShell script export type

Use a PowerShell script to export Devolutions Cloud data to JSON or CSV, filling in application identity credentials automatically or manually.

Use a PowerShell script to export your data in JSON or CSV format. This method is only available with Devolutions Cloud and requires PowerShell 7 or later.

First choose whether you want to automatically or manually fill in your information in the PowerShell script.

### Automatically fill in the information

1. In ***Help & tools***, click on ***Export***.
2. Select the ***PowerShell script*** export type.
3. Next, create an [Application identity](/cloud/web-interface/administration/management/application-identities/manage-application-identities.md) with the right to export the desired vaults (see [Roles and Permissions](/cloud/web-interface/administration/configuration-and-security/system-permissions/roles-and-permissions.md) for more details). Enable ***Can access user vaults*** only to include every user vault in the export. To export a single vault, see [Export a single vault with PowerShell](/cloud/knowledge-base/how-to-articles/export-a-single-vault-with-powershell.md).
4. Select the ***Automatic*** option.
5. Enter your application identity's ***Application secret*** and ***Application key*** in the corresponding fields.
6. Enter the ***Destination folder path***. This is where your data will be exported.
7. Choose to export in JSON or CSV.
8. Click ***Download***.
9. Run the downloaded script using PowerShell 7.

Your data has been exported to the destination folder.

### Manually fill in the information

1. In ***Help & tools***, click on ***Export***.
2. Select the ***PowerShell script*** export type.
3. [Create an application identity](/cloud/web-interface/administration/management/application-identities.md) and assign it the ***Vault owners*** role, or a custom role that includes the ***Export*** permission, for the desired vault.
4. Select the ***Manual*** option.
5. Choose to export in JSON or CSV.
6. Copy and paste the script in a PowerShell file (.ps1).
7. In your copied script, change the variables with the appropriate information. See the table below.

   <table><thead><tr><th width="211.79998779296875">Variable</th><th>Description</th></tr></thead><tbody><tr><td><code>$url</code></td><td>Enter your Devolutions Cloud URL. This variable is automatically filled in, but it is still possible to change it.</td></tr><tr><td><code>$appSecret</code></td><td>Enter the application user's <em><strong>Application secret</strong></em>.</td></tr><tr><td><code>$appKey</code></td><td>Enter the application user's <em><strong>Application key</strong></em>.</td></tr><tr><td><code>$pathToExportedFolder</code></td><td>Enter the <em><strong>Destination folder path</strong></em>. This is where your data will be exported.</td></tr></tbody></table>
8. Run the script using PowerShell 7.

Your data has been exported to the destination folder.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/cloud/web-interface/help-and-tools/export/powershell-script-export-type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.