> 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/import.md).

# Import

Import JSON and CSV entry files into Devolutions Cloud from RDM, Bitwarden, Chrome, KeePass, LastPass, and 1Password into a chosen vault and folder.

Import JSON and CSV entry files in Devolutions Cloud.

1. In ***Help & tools***, click on ***Import***.
2. Select the format of the imported file (JSON or CSV) between the following options:
   * RDM (.json)
   * Bitwarden (.json)
   * Bitwarden (.csv)
   * Google Chrome (.csv)
   * KeePass (.csv)
   * LastPass (.csv)
   * 1Password (.csv)
3. Upload the file (one at a time) to Devolutions Cloud by either dragging and dropping it directly or by selecting a file through your device's file browser.
4. Select a ***Destination vault*** (Devolutions Cloud only) and a ***Destination folder***, or create a new folder. This is where the entries are imported.
5. Click ***Import***.
6. A summary of all the entries to import will appear. Click ***Complete import***.

   The import process takes some time depending on the size of your file. Once the file is imported, you will be brought to where the entries are located.


---

# 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/import.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.