Diagram
A decision tree branching on speed and continuity, need for managed reliability without rewrite, and need for scale to choose lift-and-shift, replatform, or modernize.
Choosing a Strategy by Goals and Constraints
The choice of migration strategy depends on effort, workload characteristics, and how much operational change the organization can absorb. Transforming in the source environment is limited by existing compute and may need extra transfer time and bandwidth, while transforming on Google Cloud provides virtually limitless processing but requires building pipelines. Starting downstream with reports and dashboards shows value quickly, while facade views let upstream tables evolve independently until source tables can be retired.
| Strategy | Change required | Choose when |
|---|---|---|
| Lift-and-shift | Move schema and data as-is | Speed and continuity matter most and pipelines cannot change yet |
| Replatform to Cloud SQL, Bigtable, or Firestore | Move to managed replication and backup with minimal redesign | Reliability, availability, and simpler operations are needed without rewriting applications |
| Modernize to BigQuery or Bigtable design | Redesign schema and queries for columnar or wide-column storage | Analytics scale, low latency at high throughput, and long-term cost efficiency justify more effort |
Domain 6 of 6
27 practice questions
Practice this DomainLast updated