> 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/knowledge-base/migrate-a-local-workspace-to-devolutions-cloud.md).

# Migrate a local workspace to Devolutions Cloud

Use the Migrate to cloud workspace wizard in Remote Desktop Manager to copy a local SQLite or XML workspace into a Devolutions Cloud workspace.

The ***Migrate to cloud workspace*** wizard copies the data in your currently active local workspace (SQLite or XML) into a Devolutions Cloud workspace, without you having to manually export and import files.

{% hint style="info" %}
The migration wizard is currently available in Remote Desktop Manager Windows only, and only appears when your currently active workspace is a local SQLite or XML workspace.
{% endhint %}

1. Go to ***Administration*** – ***Maintenance*** and click ***Migrate to cloud workspace***.
2. Review what migrating to the cloud gives you (access from all your devices, automatic backups, and offline-friendly sync) and confirm the source workspace shown is the one you want to migrate.
3. Sign in to your Devolutions Account, or create one for free if you don't have one yet.
4. Choose the Cloud workspace to migrate into.
   * ***Select an existing Cloud workspace***, or ***create a new one***. When creating a new workspace, only the workspace name and Cloud region need confirming. The region is pre-filled based on your location, and both fields remain editable.
   * If the target workspace already has data in it, you're prompted to choose a destination folder; your entries are imported into it with their IDs remapped to avoid collisions with existing entries.
   * If the target workspace has shared vaults, you're prompted to choose between importing into your user vault (the default) or a shared vault. This choice only appears if a shared vault is available to you.
5. Confirm the source workspace, target workspace, vault, and folder, then click ***Start migration***. Each item has a ***Change*** link to go back and adjust it. Your local workspace is not modified or removed by this step.
6. Once the migration completes, you'll see a confirmation that your connections were successfully copied to your Cloud workspace.

{% hint style="info" %}
If your local workspace had a license assigned to it, that license is carried over to the Cloud workspace as part of the migration.
{% endhint %}

#### After the migration

Once the migration is complete, your local workspace is set to read-only. It isn't deleted or unlinked, but it can no longer be edited, which prevents your data from diverging between the two workspaces. You can make it writable again from the workspace's properties if needed.


---

# 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/knowledge-base/migrate-a-local-workspace-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.