Migration software
rclone
Suggested in one of our migration playbooks, mainly for Servers and cloud. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that rclone gets around, as covered in our playbooks.
Cloud-to-cloud migration
- Pick an object copy tool for the Azure to AWS directionOpen-source command-line tool with Azure Blob Storage and Amazon S3 (and S3-compatible) backends, so rclone sync can copy a container to a bucket and later passes copy only changes.
- AzCopy cannot write to Amazon S3, so it does not help with Azure to AWS or repatriation copies.Open-source tool that copies between Azure Blob, Amazon S3 and S3-compatible storage in either direction, with later passes copying only changes.
How it handles key settings
From the settings checklists in our playbooks: what rclone carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Object metadata and bucket names | With --metadata, maps metadata to Azure Blob headers, user metadata and tags. Stores modification time as metadata (mtime), because it cannot set Azure's Last-Modified. | Cloud-to-cloud migration |
| Storage tiers and archived objects | Cannot read blobs in the archive tier until they are rehydrated. | Cloud-to-cloud migration |
| Top-up copies (delta passes) | Copies in either direction between Azure Blob, Amazon S3 and S3-compatible storage; later passes copy only changes. | Cloud-to-cloud migration |
Tools for the same jobs
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.