Rclone can copy and synchronize across many storage backends. A replacement must be tested against the exact remote and operation you use. Start with the Rclone alternatives page.
Safe test
- Use a disposable source and destination with nested paths, Unicode names, large files, and changed timestamps.
- Compare copy versus sync behavior, especially deletion propagation.
- Interrupt a transfer, resume it, and verify final hashes or provider checksums.
- Test credentials, encryption if needed, rate limits, and detailed logs.
- Measure throughput and API charges under a realistic file mix.
Never point a new sync job at your only copy. Keep a separate backup and dry-run where supported before permitting deletion.