Google Cloud Storage migrations,
without scripts.
Mover is the data-migration tool from Files.com. One-time moves between 20+ providers — no subscriptions, no surprises, no scripts.
Migrate data to or from Google Cloud Storage with Mover — fast, simple, and at a fraction of what other migration tools charge.
GCSWhere GCS migrations come from. Where they go.
Inbound: somebody picked BigQuery or Vertex AI and pulled the data over to sit next to it. Outbound: the egress bill caught up. Hundreds of GCS migrations later, those two patterns cover most of them.
Standardizing on Google Cloud for analytics and AI
Teams building on BigQuery, Vertex AI, Dataflow, or GKE pull data into GCS to keep it next to the analytics, ML, and compute layer they already use.
Multi-region durability without complexity
GCS Multi-Region and Dual-Region storage classes replicate data across geographies automatically. Customers with availability requirements often end up on GCS for the geography model.
Consolidating into one Google Workspace tenant
Organizations that already run on Google Workspace move file workloads into GCS to align identity, billing, and compliance with the tools their teams use every day.
Cost arbitrage to Wasabi or Backblaze B2
GCS egress is the most expensive of the three hyperscalers — roughly $0.12/GB at the starting tier. Both Wasabi and Backblaze run a fraction of GCS Standard at rest and charge zero egress. For read-heavy workloads, the round-trip can pay for itself in months.
Multi-cloud rebalance to AWS or Azure
Moving primary storage to align with an AWS-first or Azure-first compute stack.
Cross-project or cross-region reorg
Project splits, region migrations, or compliance-driven moves between GCS buckets.
Pair GCS with any cloud.
GCS migrations rarely happen in isolation. These are the providers we pair with most often — one-click setup on either side, same dry-run flow, same audit trail.
How Mover connects.
Mover supports 2 standard Google authentication methods. Pick the one that matches how your team manages credentials.
Service account JSON key
Standard for accounts you control. Create a service account in Google Cloud, grant it Storage Object Admin (or narrower) on the buckets you're migrating, and paste the JSON key into Mover.
HMAC key
Useful when your existing tooling already uses GCS via its S3-compatible interoperability layer. Mover accepts HMAC access keys generated in the Google Cloud Console.
See your twelve-month savings.
Move from a paid-egress provider to one with free egress and your monthly invoice shrinks. Plug in your data size and how much you read from storage each month — the calculator does the rest, including the one-time Mover migration cost.
Current cost on Google Cloud Storage
per month
$410
New cost on Wasabi
per month
$35
Monthly savings
recurring
$374
One-time Mover migration
1× 5 TB + 1× 100 GB
$848
12-month savings
$4,491
Before subtracting the one-time migration cost.
Payback period
2.3 mo
$848 migration ÷ monthly savings.
Net savings, year one
$3,643
Numbers use published standard-tier rates from each provider as of May 2026. Actual invoice varies by region, committed-use discounts, and your specific contract. Mover migration cost uses the cheapest combination of prepaid usage packs that covers the data size — packs stack, so a 2 TB migration is two 1 TB packs, not one 5 TB pack. The dry run prices the migration against your actual data and shows the exact one-time Mover cost before you commit.
4 steps to Go.
From credential to first byte in four clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect GCS.
Paste a service account JSON key or an HMAC access key. Mover validates the credential and lists buckets it can see.
Choose source and destination buckets.
Apply filters and a date range if you want a partial migration.
Run a dry-run.
Mover walks the source bucket, counts files, sizes the transfer, and produces an exact cost estimate — Mover fees + GCS egress.
Launch.
Live progress, automatic retries on transient failures. Pause, resume, or cancel at any time.
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Run a dry run before you buy anything. Mover connects to Google Cloud Storage, walks it, counts every file, sums the bytes, and returns an exact file count and price before a single byte moves — with nothing charged. The dry run is always free, and you can re-run it as often as you want as you scope the migration.
A service account JSON key, or an HMAC key generated in the Google Cloud Console. Service account keys are the standard path; HMAC keys are useful when your existing tooling already uses GCS via the S3-compatible interoperability layer.
Mover charges as low as $0.15/GB when purchasing a 10 TB pack. Google charges egress separately — roughly $0.12/GB for the first 1 TB, dropping to $0.08/GB at higher volumes. For a 10 TB migration, expect ~$1,499 in Mover fees and roughly $860 in GCS egress. Migrating into GCS is free on the Google side; only Mover fees apply.
GCS inbound is free. You pay Mover fees plus any egress your source provider charges.
Yes. Generate a service account key for each side, or use a single service account with permissions on both projects' buckets.
Yes. Cross-region and storage-class changes incur their own Google-side charges; those costs appear in Mover's dry-run estimate before you commit.
Start the move. finish.
Run a free dry run on your Google Cloud Storage data. See the exact size, file count, and price before you commit a single GB.