Azure Storage Mover vs rclone

Azure Storage Mover moves files and folders from on-premises systems and cloud sources into Azure Storage. It can transfer to Azure Blob Storage or Azure Files from sources using SMB 2.x/3.x, NFS 3/4 or S3. Choose a one-time migration, recurring transfers, or a metadata-only run that creates folder structures and permissions without transferring file contents. Transfers can retain file structure, permissions, attributes and metadata. An Azure-hosted resource coordinates jobs, authentication and progress; agents scan and transfer data from on-premises systems or cloud virtual machines. For AWS S3-to-Azure moves, Azure Arc connectors provide source access and allow server-to-server copying without an agent. Transfers use HTTPS, and Private Link to storage accounts is optional. Storage Mover is free for on-premises-to-Azure and AWS-to-Azure scenarios, though standard storage, transaction and networking charges apply. Resources can be created in six listed regions, while data can be ingested into all Azure public regions. Microsoft reports no per-job file or directory limit and testing up to 500 million objects in on-premises scenarios.

Rclone is a free command-line program for managing files on cloud storage. It can back up and restore files, mirror or migrate data, mount storage as a disk, and combine file systems. The project lists more than 70 cloud storage products, including Amazon S3, Google Drive, Dropbox, Microsoft OneDrive, and Backblaze B2. Sync options include copying changed files, one-way sync, and two-way bisync. Rclone checks MD5 and SHA1 hashes, preserves timestamps, and can restart operations. Where supported, it transfers between providers without using local disk. It can mount local, cloud, or virtual file systems and serve files over SFTP, HTTP, WebDAV, FTP, and DLNA. Rclone is also available through scripts and an API. Its crypt remote encrypts files before upload and decrypts them after download, but leaves file length and modification time unencrypted. The crypt password in the configuration file is only lightly obscured unless configuration encryption is enabled. The web-based GUI is described as experimental, and Android builds are not yet first-class builds.