Storage Transfer Service

Name: Storage Transfer Service
Brand: Google
Rating: 4.2 (17 reviews)

Storage Transfer Service is a managed data-movement service that transfers data into, out of, and within Google Cloud Storage across cloud-to-cloud, bucket-to-bucket, on-prem file-system agents, and bulk HTTP/HTTPS ingestion while providing centralized scheduling, retries, and monitoring.

Est 1998|Valuation $4081.3B|Raised $26.1M

LinkedIn 41.9M|Website|Web traffic 3.3M|FTEs 198,933|HQ Mountain View, California, US

01Competitive Landscape

| Aspect | Storage Transfer Service (Google) | AWS DataSync | Azure Data Box (and Data Box Gateway) | |--------|----------------------------------|--------------|--------------------------------------| | Starting Price | No published STS licensing fee for agentless transfers; agent-based file transfers billed at published per-GB transfer rates; private network transfers incur published regional per-GB transfer rates | DataSync service pricing is published by AWS; total cost also includes standard request, storage, and data transfer rates on involved AWS services | Device/order fees plus usage and shipping; published pricing often requires a calculator or sign-in for exact figures | | Recommended For | Moving data into GCS from S3/Azure/on-prem/file systems; scheduled batch transfers; centralized job management | Moving data into/within AWS storage services; hybrid NAS to AWS patterns | Cases where network transfer is impractical and physical shipment of data is acceptable; very large offline moves | | Key Strength | Managed transfers; private network options via interconnect; integration with GCS and Google IAM controls | Tight AWS storage integration and broad AWS ecosystem fit | Offline transfer with encrypted devices; avoids prolonged WAN transfers | | Key Weakness | Not a general any-to-any mover; periodic scan cadence for some sources; IAM/service-agent complexity; operational overhead for agents | Destination lock-in potential; still subject to source egress and request/storage costs | Logistics lead time and device handling; not real-time | - STS vs AWS DataSync - AWS DataSync pricing highlights that standard request, storage, and data transfer rates on AWS services accessed during copy may apply in addition to DataSync charges; this mirrors the "tool + underlying operations" cost structure seen with STS. - If the strategic destination is GCS, STS provides native integration. If the destination is AWS storage (S3/EFS/FSx), DataSync is generally the native alternative. - STS vs Azure approaches - Azure Data Box is focused on encrypted physical devices for offline ingestion and is an alternative when network-based transfer is impractical. - Azure Data Factory's Copy activity is closer to ETL/orchestration and may be selected when transformations or orchestration are required rather than pure storage migration. - Egress economics - Cross-cloud migration decisions are often governed by egress fees and request/operation costs at the source cloud; special commercial arrangements or credits can affect ROI calculations and should be considered in procurement discussions. - Market adoption trends - No credible public market-share numbers for STS were found in this research pass. - Frequent documentation updates and release notes in recent periods indicate active product development.

01Competitive Landscape

Aspect	Storage Transfer Service (Google)	AWS DataSync	Azure Data Box (and Data Box Gateway)
Starting Price	No published STS licensing fee for agentless transfers; agent-based file transfers billed at published per-GB transfer rates; private network transfers incur published regional per-GB transfer rates	DataSync service pricing is published by AWS; total cost also includes standard request, storage, and data transfer rates on involved AWS services	Device/order fees plus usage and shipping; published pricing often requires a calculator or sign-in for exact figures
Recommended For	Moving data into GCS from S3/Azure/on-prem/file systems; scheduled batch transfers; centralized job management	Moving data into/within AWS storage services; hybrid NAS to AWS patterns	Cases where network transfer is impractical and physical shipment of data is acceptable; very large offline moves
Key Strength	Managed transfers; private network options via interconnect; integration with GCS and Google IAM controls	Tight AWS storage integration and broad AWS ecosystem fit	Offline transfer with encrypted devices; avoids prolonged WAN transfers
Key Weakness	Not a general any-to-any mover; periodic scan cadence for some sources; IAM/service-agent complexity; operational overhead for agents	Destination lock-in potential; still subject to source egress and request/storage costs	Logistics lead time and device handling; not real-time

STS vs AWS DataSync
- AWS DataSync pricing highlights that standard request, storage, and data transfer rates on AWS services accessed during copy may apply in addition to DataSync charges; this mirrors the "tool + underlying operations" cost structure seen with STS.
- If the strategic destination is GCS, STS provides native integration. If the destination is AWS storage (S3/EFS/FSx), DataSync is generally the native alternative.
STS vs Azure approaches
- Azure Data Box is focused on encrypted physical devices for offline ingestion and is an alternative when network-based transfer is impractical.
- Azure Data Factory's Copy activity is closer to ETL/orchestration and may be selected when transformations or orchestration are required rather than pure storage migration.
Egress economics
- Cross-cloud migration decisions are often governed by egress fees and request/operation costs at the source cloud; special commercial arrangements or credits can affect ROI calculations and should be considered in procurement discussions.
Market adoption trends
- No credible public market-share numbers for STS were found in this research pass.
- Frequent documentation updates and release notes in recent periods indicate active product development.

Aspect

Storage Transfer Service (Google)

AWS DataSync

Azure Data Box (and Data Box Gateway)

Starting Price

No published STS licensing fee for agentless transfers; agent-based file transfers billed at published per-GB transfer rates; private network transfers incur published regional per-GB transfer rates

DataSync service pricing is published by AWS; total cost also includes standard request, storage, and data transfer rates on involved AWS services

Device/order fees plus usage and shipping; published pricing often requires a calculator or sign-in for exact figures

Recommended For

Moving data into GCS from S3/Azure/on-prem/file systems; scheduled batch transfers; centralized job management

Moving data into/within AWS storage services; hybrid NAS to AWS patterns

Cases where network transfer is impractical and physical shipment of data is acceptable; very large offline moves

Key Strength

Managed transfers; private network options via interconnect; integration with GCS and Google IAM controls

Tight AWS storage integration and broad AWS ecosystem fit

Offline transfer with encrypted devices; avoids prolonged WAN transfers

Key Weakness

Not a general any-to-any mover; periodic scan cadence for some sources; IAM/service-agent complexity; operational overhead for agents

Destination lock-in potential; still subject to source egress and request/storage costs

Logistics lead time and device handling; not real-time

Storage Transfer Service

01Competitive Landscape

02Market Map

01Competitive Landscape

02Market Map