Migrate a local workspace to Devolutions Cloud

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.

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.

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.

If your local workspace had a license assigned to it, that license is carried over to the Cloud workspace as part of the migration.

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.