Migrate OpenDrive to Backblaze B2 — Transfer Files with RcloneView
Move an OpenDrive library into Backblaze B2 buckets with a previewed, verifiable cloud-to-cloud transfer instead of a manual download and re-upload.
Teams that outgrow a file-sharing account often want object storage for long-term archives. Moving data from OpenDrive to Backblaze B2 by hand means downloading everything locally first. RcloneView connects both services and transfers between them directly, with a Dry Run and a comparison step so you know what moved. Connect S3, Azure, or Backblaze B2 with full read/write on the FREE license.
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.
Connect Both Remotes
Open the Remote tab and choose New Remote. Add OpenDrive as one remote and Backblaze B2 as the other. B2 uses an Application Key ID and Application Key, which you create in the Backblaze key management page. Create the destination bucket in Backblaze first so you have a target path ready.
Once both remotes appear in Remote Manager, open them in two Explorer panels side by side. Browsing the top level of each confirms the credentials work before you commit to a large transfer.
Plan the Folder Layout
A migration is a good moment to decide how data lands in B2. A common pattern is one bucket per purpose, such as an archive bucket for finished projects, with top-level folders mirroring your current OpenDrive structure. Use Get Size on the largest OpenDrive folders to estimate volume, and copy the most important folders first.
If some file types should stay behind, Step 3 of the sync wizard lets you set max file size, max file age, or custom exclusion rules such as .iso.
Dry Run, Then Transfer
Create a job with OpenDrive as the source and your B2 bucket as the destination. For a migration, a Copy job is the safer choice because it leaves the source untouched; a Sync job can delete files on the destination to match the source. Run a Dry Run first to see the list of files that would be copied.
In Step 2, keep "Retry entire sync if fails" at its default of 3 and consider lowering concurrent transfers if the source throttles. Then run the job and watch progress, speed, and file counts in the Transferring tab.
Verify Before You Retire the Source
When the job finishes, open Job History to confirm the status is Completed and review total size and file count. Then use Compare on the OpenDrive and B2 folders. Left-only files are items that did not arrive; different files point to size mismatches worth re-copying. Keep the OpenDrive data until the comparison shows no left-only files.
Getting Started
- Download RcloneView from rcloneview.com.
- Add OpenDrive and Backblaze B2 as remotes and create the destination bucket.
- Build a Copy job, run a Dry Run, then run the transfer.
- Verify with Job History and Folder Compare before decommissioning the source.
A previewed, verified copy makes the move to B2 predictable even for large libraries.
Related Guides:
- Manage OpenDrive Storage — Sync and Backup Files with RcloneView
- Migrate SugarSync to Backblaze B2 with RcloneView
- Migrate Koofr to Backblaze B2 with RcloneView
Supported Cloud Providers
