Skip to content

Articles

How to Migrate from Google Drive to Backblaze B2

Migrate Google Drive files to Backblaze B2 with Blober

Why Move from Google Drive to Backblaze B2?

Section titled "Why Move from Google Drive to Backblaze B2?"

Google Drive is a collaboration tool with storage built in. Backblaze B2 is pure storage built for scale. The reasons people move between them usually come down to one or more of these:

  • Cost. Google One charges $100/year for 2 TB. Backblaze B2 charges $6.95/TB/month, but for archival or backup data you access rarely, the math works differently. If you are storing 5+ TB of media, raw footage, or project archives, B2 can be significantly cheaper depending on your access patterns.
  • Control. B2 gives you S3-compatible API access, which means you can integrate it with backup tools, CDNs, media workflows, and custom applications. Google Drive's API is more limited for bulk operations.
  • Redundancy. Keeping a copy of your Google Drive data in B2 means you are not dependent on a single provider. If Google changes pricing, restricts your account, or has an outage, your files are safe elsewhere.

Google Drive stores native files (Docs, Sheets, Slides) as cloud-only application states, not as downloadable files. When you need them outside of Google, they must be converted to Office formats first.

Google Takeout can export your Drive, but it takes hours, produces fragmented zip archives, and flattens your folder structure. For a migration to B2 specifically, Takeout is especially awkward because you would need to download everything locally, extract it, then upload it to B2 using a separate tool.

Blober connects to both Google Drive and Backblaze B2. It handles the tricky parts automatically:

  • Google Docs become .docx files during transfer
  • Google Sheets become .xlsx files during transfer
  • Google Slides become .pptx files during transfer
  • Regular files (photos, videos, PDFs) transfer as-is
  • Folder structure is preserved in your B2 bucket
  • Shared files are accessible through a "Shared with me" virtual folder
  1. Connect Google Drive: Add Google Drive as a provider in Blober. OAuth login through your browser.
  2. Connect Backblaze B2: Add B2 with your Application Key ID and Application Key. Blober auto-detects your bucket regions.
  3. Create a workflow: Set Google Drive as source, B2 as destination. Browse and select files or folders.
  4. Run: Blober streams files from Google Drive to B2 through your machine. No local storage needed for intermediate files.
Google One (2 TB)Backblaze B2 (2 TB)
Monthly$8.33~$14
Annual$100~$167
5 TB$25/month (Google One Premium)~$35/month
10 TB+Not available on consumer plans~$70/month
EgressFree (via Drive sync/download)Free up to 3x stored

For small amounts of active data, Google Drive is the better deal. For large archives, backups, and media libraries that you rarely access, B2's pay-for-what-you-use model wins.

Many people do not fully leave Google Drive. Instead, they keep it for active collaboration (shared documents, team folders) and move everything else to B2:

  • Current projects stay in Google Drive for real-time editing
  • Completed projects, old photos, and archives go to Backblaze B2
  • Blober handles the transfer once, then you adjust your Google storage plan

This hybrid approach gives you the best of both: Google's collaboration features for active work and B2's affordable storage for everything else.

One-time purchase. No subscription, no per-GB fees.

Download Blober at blober.io

How to Migrate Google Drive Files to AWS S3

Migrate Google Drive files to AWS S3 with Blober

Google Drive works great as a collaboration tool. Real-time editing, sharing links, 15 GB free storage. But when your data grows past a few hundred gigabytes, or when you need programmatic access, versioning policies, or storage tiering, Google Drive starts showing its limits.

AWS S3 is built for exactly those use cases. It handles petabytes, offers multiple storage classes, integrates with hundreds of AWS services, and gives you full API control. The gap between Google Drive and S3 is not about which is "better." It is about what each one is built for.

Moving from one to the other is where things get complicated.

Google Drive stores some files as native Google formats: Google Docs, Google Sheets, Google Slides. These are not actual files on disk. They are application states stored in Google's cloud. You cannot download a "Google Doc file" the way you download a PDF.

When you export from Google Drive (or use Google Takeout), these files get converted to their Microsoft Office equivalents: DOCX, XLSX, PPTX. But this conversion is often inconsistent with Takeout, and the folder structure gets flattened.

How Blober Handles Google Drive to S3

Section titled "How Blober Handles Google Drive to S3"

Blober connects to Google Drive via OAuth and to AWS S3 via access keys. It solves the two biggest pain points of this migration:

When Blober encounters a Google Doc, Sheet, or Slide, it automatically converts it to the corresponding Office format (DOCX, XLSX, PPTX) during transfer. This happens on the fly. You do not need to manually export anything.

The converted files land in your S3 bucket in a usable format that any application can read.

Blober recreates your Google Drive folder hierarchy in S3. If you have Work/Projects/2025/Proposal.docx in Google Drive, it becomes Work/Projects/2025/Proposal.docx in your S3 bucket. No flat dumps, no reorganization needed.

Google Drive has a "Shared with me" section that is separate from your main drive. Blober shows this as a browsable folder, so you can include shared files in your migration if needed.

  1. Connect Google Drive: Add Google Drive as a provider. Blober opens a browser window for OAuth authorization. Sign in and grant access.
  2. Connect AWS S3: Add S3 with your Access Key ID, Secret Access Key, and region.
  3. Create a workflow: Set Google Drive as source, S3 as destination. Browse your Drive, select files and folders.
  4. Choose S3 options: Pick the storage class (Standard, Intelligent-Tiering, Standard-IA, Glacier, etc.) and target bucket.
  5. Run: Blober transfers with progress tracking and auto-resume.

One advantage of moving to S3 is choosing the right storage class for your data:

Storage ClassUse CaseCost (per TB/mo)
StandardFrequently accessed files~$23
Intelligent-TieringUnknown access patterns~$23 (auto-optimizes)
Standard-IAInfrequent access, fast retrieval~$12.50
Glacier InstantArchive with instant access~$4
Glacier Deep ArchiveLong-term cold storage~$1

With Blober, you set the storage class when creating the workflow. All transferred files land on the tier you choose. If you want different tiers for different data, create multiple workflows.

  • Startups growing out of Google Workspace who need infrastructure-grade storage
  • Data teams that need to run analytics on files currently in Google Drive
  • Companies consolidating storage to AWS for compliance or integration reasons
  • Developers who want S3's API and event-driven architecture instead of Google Drive's sync model

One-time purchase. No per-GB fees, no subscription.

Download Blober at blober.io

How to Move Data from Azure Blob Storage to Cloudflare R2

Move data from Azure Blob Storage to Cloudflare R2 with Blober

Azure Blob Storage charges $0.087 per GB for data leaving their network. If you serve 1 TB of files per month to users or external systems, that is $87/month in egress alone, on top of storage costs.

Cloudflare R2 charges $0 for egress. Zero. Nothing. You pay for storage ($0.015/GB/month) and operations, but downloading data from R2 is free. For applications that serve files to users, APIs, CDNs, or other services, switching to R2 can cut your cloud bill significantly.

The most common reason is cost. If your Azure Blob account is mostly used for serving static assets, media files, backups that get restored frequently, or API responses, the egress fees can dwarf your storage costs. R2 removes that variable entirely.

Another reason is simplicity. R2 is S3-compatible, meaning any tool or SDK that works with S3 works with R2. If your application already uses the S3 API (many do, even on Azure), the migration is mostly about moving data and updating the endpoint.

Blober supports both Azure Blob Storage and Cloudflare R2 as native providers. The transfer works like any other Blober workflow: connect both accounts, select files, run.

Step 1: Connect Azure Blob Storage

Section titled "Step 1: Connect Azure Blob Storage"

Add Azure Blob as a provider with your connection string. Blober lists your containers and their contents.

Add Cloudflare R2 as a provider. You will need your Account ID along with an S3-compatible Access Key ID and Secret Access Key from the Cloudflare dashboard. If you also provide a Cloudflare API token, Blober can list your buckets through Cloudflare's native API with server-side pagination, which is more efficient for accounts with many buckets.

Set Azure Blob as the source and Cloudflare R2 as the destination. Browse your Azure containers, select the files or containers you want to migrate, and choose the destination bucket in R2.

Blober streams data from Azure through your machine to R2. It uses parallel uploads on both ends, so large files move efficiently. If the transfer is interrupted, Blober resumes from where it stopped.

What About Azure Egress Fees During Migration?

Section titled "What About Azure Egress Fees During Migration?"

This is the unavoidable part. Moving data out of Azure means paying egress. For the initial migration, you will pay $0.087/GB to get your data from Azure to your machine (where Blober runs), and from there to R2.

For 1 TB, that is about $87 in egress fees. That is a one-time cost. After the migration, your ongoing egress from R2 is $0.

If you were paying $87/month in Azure egress, the migration pays for itself in the first month.

Data SizeAzure Egress Cost (one-time)Monthly Savings on R2
500 GB~$43Depends on egress pattern
1 TB~$87Up to $87/month
5 TB~$435Up to $435/month
10 TB~$870Up to $870/month

This matters because your application code likely uses the AWS SDK or an S3-compatible client. After migrating data to R2, updating your app is often as simple as changing the endpoint URL and credentials. No SDK changes, no API rewrites.

Blober connects to R2 using the same S3 protocol, so the transfer is seamless.

When Azure Is Still the Right Choice

Section titled "When Azure Is Still the Right Choice"

R2 is excellent for serving files and eliminating egress. But Azure has features that R2 does not:

  • Storage tiers (Hot, Cool, Cold, Archive) for lifecycle cost optimization
  • Geo-redundant replication built into the platform
  • Azure Functions and event triggers tied to blob operations
  • Enterprise compliance certifications that some industries require

If you need those features, Azure is worth the egress premium. Many teams keep some data on Azure (for processing and compliance) and move the served/public data to R2 (for cost savings).

One-time purchase. Transfer as much data as you need.

Download Blober at blober.io

How to Move Files from Dropbox to Backblaze B2

Move files from Dropbox to Backblaze B2 with Blober

Why People Leave Dropbox for Backblaze B2

Section titled "Why People Leave Dropbox for Backblaze B2"

Dropbox works well as a file sync tool. You drop files in a folder and they show up on all your devices. But as your data grows, Dropbox gets expensive. The Plus plan costs $120/year for 2 TB. If you have 5 TB or more, you need Dropbox Business at $180/year per user.

Backblaze B2 charges $6.95 per TB per month for storage. For 2 TB, that is about $14/month or $167/year. But here is where it gets interesting: most of the data sitting in Dropbox is not being actively synced. It is old projects, archives, backups, photos from three years ago. That data does not need instant sync to every device. It needs to be stored cheaply and retrieved when needed.

For archival and backup storage, Backblaze B2 is significantly cheaper. And unlike Dropbox, you only pay for what you use. No fixed plans, no storage ceilings.

The Problem with Moving Data Out of Dropbox

Section titled "The Problem with Moving Data Out of Dropbox"

The obvious approach is to download everything from Dropbox to your computer, then upload it to Backblaze B2. This works for small amounts of data. For 500 GB or more, it becomes painful:

  • You need enough free space on your local disk to hold the download
  • Downloading takes hours or days depending on your connection
  • Uploading to B2 takes equally long
  • If anything fails midway, you start over

Some people try rclone for this. rclone works, but you need to configure both remotes in a text file, understand the command syntax, and handle errors yourself. If you are comfortable with the terminal, rclone is a solid choice. If you are not, it is a wall.

Blober connects to both Dropbox and Backblaze B2. You set up both providers, select the files you want to move, and Blober handles the transfer. Files stream from Dropbox through your computer to Backblaze B2 without needing to store them locally.

Add Dropbox as a provider in Blober. Click the OAuth login button and authorize Blober with your Dropbox account. Blober stores your credentials locally on your machine, not on any server.

Add Backblaze B2 as a provider. You will need your Application Key ID and Application Key from the Backblaze dashboard. Blober verifies the connection and lists your buckets.

Create a new workflow with Dropbox as the source and Backblaze B2 as the destination. Browse your Dropbox files, select what you want to transfer, and choose which B2 bucket to send it to.

Click run. Blober transfers files with parallel uploads, progress tracking, and automatic resume if your connection drops.

Blober preserves your folder structure. If you have Projects/2024/Client-A/ in Dropbox, it creates the same path in your B2 bucket. You do not end up with a flat pile of files.

Dropbox PlusBackblaze B2 (2 TB)
Monthly cost$10/month~$14/month
5 TBNeed Business plan ($15/user/mo)~$35/month
10 TBNeed Business plan~$70/month
EgressFree (sync)Free to Cloudflare partners, $0.01/GB otherwise
API accessOAuthS3-compatible

For pure storage (not sync), B2 wins at every tier above 2 TB. And if you pair B2 with Cloudflare CDN through the Bandwidth Alliance, egress is free.

This is not about abandoning Dropbox entirely. Dropbox is great for active files you need on every device. The move that makes sense for most people is:

  • Keep Dropbox for current projects and actively used files
  • Move archives, old projects, and large media to Backblaze B2
  • Use Blober to transfer the archival data once, then cancel the upgraded Dropbox plan

Blober is a one-time purchase. No subscription, no per-GB transfer fees.

Download Blober at blober.io

How to Move Files from Dropbox to Google Drive

Move files from Dropbox to Google Drive with Blober

Move Dropbox to Google Drive Without Filling Your Disk

Section titled "Move Dropbox to Google Drive Without Filling Your Disk"

The problem: there is no built-in transfer between Dropbox and Google Drive. The manual route makes you download your entire Dropbox to your computer, then upload all of it to Drive. That needs free disk space equal to your whole library and sends every file over the network twice.

The short answer: you have three realistic options. Drag and drop through the desktop apps, upload through the browser, or run a direct cloud-to-cloud transfer with Blober that streams each file from Dropbox to Google Drive without saving it to your disk. Here is how they compare.

MethodLocal disk neededSpeedFolder structureBest for
Manual (desktop sync, then drag)Full library sizeSlow: download, then uploadYou may have to rebuild itA single small folder
Browser uploadEnough to download firstSlowPreserved if you recreate foldersA few gigabytes
Blober (direct)None, files stream through memoryAbout half the time, single passPreserved automaticallyWhole-account moves and large libraries

People switch from Dropbox to Google Drive for a few common reasons:

  • Their company standardized on Google Workspace and needs everything in Drive
  • Google One pricing is more competitive for their storage needs (2 TB for $100/year vs Dropbox Plus at $120/year)
  • They want the Google Docs, Sheets, and Slides collaboration features
  • They are consolidating everything under one Google account

The actual move is where friction shows up.

Without a migration tool, moving from Dropbox to Google Drive looks like this:

  1. Install the Dropbox desktop client
  2. Wait for all files to sync to your computer
  3. Drag those files into your Google Drive folder (if using the desktop client) or upload them through the browser
  4. Wait for everything to upload
  5. Verify nothing was missed

This requires enough local disk space to hold your entire Dropbox. If you have 500 GB in Dropbox and a 256 GB laptop, you are stuck.

Even with enough space, the process is slow. You are downloading everything from Dropbox's servers to your local disk, then uploading everything from your local disk to Google's servers. That is double the transfer time.

Blober connects to both Dropbox and Google Drive. Files stream from Dropbox through your computer to Google Drive without being stored on your local disk. You need just enough memory to buffer the current file being transferred, not enough disk space for your entire library.

  • No disk space worries. A 1 TB Dropbox migrates to Google Drive even on a laptop with 128 GB of storage.
  • Half the network time. Instead of download + upload (two trips), Blober streams the data through in a single pass. The download from Dropbox and upload to Google Drive happen simultaneously.
  • Folder structure preserved. Your Dropbox folder hierarchy recreates exactly in Google Drive.
  1. Connect Dropbox: OAuth login in your browser. Blober supports both long-term OAuth tokens (with refresh) and direct access tokens.
  2. Connect Google Drive: OAuth login in your browser. Blober accesses your Drive files.
  3. Browse and select: Navigate your Dropbox in Blober's file browser. Select specific folders or your entire Dropbox.
  4. Create a workflow: Set Dropbox as source, Google Drive as destination.
  5. Run: Blober transfers with auto-resume and progress tracking.

Moving your whole Dropbox? Blober streams it straight into Google Drive without filling your laptop. Download Blober, connect both accounts, and start the transfer.

Dropbox is one of the providers where Blober supports native copy and move operations. This means:

  • Copy duplicates files within Dropbox without re-downloading them
  • Move relocates files within Dropbox without a round-trip transfer

For the cross-cloud transfer to Google Drive, files stream through your machine as described above. But if you also need to reorganize files within Dropbox before or after the migration, Blober handles that natively.

Once your files are in Google Drive:

  • They are accessible from any device with a Google account
  • Google automatically indexes content for search
  • Office files (DOCX, XLSX, PPTX) can be edited natively in Google Docs/Sheets/Slides
  • Files sync across devices via the Google Drive desktop app

You can keep Dropbox installed alongside Google Drive if you need a transition period. Once you verify everything transferred correctly, you can downgrade or cancel Dropbox.

Can I transfer files from Dropbox to Google Drive without downloading them first? Yes. Blober streams each file directly from Dropbox to Google Drive through your computer. Nothing is saved to your local disk, so you do not need free space equal to your library size.

Does Blober preserve my Dropbox folder structure in Google Drive? Yes. Your Dropbox folder hierarchy is recreated exactly in Google Drive, including nested folders.

How long does a Dropbox to Google Drive migration take? It depends on how much data you have and your upload speed. Because Blober downloads and uploads in a single pass instead of two separate trips, it finishes in roughly half the time of a manual download-then-upload.

Can I sync Dropbox to Google Drive automatically? Blober moves and copies files on demand through workflows that you start when you need them. You can re-run a workflow at any time to move newly added files. It is built for migrations and repeat transfers rather than always-on background sync.

Can I move from Dropbox to Google Workspace or a Shared Drive? Yes. Google Workspace accounts and Shared Drives appear in Blober once you connect Google Drive, so you can set either as the destination.

Most cloud-to-cloud services bill per gigabyte or charge a monthly fee for as long as you keep them. Blober is a one-time purchase. Moving 50 GB costs the same as moving 5 TB, and there is nothing to cancel once the migration is done. For a one-off move from Dropbox to Google Drive, that is the difference between paying once and renting a tool for a weekend.

Move your Dropbox into Google Drive without filling your disk or paying per gigabyte. One-time purchase, no subscription, no per-GB fees.

Download Blober at blober.io