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

# Migrar bóvedas de SQL Server a Devolutions Cloud

Migre bóvedas de un espacio de trabajo de SQL Server a un espacio de trabajo de Devolutions Cloud en Remote Desktop Manager, paso a paso y con las mejores prácticas.

Este artículo explica cómo migrar sus bóvedas de un espacio de trabajo de SQL Server a un espacio de trabajo de Devolutions Cloud en Remote Desktop Manager.

{% hint style="info" %}
Para que la migración se realice correctamente, revise las siguientes mejores prácticas y advertencias:

* Las bóvedas de usuario deben importarse manualmente.
* La configuración de permisos no se conserva durante la migración. Los administradores deben inventariar y documentar los permisos actuales antes de continuar.
* Haga una copia de seguridad de su base de datos de SQL Server para evitar la pérdida de datos en caso de problemas inesperados.
  {% endhint %}

#### Pasos de la migración

1. Cree un nuevo [Devolutions Cloud](https://docs.devolutions.net/cloud/es/getting-started/create-your-devolutions-cloud-workspace.md) e importe la licencia.
2. Añada Devolutions Cloud como espacio de trabajo en Remote Desktop Manager.
3. Exporte sus bóvedas de SQL Server e impórtelas en el espacio de trabajo de Devolutions Cloud.

#### Temas relacionados

* [Espacios de trabajo](https://docs.devolutions.net/rdm/es/ribbon-menu-bar/file/workspaces)
* [Exportar e importar bóvedas](https://docs.devolutions.net/rdm/es/knowledge-base/how-to-articles/export-and-import-vaults)
* [Permisos](https://docs.devolutions.net/rdm/es/user-group-based-access-control/permissions)


---

# 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/es/knowledge-base/how-to-articles/migrate-vaults-from-sql-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.
