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

# Migrare le casseforti da Devolutions Server a Devolutions Cloud

Migri le casseforti da Devolutions Server a Devolutions Cloud esportando un file rdm e importandolo in una cassaforte dello spazio di lavoro di Remote Desktop Manager.

Le casseforti possono essere importate da Devolutions Server a Devolutions Cloud tramite un semplice processo di importazione di file. Ecco come funziona:

1. Apra Devolutions Server nel browser web di sua scelta e vada alla cassaforte da migrare.
2. Clicchi sul pulsante con i puntini di sospensione (***...***) nell'area dei contenuti e selezioni ***Export (.rdm)***.
3. Selezioni tutte le opzioni più adatte alle sue esigenze. Scelga ***v2*** come ***Export file version***.

#### Con Remote Desktop Manager

1. Apra Remote Desktop Manager e si connetta al suo spazio di lavoro Devolutions Cloud.
2. Clicchi con il tasto destro in un punto qualsiasi del riquadro di navigazione della cassaforte di sua scelta, quindi clicchi su ***Import*** – ***Import in vault (.rdm)***.
3. Individui e apra il file ***.rdm*** precedentemente esportato da Devolutions Server.
4. Scelga se importare nella radice o in una cartella specifica, quindi clicchi su ***Import***.
5. Selezioni le voci da importare e clicchi nuovamente su ***Import***.


---

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