Skip to main content

Migrate Google Drive to Storj — Transfer Files with RcloneView

· 4 min read
Jay
Tech Writer

Move your entire Google Drive to Storj's decentralized, end-to-end encrypted storage without writing a single command.

Teams storing sensitive project files in Google Drive often reach a point where they want stronger data sovereignty, lower egress costs, or S3-compatible access for their toolchain. Storj distributes file chunks across independent nodes worldwide, delivering end-to-end encryption and geographic redundancy by design. RcloneView makes this migration straightforward: connect both remotes through a browser-authenticated setup, then run a copy job that transfers files from Google Drive to Storj through your local machine.

RcloneView app preview

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
WindowsmacOSLinux
Get Started Free →

Free core features. Plus automations available.

Connect Google Drive and Storj as Remotes

Before transferring anything, both cloud accounts need to be registered in RcloneView as remotes. Google Drive uses OAuth browser authentication — open the Remote tab, click New Remote, select Google Drive, and RcloneView launches a browser window for you to authorize the connection. No API keys or credentials to manage manually.

Storj uses S3-compatible access. In RcloneView's New Remote wizard, select the S3 provider type and choose Storj as the S3 provider. Enter your Storj Access Key ID, Secret Access Key, and the Storj S3 gateway endpoint. Once saved, the remote appears in the explorer panel, giving you a familiar file-browser view of your Storj buckets.

Adding Google Drive and Storj as remotes in RcloneView

With both remotes registered, you can open them side by side in RcloneView's dual-panel explorer. Drag a folder from the left panel (Google Drive) to the right panel (Storj) for a quick one-off copy, or set up a managed job for larger migrations.

Configure the Migration Job

For migrating a full Google Drive — a design agency with 300 GB of assets or a research team with years of shared documents — using a Job is the right approach. Click Job Manager in the Home tab, then Add Job. Set the source to your Google Drive remote and folder, and the destination to your Storj bucket. Choose Copy as the job type to transfer all source files without deleting originals from Google Drive.

In Step 2 (Advanced Settings), set the number of concurrent file transfers based on your connection. The default multi-thread transfer count of 4 works well for most internet connections. Enable checksum verification to ensure file integrity — RcloneView compares checksums after each transfer, catching any corruption introduced during transit.

Configuring a Google Drive to Storj copy job in RcloneView

Step 3 lets you add filtering rules if you only want to migrate specific file types — for example, exclude .tmp working files or limit the transfer to files younger than a certain age. This is particularly useful when migrating an active workspace where some temporary files shouldn't follow you to the new storage provider.

Monitor and Verify the Transfer

Once you click Run, the Transferring tab at the bottom of RcloneView shows live progress: transfer speed, file count, and total size moved. For large migrations, RcloneView continues the job in the background even if you navigate to other remotes — and if the transfer is interrupted, setting the retry count in Step 2 ensures it picks up where it left off.

Running the Google Drive to Storj migration job in RcloneView

After the job completes, use RcloneView's Folder Compare feature (Home tab > Compare) to verify that both sides match. Point the left panel at your Google Drive source and the right panel at your Storj destination. Folder Compare will surface any files that exist only on one side or have different sizes, giving you a clear audit trail before you begin winding down the Google Drive workspace.

Job history showing completed Google Drive to Storj migration

Getting Started

  1. Download RcloneView from rcloneview.com.
  2. Add your Google Drive remote via Remote tab > New Remote and complete the OAuth browser login.
  3. Add your Storj remote using the S3 provider type with your Storj Access Key, Secret Key, and gateway endpoint.
  4. Open Job Manager, create a Copy job from your Google Drive folder to your Storj bucket, enable checksum in Step 2, and click Run.

Storj's architecture gives your files geographic distribution and end-to-end encryption by default — RcloneView makes reaching that destination a matter of minutes, not hours of scripting.


Related Guides:

Supported Cloud Providers

Local Files
WebDAV
FTP
SFTP
HTTP
SMB / CIFS
Google Drive
Google Photos
Google Cloud Storage
OneDrive
Dropbox
Box
MS Azure Blob
MS File Storage
S3 Compatible
Amazon S3
pCloud
Wasabi
Mega
Backblaze B2
Cloudflare R2
Alibaba OSS
Ceph
Swift (OpenStack)
IBM Cloud Object Storage
Oracle Cloud Object Storage
IDrive e2
MinIO
Storj
DigitalOcean Spaces