> 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/rdm/ribbon-menu-bar/administration/migrate-workspace.md).

# Migrate workspace

Migrate a Remote Desktop Manager workspace between supported SQL Server and Azure SQL destinations without altering the source workspace.

When migrating a workspace in Remote Desktop Manager, all data in the destination workspace will be erased, but the source workspace will remain untouched.

{% hint style="danger" %}
It is highly recommend to [clean up](/rdm/ribbon-menu-bar/administration.md#clean-up) your workspace before proceeding with the migration.
{% endhint %}

The supported workspace combinations are:

* ***SQL Server*** to ***SQL Server***
* ***SQL Server*** to ***Azure SQL***

To start the migration process on Remote Desktop Manager's side, click the ***Administration – Migrate workspace*** button located in the top ribbon, and select the destination workspace.

{% hint style="info" %}
Follow [Microsoft’s best practices](https://learn.microsoft.com/en-us/data-migration/sql-server/overview) for the detailed steps to migrate a local SQL workspace.
{% endhint %}


---

# 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/rdm/ribbon-menu-bar/administration/migrate-workspace.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.