CNE GCP Ready: Migration Paths
This reference helps you choose how to migrate document libraries and databases into Google Cloud Platform (GCP) for use with Cloud Native Experience (CNE).
Use this guide to select a migration approach based on source system, data size, and operational constraints.
GCP does not charge for inbound data transfer. AWS and Azure bill outbound (egress) data transfer at their published rates, which applies to cross-cloud migrations.
Document Library Migration
Local Filesystem or On-Premises
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | gcloud storage cp or rsync from workstation or staging VM | Free transfer. Storage and request charges apply in GCP. |
| Managed | Storage Transfer Service (on-premises agents) | ~$0.0125/GB (agent-based transfers) |
| Advanced | Large dataset migration guide | Depends on architecture |
Amazon S3 or Azure Blob Storage
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | Storage Transfer Service (S3 / Azure Blob) | No additional charge for agentless transfers; source egress may apply |
| Automated | Storage Transfer Service API / gcloud | Same as above |
| Advanced | Dataflow or rclone | Compute-based pricing applies |
Large-Scale Migrations (2 TB+ or Constrained Networks)
| Tier | Approach | Pricing |
|---|---|---|
| Easiest at scale | Storage Transfer Service with agents | ~$0.0125/GB (filesystem agents) |
| Medium | Transfer Appliance | Hardware rental + shipping |
| Advanced | Dedicated Interconnect + parallel uploads | Networking costs apply |
Database Migration
Database Migration Service (DMS):
- Homogeneous migrations (same engine) → free
- Heterogeneous migrations (cross-engine) → paid
MySQL / MariaDB
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | DMS → Cloud SQL for MySQL | Free |
| Manual | mysqldump + Cloud Storage import | Storage + Cloud SQL costs |
| Advanced | Self-managed migration on Compute Engine | Compute costs apply |
PostgreSQL
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | DMS → Cloud SQL for PostgreSQL | Free |
| Manual | pg_dump + import | Storage + Cloud SQL costs |
| Modernization | DMS → AlloyDB | AlloyDB pricing applies |
SQL Server
| Tier | Approach | Pricing |
|---|---|---|
| Easiest | DMS → Cloud SQL for SQL Server | Free |
| File-based | BAK restore via Cloud Storage | Storage costs |
| Advanced | Continuous migration / log shipping | Minimal downtime, standard costs |
Oracle
| Tier | Approach | Pricing |
|---|---|---|
| Lift-and-shift | Bare Metal Solution for Oracle | Infrastructure + Oracle licensing |
| Replatform | DMS Oracle → PostgreSQL | DMS heterogeneous (paid) |
| Streaming | Datastream or DMS → AlloyDB | Data processed billed |
Pricing Overview
General Rules
- GCP does not charge for inbound data transfer
- AWS and Azure bill outbound (egress) data transfer at their published rates
- GCP charges depend on service usage (storage, compute, network)
For up-to-date pricing details, see Storage Transfer Service pricing, Database Migration Service pricing, and Transfer Appliance pricing.