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

# Migrate vaults from SQL Server to Devolutions Cloud

Migrate vaults from an SQL Server workspace to a Devolutions Cloud workspace in Remote Desktop Manager, step by step with best practices.

This article explains how to migrate your vaults from an SQL Server workspace to a Devolutions Cloud workspace in Remote Desktop Manager.

{% hint style="info" %}
For a successful migration, review the following best practices and warnings:

* User vaults must be imported manually.
* Permission settings are not retained during the migration. Administrators should inventory and document current permissions before proceeding.
* Back up your SQL Server database to prevent data loss in case of unexpected issues.
  {% endhint %}

#### Migration steps

1. Create a new [Devolutions Cloud](/cloud/getting-started/create-your-devolutions-cloud-workspace.md) and import the license.
2. Add the Devolutions Cloud as a workspace in Remote Desktop Manager.
3. Export your SQL Server vaults and import them into the Devolutions Cloud workspace.

#### Related topics

* [Workspaces](https://docs.devolutions.net/rdm/ribbon-menu-bar/file/workspaces)
* [Export and import vaults](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/export-and-import-vaults)
* [Permissions](https://docs.devolutions.net/rdm/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/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.