rclone excels at cloud storage - but is it the right choice for storage-to-storage migrations?

What is rclone?

rclone is often described as "rsync for cloud storage." It's a powerful command-line tool that supports over 70 cloud storage backends including AWS S3, Google Cloud Storage, Dropbox, OneDrive, and many more.

rclone is excellent for cloud-to-cloud transfers and backup to cloud storage. However, when it comes to storage-to-storage migrations with NFS or SMB, it has some limitations that syncopio was designed to address.

Capability rclone â„¢
Primary Use Case Cloud storage sync storage-to-storage migration
User Interface CLI only (rclone rcd web GUI available) Full web dashboard
Backend Count 70+ cloud backends NFS, SMB, S3 (focused)
NFS Support Via local mount only Native NFS v3/v4
SMB Support Via local mount only Native SMB/CIFS
Distributed Workers Unlimited
ACL Preservation Limited (metadata flag) Full POSIX + NFSv4
Hard Link & Symlink Support No (copies as separate files) Both preserved
Pre-flight Analysis --dry-run, size/check Detailed breakdown + ETA
Post-Transfer Verification check command (separate) Built-in verification phase
Encryption Built-in crypt TLS in transit
Scheduling External (cron) Built-in scheduler
Reporting Log output Automatic PDF / CSV / Excel
Cost Free (MIT) Commercial

Where rclone Shines

  • 70+ cloud backends

    If you need to sync to Backblaze B2, Wasabi, Google Drive, or dozens of other cloud services, rclone is unmatched.

  • Built-in encryption

    The crypt backend provides client-side encryption for untrusted cloud storage.

  • Mount as filesystem

    rclone mount lets you access cloud storage as a local filesystem - great for occasional access.

  • Active community

    Large user base, frequent updates, and extensive documentation.

rclone Limitations for Migrations

  • 1.
    No native NFS/SMB support

    rclone accesses NFS and SMB through local mounts, not native protocol support. This means you need to mount both source and destination on the same machine, losing the benefits of direct protocol communication.

  • 2.
    No distributed workers

    rclone runs as a single process. For large migrations, you'd need to manually partition the workload across multiple rclone instances.

  • 3.
    Limited ACL handling

    While rclone has a --metadata flag, ACL support is limited. POSIX and NFSv4 ACLs may not transfer correctly between NAS systems.

  • 4.
    Hard links and symlinks become separate files

    rclone doesn't track hard links or symlinks — each hard link becomes a separate file copy, potentially doubling storage usage. Symlinks may be skipped entirely.

  • 5.
    Optimized for cloud, not NAS

    rclone's architecture is optimized for API-based cloud backends, not the high-throughput, low-latency requirements of storage-to-storage transfers.

Use rclone when:

  • Cloud storage is your destination
  • You need client-side encryption
  • ACLs aren't critical
  • Single-machine transfer is sufficient
  • Budget is zero

Use syncopio when:

  • Storage-to-storage is your primary use case
  • ACL preservation is required
  • You need to scale with multiple workers
  • Hard links and symlinks must be preserved
  • Team needs web dashboard visibility
  • Enterprise support is needed

Can rclone and syncopio Work Together?

Absolutely! Many organizations use both tools for different purposes:

  • syncopio for primary storage-to-storage migrations between data centers
  • rclone for backup copies to cloud storage (S3, B2, etc.)
  • syncopio handles the production migration with full ACL support
  • rclone syncs archives to encrypted cloud storage for disaster recovery

rclone Commands vs syncopio Features

rclone sync Mirror mode (with safety checks)
rclone copy Update mode (no deletions)
rclone check Post-transfer verification (built-in)
rclone size Pre-flight analysis (with breakdown)
rclone --dry-run Pre-flight analysis (always available)
rclone --bwlimit Bandwidth throttling (per-worker)

See what you're missing. And what it's costing you.