Migrate Proton Drive to Backblaze B2 — Secure Cloud Transfer with RcloneView
Move your Proton Drive files to Backblaze B2's affordable object storage using RcloneView — no manual downloading required.
Proton Drive offers strong end-to-end encryption and privacy-first storage, making it a popular choice for sensitive personal and business data. As storage needs grow — or when you need a cost-effective secondary backup destination — migrating files to Backblaze B2 becomes a practical option. A photography studio archiving terabytes of RAW files, or a developer team consolidating cloud assets, can benefit from B2's scalable object storage alongside Proton's privacy-focused primary storage. RcloneView makes this cloud-to-cloud migration straightforward, streaming data directly between providers without downloading files to your local machine first.

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 Proton Drive and Backblaze B2
Before migrating, configure both cloud remotes in RcloneView. Start by adding your Proton Drive account: navigate to the Remote tab in the menu bar and click New Remote. Select Proton Drive from the provider list and enter your Proton account email and password. If you have two-factor authentication enabled, RcloneView will prompt for your 2FA code during setup. Proton Drive support requires rclone v1.69 or later — RcloneView's embedded rclone handles this automatically.
Next, add your Backblaze B2 remote. Click New Remote again and choose Backblaze B2. You will need your Application Key ID and Application Key, generated from the Backblaze B2 console under App Keys. Scope the key to the specific bucket you want as the migration destination, or grant account-wide access if you plan to create a new bucket during setup.
Once both remotes are configured, browse them side by side in RcloneView's dual-panel explorer. Navigate to your Proton Drive folder on one side and your B2 bucket on the other to confirm both connections are working before starting the migration.
Configuring the Migration Job
With both remotes connected, open the Job Manager from the Home tab and create a new sync or copy job. Set your Proton Drive folder as the source and your Backblaze B2 bucket as the destination. Give the job a descriptive name such as proton-to-b2-archive to distinguish it from other transfer jobs.
Before running the full migration, use the Dry Run option to preview exactly which files will be transferred. This simulation shows the complete list of files to be copied without moving any data — an essential step when migrating large libraries to catch path mapping issues early. For large Proton Drive archives, enable checksum verification in the Advanced Settings to ensure file integrity across both providers.
The concurrent transfer settings in Step 2 of the job wizard let you tune performance. Starting with 4 concurrent transfers is a reasonable default, and you can increase this once you have confirmed the migration is running smoothly.
Monitoring and Verifying the Transfer
Once you start the migration job, the Transferring tab in RcloneView's bottom panel shows real-time progress: transfer speed, files completed, total size, and remaining data. For large migrations running into tens or hundreds of gigabytes, minimize RcloneView to the system tray and let the transfer run in the background while jobs continue uninterrupted.
After the migration completes, check the Job History tab to confirm transfer status, total files moved, and any errors. If the job reports errors for specific files, the log view provides exact error messages to identify whether the issue is a permission problem, a network timeout, or a filename encoding conflict.
Scheduling Ongoing Backups
For users who want Backblaze B2 as a continuous backup destination for their Proton Drive data, RcloneView PLUS supports crontab-style scheduling. After the initial migration is complete, edit the job and navigate to Step 4 (Scheduling) to configure a recurring sync — for example, nightly at 2 AM. The scheduled job will run automatically, copying only new or changed files since the last run, keeping your B2 archive current without manual intervention.
Getting Started
- Download RcloneView from rcloneview.com.
- Add your Proton Drive remote via Remote tab > New Remote, entering your email and password.
- Add your Backblaze B2 remote using your Application Key ID and Application Key from the B2 console.
- Create a sync or copy job in Job Manager with Proton Drive as source and your B2 bucket as destination.
- Run a Dry Run to preview the migration, then execute the full transfer and monitor progress in the Transferring tab.
With RcloneView handling the connection between Proton Drive and Backblaze B2, you can build a reliable cross-cloud backup strategy that pairs Proton's privacy with B2's cost-effective storage capacity.
Related Guides:
- Migrate Proton Drive to Google Drive — Transfer Files with RcloneView
- Migrate Dropbox to Proton Drive — Cloud Transfer with RcloneView
- Migrate Google Drive to Backblaze B2 — Cloud Transfer with RcloneView