Migrate IDrive e2 to Backblaze B2 — Transfer Files with RcloneView
Move object storage buckets between two S3-compatible providers without staging files locally first.
Switching S3-compatible object storage providers usually means picking apart access keys, endpoints, and bucket structures before a single file moves. RcloneView connects to both IDrive e2 and Backblaze B2 as native remotes, so a migration between them is a direct cloud-to-cloud transfer instead of a two-step download-then-upload process.
Manage & Sync All Clouds in One Place
RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.
- One-click jobs: Copy · Sync · Compare
- Schedulers & history for reliable automation
- Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
Free core features. Plus automations available.
Connecting Both Remotes
IDrive e2 and Backblaze B2 are both configured through RcloneView's S3-compatible remote setup, requiring an Access Key, Secret Key, and endpoint for each. For Backblaze B2 specifically, RcloneView also supports its native credential entry method using an Application Key ID and Application Key, which some teams prefer over the S3-compatible route. Once both remotes appear in the Remote Manager, open two Explorer panels side by side — one per remote — using RcloneView's horizontal or vertical split layout.
With both buckets visible at once, you can browse folder structures on each side before committing to a transfer, which catches naming mismatches or unexpected nested folders early.
Running the Transfer as a Sync Job
Rather than dragging large buckets manually, set up a Sync job through the 4-step wizard: select IDrive e2 as source, Backblaze B2 as destination, and choose One-way sync so the destination is only modified to match the source — nothing on IDrive e2 changes. In Step 2, RcloneView mounts AND syncs 90+ providers from one window, and lets you tune the number of file transfers and enable checksum comparison so files are verified by hash and size, not just modification time, which matters when migrating between two different storage backends.
Before running the real transfer, use Dry Run to preview exactly which files will copy and confirm nothing unexpected gets deleted or skipped.
Verifying the Migration
After the sync completes, Job History shows total size transferred, transfer speed, and file count for that run, giving you a record to compare against the source bucket's totals. For an extra check, RcloneView's Folder Compare tool can run a side-by-side comparison between the two buckets after migration, flagging any files that differ in size or exist on only one side.
Getting Started
- Download RcloneView from rcloneview.com.
- Add your IDrive e2 remote with its Access Key, Secret Key, and endpoint.
- Add your Backblaze B2 remote using either S3-compatible or native credentials.
- Configure a one-way sync job, run a Dry Run first, then execute and verify with Job History.
A clean bucket migration comes down to verifying before and after — RcloneView's dry run and comparison tools make both steps part of the same workflow.
Related Guides:
- Manage IDrive e2 Storage — Sync and Backup Files with RcloneView
- Manage Backblaze B2 Storage — Sync and Backup Files with RcloneView
- Wasabi vs Backblaze B2 vs IDrive e2 — Object Storage Comparison
Supported Cloud Providers
