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

# Migrar bóvedas de Devolutions Server a Devolutions Cloud

Migre bóvedas de Devolutions Server a Devolutions Cloud exportando un fichero rdm e importándolo en una bóveda del espacio de trabajo de Remote Desktop Manager.

Las bóvedas se pueden importar de Devolutions Server a Devolutions Cloud mediante un sencillo proceso de importación de ficheros. Así es como funciona:

1. Abra Devolutions Server en el navegador web que prefiera y vaya a la bóveda que desea migrar.
2. Haga clic en el botón de puntos suspensivos (***...***) en el área de contenido y seleccione ***Exportar (.rdm)***.
3. Marque todas las opciones que mejor se ajusten a sus necesidades. Elija ***v2*** como ***Versión del fichero de exportación***.

#### Con Remote Desktop Manager

1. Abra Remote Desktop Manager y conéctese a su espacio de trabajo de Devolutions Cloud.
2. Haga clic con el botón derecho en cualquier punto del panel de navegación de la bóveda que desee y, a continuación, haga clic en ***Importar*** – ***Importar en bóveda (.rdm)***.
3. Localice y abra el fichero ***.rdm*** exportado previamente desde Devolutions Server.
4. Elija si desea importar en la raíz o en una carpeta específica y, a continuación, haga clic en ***Importar***.
5. Seleccione las entradas que desea importar y haga clic de nuevo en ***Importar***.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/es/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 `build a script that syncs our docs to a CMS` 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.