Migrate Cloudflare R2 to Google Drive — Transfer Files with RcloneView
Move files from a Cloudflare R2 bucket to Google Drive using RcloneView's visual interface — no CLI required, no egress fees from R2.
Cloudflare R2 is popular with developers for its zero-egress object storage, but teams often need to move data into Google Drive for sharing with non-technical colleagues, integrating with Google Workspace, or consolidating storage accounts. RcloneView connects both services through a point-and-click workflow, so you can migrate R2 buckets to Google Drive without writing a single command.
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 Cloudflare R2 and Google Drive
Start by adding both services as remotes. In the Remote tab, click New Remote and select Cloudflare R2. You will need your Cloudflare API Token, Account ID, and Endpoint URL (in the format https://<account-id>.r2.cloudflarestorage.com). RcloneView uses rclone's S3-compatible backend for R2, so your R2 API token maps directly to the Access Key and Secret Key fields.
Next, add Google Drive as a second remote. RcloneView opens a browser window for OAuth authentication — sign in to your Google account and grant access. No API key entry is required.
Once both remotes are configured, you can browse your R2 buckets and Google Drive folders side by side in RcloneView's dual-panel explorer.
Running the Migration
Click Sync in the Home tab to launch the 4-step job wizard. In Step 1, select your R2 bucket (or a specific subfolder within it) as the source, and a Google Drive folder as the destination. Name the job clearly — something like r2-to-gdrive-migration helps when reviewing history later.
In Step 2, enable checksum verification to confirm file integrity after each transfer. This is particularly important for large files like videos or archives, where corruption during transfer would otherwise go undetected. Set the retry count to at least 3 to handle temporary network interruptions automatically.
Before committing, run a Dry Run to preview exactly which files will be copied. This shows the full transfer list and file sizes, letting you confirm scope before anything touches your Google Drive.
Filtering and Handling Large Transfers
If your R2 bucket contains a mix of file types, Step 3 lets you apply filters. A design team migrating a project bucket might exclude raw .psd files over 500 MB while keeping all web-ready exports, using the Max File Size filter. The Max File Age filter is equally useful for incremental migrations — moving only files modified in the last 30 days rather than an entire historical dataset.
For large migrations spanning hours, the Job History tab records each execution's speed, file count, and completion status. If the job is interrupted mid-way, re-running it is safe — RcloneView skips files already transferred successfully and continues from where it left off.
Getting Started
- Download RcloneView from rcloneview.com.
- Add Cloudflare R2 as a remote using your API Token, Account ID, and Endpoint URL.
- Add Google Drive as a remote via OAuth browser login.
- Create a Copy or Sync job from your R2 bucket to a Google Drive folder — run a Dry Run first to confirm scope.
Cloudflare R2's zero-egress model means moving your data out costs nothing on the R2 side, and RcloneView handles the rest visually.
Related Guides:
- Migrate Google Drive to Cloudflare R2 with RcloneView
- Manage Cloudflare R2 — Sync and Backup with RcloneView
- Manage Google Drive — Sync and Backup Files with RcloneView
Supported Cloud Providers
