Migrate Google Drive to Backblaze B2 — Transfer Files with RcloneView
Google Drive is built for collaboration, not cold archiving — RcloneView migrates your Drive content directly to Backblaze B2 without touching your local disk, saving storage costs at scale.
Google Drive excels at real-time collaboration, but it's not designed for cost-efficient long-term archiving at scale. Backblaze B2 offers S3-compatible object storage at a fraction of Google's storage cost, making it a popular destination for archiving large datasets, video projects, and business records that don't require daily access. RcloneView handles the migration directly between both clouds — no local disk intermediary needed.
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.
Setting Up Both Remotes
In RcloneView, add Google Drive first — Remote tab > New Remote > Google Drive — and authenticate via browser OAuth. Then add Backblaze B2: select it from the provider list and enter your Application Key ID and Application Key. Both remotes become active immediately.
Open both remotes side by side in RcloneView's dual-panel explorer. This direct view is valuable for planning the migration: verify what exists in your Drive folders on the left, confirm the target B2 bucket structure on the right, and identify which folders to prioritize before starting the transfer.
Configuring the Migration Job
Open Job Manager and create a new sync or copy job. Set the source to your Google Drive folder (or a specific subfolder for incremental migration) and the destination to your Backblaze B2 bucket path.
For large migrations — a video production company moving 2 TB of completed projects from Drive to B2 — enable multi-thread transfers and increase the concurrent file count in the job's Advanced Settings. The Dry Run feature shows exactly which files will be transferred before the actual job runs, preventing accidental overwrites or skipped content. Enabling checksum verification ensures every file arrives intact on B2, which is especially critical for archiving where files may not be accessed for years.
Verification and Cleanup After Migration
Once the transfer completes, use RcloneView's Folder Compare to compare the Google Drive source against the B2 destination. The comparison view highlights left-only files (not yet migrated), right-only files (already on B2), and equal files — giving you a clear, visual checklist before removing anything from Drive.
Running the migration job a second time after comparison is safe — rclone skips files that already exist at the destination with matching size and timestamp, so only remaining differences get transferred. This idempotent behavior makes large-scale migrations reliable even across multiple sessions.
Getting Started
- Download RcloneView from rcloneview.com.
- Add a Google Drive remote (OAuth browser auth) and a Backblaze B2 remote (Application Key credentials).
- Open Job Manager and create a sync or copy job from Google Drive to B2.
- Enable Dry Run to preview, then execute — use Folder Compare to verify completion.
Migrating to Backblaze B2 with RcloneView removes cloud egress complexity and gives you a verified, cost-efficient archive without writing a single CLI command.
Related Guides:
- Migrate Backblaze B2 to Google Drive with RcloneView
- Manage Backblaze B2 Cloud Storage — Sync and Backup with RcloneView
- Backup Dropbox to Backblaze B2 — Affordable Storage with RcloneView
Supported Cloud Providers
