> 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/server/knowledge-base/how-to-articles/migrate-vaults-from-devolutions-server-to-devolutions-cloud.md).

# Migrate vaults from Devolutions Server to Devolutions Cloud

Migrate vaults from Devolutions Server to Devolutions Cloud by exporting an rdm file and importing it into a Remote Desktop Manager workspace vault.

Vaults can be imported from Devolutions Server to Devolutions Cloud by way of a simple file importation process. Here is how this works:

1. Open Devolutions Server in your chosen web browser, and head over to the vault to migrate.
2. Click on the ellipsis button (***...***) in the content area, and select ***Export (.rdm)***.
3. Check all the options that best fit your needs. Choose ***v2*** as the ***Export file version***.

#### With Remote Desktop Manager

1. Open Remote Desktop Manager, and connect to your Devolutions Cloud workspace.
2. Right-click anywhere in the navigation pane of the vault of your choice, then click on ***Import*** – ***Import in vault (.rdm)***.
3. Locate and then open the ***.rdm*** file previously exported from Devolutions Server.
4. Choose whether to import at root or in a specific folder, then click on ***Import***.
5. Select the entries to import, and click on ***Import*** again.


---

# 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/server/knowledge-base/how-to-articles/migrate-vaults-from-devolutions-server-to-devolutions-cloud.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.