Amazon S3 to Google Cloud Storage,
across clouds, without the bespoke pipeline.
The cross-cloud move toward Google Cloud. Teams shifting workloads onto BigQuery, Vertex AI, or GKE colocate their storage on GCS so analytics and compute don't pay egress on every query.
Mover handles S3 → GCS end to end. Authorize an S3 access key, authorize a GCS HMAC key or service-account credential, see the price before a single byte moves.
From
Amazon S3
To
GCS
The cross-cloud move
Why teams move from S3 to GCS
Most S3 → GCS migrations are about colocation with Google Cloud compute or analytics. Once BigQuery, Vertex, or GKE is the primary workload, paying AWS egress on every read becomes the line item ending the relationship.
Colocating storage with BigQuery and Vertex AI
Analytics and ML workloads on Google Cloud read storage hot and often. Keeping the data on S3 means paying AWS egress on every query; landing it on GCS ends that line item and unlocks features like BigQuery's direct GCS table reads.
Standardizing on Google Cloud as primary
Strategic shift to GCP — often paired with an enterprise agreement, Anthos / GKE adoption, or a Workspace tenancy — that has to bring the existing S3 estate along.
Compliance or sovereignty alignment
Data residency, regulatory, or contractual constraints that map cleanly onto Google Cloud regions. Moving the data is what makes the policy real.
Ending an AWS engagement
Sunsetting an AWS account, ending a vendor relationship, or finishing a project hosted on AWS — the data lands on GCS as part of the wind-down so nothing is stranded.
Getting started
4 steps to Go.
From credential to first byte in a handful of clicks. The dry-run is free, every time, and shows the exact cost before you commit a byte.
Connect Amazon S3.
Provide an IAM access key with read on the source bucket. Mover supports scoped, least-privilege credentials.
Connect Google Cloud Storage.
Provide a GCS HMAC key or service-account credential with write access to the destination bucket. Mover supports both authentication flows.
Run a free dry run.
Mover walks the S3 source, sums bytes, and produces an exact-cost estimate that includes Mover fees and AWS egress. The dry run is free, every time.
Launch the migration.
Live progress, multipart parallelism, automatic retries on transient failures, structured audit log of every object moved.
The price
The pricing math, honestly.
S3 charges egress (typically $0.09/GB at standard rates). GCS does not charge for ingress. The line items are Mover (as low as $0.15/GB on a 10 TB pack) and AWS egress. The dry run shows both numbers at the dollar.
Pricing example
10 TB S3 → GCS migration
AWS egress varies by region and committed-use discounts. The dry run shows the exact AWS-side cost for your data.
Common Questions
Frequently asked.
Most teams launch their first migration in under 15 minutes. The dry run is free, every time.
Mover migrates the current version of each object by default. Versioned migrations — pulling every historical version — are supported on request and multiply the byte count, so the dry run is the right place to confirm scope.
Move S3 to GCS with the price up front.
Connect both sides, run a free dry run, see the exact cost — including AWS egress. Launch when you are ready.