CNE GCP Ready: Migration Paths
This reference helps you choose migration approaches for moving document libraries and databases into Google Cloud Platform (GCP) environments running Cloud Native Experience (CNE).
Migration options are ordered from the simplest operational approach to more advanced migration strategies for large-scale or specialized environments.
Google Cloud does not charge for inbound data transfer.
AWS, Azure, and other providers may charge outbound (egress) transfer fees for cross-cloud migrations.
Document Library Migration
Choose a migration approach based on the source system, dataset size, operational complexity, and available network bandwidth.
Local Filesystem or On-Premises
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | gcloud storage cp or rsync from workstation or staging VM | Free transfer. Cloud Storage storage and request charges apply. |
| Managed | Storage Transfer Service (on-premises agents) | Approximately $0.0125/GB for agent-based filesystem transfers. |
| Advanced | Large dataset migration guide | Pricing depends on selected architecture and infrastructure. |
Use direct gcloud storage commands for smaller datasets and one-time migrations.
Use Storage Transfer Service for recurring or operationalized migrations.
Amazon S3 or Azure Blob Storage
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Storage Transfer Service from Amazon S3 or Azure Blob | No additional Google Cloud transfer charge for agentless transfers. Source-cloud egress charges may apply. |
| Medium | Storage Transfer Service through gcloud or APIs for scheduled migrations | Same pricing model as standard Storage Transfer Service transfers. |
| Complex | Dataflow pipelines or rclone-based migrations | Compute charges apply for Dataflow workloads. Source-cloud egress charges may apply. |
Large-Scale Migrations (2 TB+ or Constrained Networks)
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Storage Transfer Service with parallel agents | Approximately $0.0125/GB for filesystem-agent transfers. |
| Medium | Transfer Appliance | Hardware rental and shipping charges apply. |
| Complex | Dedicated Interconnect with parallel composite uploads | Networking and Interconnect charges apply. |
Database Migration
Database migration approaches depend primarily on the source database engine and migration complexity.
Database Migration Service (DMS) homogeneous migrations are free.
Heterogeneous migrations between different database engines are billed separately.
MySQL / MariaDB
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Database Migration Service to Cloud SQL for MySQL | Free for homogeneous migrations. |
| Medium | mysqldump export with Cloud Storage import | Cloud Storage and Cloud SQL charges apply. |
| Complex | Self-managed migrations on Compute Engine | Compute and operational costs apply. |
PostgreSQL
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Database Migration Service to Cloud SQL for PostgreSQL | Free for homogeneous migrations. |
| Medium | pg_dump export and import workflows | Cloud Storage and Cloud SQL charges apply. |
| Complex | Database Migration Service to AlloyDB | AlloyDB infrastructure pricing applies. |
SQL Server
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Database Migration Service to Cloud SQL for SQL Server | Free for homogeneous migrations. |
| Medium | Backup and restore workflows through Cloud Storage (.bak) | Cloud Storage charges apply. |
| Complex | Continuous migration or log shipping architectures | Standard infrastructure and networking charges apply. |
Oracle
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Bare Metal Solution for Oracle | Bare Metal Solution infrastructure and Oracle licensing costs apply. |
| Replatform | Database Migration Service from Oracle to PostgreSQL | Heterogeneous DMS migrations are billed separately. |
| Streaming | Datastream or Database Migration Service to AlloyDB | Data processing and heterogeneous migration charges apply. |
Pricing Overview
General migration pricing rules include:
- Google Cloud does not charge for inbound data transfer.
- AWS, Azure, and other providers may charge outbound (egress) transfer fees.
- Google Cloud charges depend on the services used during migration, including storage, compute, networking, and managed migration services.
For up-to-date pricing details, see Storage Transfer Service pricing, Database Migration Service pricing, and Transfer Appliance pricing.