Prepare and test your skills
Prepare and test your skills
Evaluation of migration methodologies and validation testing is the process of choosing how much to change each workload for Google Cloud (opens in a new tab) and proving the workload still performs, scales, and works correctly. The methodology decision balances downtime tolerance against cost and complexity. Testing validates feasibility before migration and functional integrity during and after migration.
Migration strategy selection starts with downtime tolerance because zero and near-zero downtime strategies are usually more costly and complex than strategies that require downtime. Mission-critical workloads use zero or near-zero downtime approaches to avoid data loss, while secondary or backend workloads can accept a cutover window to keep the move simpler and cheaper. Migration should not be treated as lift-and-shift only, but as a chance to improve design, code quality, cost-efficiency, and use of Google Cloud built-in features.
The four change-based strategies build on a basic lift-and-shift baseline and differ in what changes and how much time and skill they need:
| Strategy | What changes | Time, skill, and tradeoff |
|---|---|---|
| Refactor | Modify workloads to use cloud capabilities such as scalability and high availability | Takes longer than rehost and requires new skills; choose when a major update is needed with migration |
| Re-architect | Change how code functions, for example splitting a monolith into microservices | More complex than refactor, takes more time, and can introduce bugs that need several rounds of testing |
| Rebuild | Decommission the app and rewrite it as fully cloud-optimized | Takes longest, removes technical debt, but is not suitable for ready-made apps |
| Repurchase | Move to a cloud software-as-a-service (SaaS) equivalent such as Google Workspace | Easier on resources than refactor or rebuild, but can cost more with less granular control |
Refactor timing depends on team experience. Teams with little migration experience often modify workloads while migrating, while experienced teams plan changes in advance to take full advantage of cloud capabilities.
Exam tip: Refactor restructures how workload code works to use cloud features, while re-architect changes how that code functions, such as splitting a monolith into microservices.
Migration tool selection happens after the strategy is chosen for each workload. Managed migration services encapsulate the complex logic of moving data, workloads, or entire infrastructures and offer migration monitoring capabilities. Deployment patterns, infrastructure orchestration, and custom migration applications can also support cutover.
Tool choice depends on the specific migration use case:
Matching the tool to these five factors reduces friction during transfer and cutover. A large, frequently changing dataset needs different tooling than a small, static workload, even when both use the same strategy.
A proof of concept (POC) is a small, preliminary implementation that validates feasibility, functionality, and potential benefits before full migration. The POC process starts by defining scope and specific success criteria, such as full workload compatibility, minimal downtime, and specific performance demands. Findings, challenges, and potential solutions are captured in migration plan documentation, and several POCs are iterated until success criteria are met.
A POC helps investigate high-risk questions at low cost:
Concrete POC examples include running the same business logic against Cloud SQL, Spanner, Firestore, or Bigtable to compare benchmarks and operating costs. Another example is using PerfKit Benchmarker to measure end-to-end virtual machine (VM) provisioning time plus latency, throughput, and time-to-complete, including tasks such as provisioning many Kubernetes clusters.
Validation of migration results is a continuous process before, during, and after migration, not a one-time event. Test cases are refactored before migration to reflect the Google Cloud target environment, so they check new dependencies, configuration, and service behavior. This continuous focus ensures that performance, scalability, and functional integrity are proven at each stage rather than only at cutover.
Validation follows an ordered flow from preparation through post-migration proof:
Post-migration testing in the target environment confirms that core behavior survived the move and that scaling works under real demand:
Network infrastructure planning and hybrid connectivity is the design of the network that links a source environment to Virtual Private Cloud (VPC) (opens in a new tab) during and after migration. The plan defines VPC layout, subnet addressing, Cloud Interconnect or Cloud VPN connections, routing, and Cloud DNS so migrated and unmigrated workloads can communicate reliably. Network design must be addressed before moving workloads because it controls migration traffic flow, bandwidth for large transfers, and routing and costs in the hybrid period.
VPC planning establishes the global network container and its regional subnets for migrated workloads. A VPC network is a global resource, while each subnet is bound to a single region and cannot be reused across regions after migration. Because subnets cannot use overlapping IP addresses in normal routing, maintaining the same addresses after a move typically requires creating a new VPC.
VPC planning also includes connectivity features that support secure and scalable growth. VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC for connecting projects and services without using public addresses. Choosing these options early helps the landing zone support multiple applications, each with its own networking pattern, while keeping traffic private and routable. The result is a foundation where new subnets can be replicated in another region without tightly coupling workloads to one topology.
Hybrid connectivity is the link between an on-premises network and the VPC network in Google Cloud. Cloud Interconnect extends an external network to the Google network through a high-availability, low-latency connection, while Cloud VPN securely extends a peer network to the Google network through an IPsec VPN tunnel. Either product can connect the two sides, and establishing this connectivity comes first so distributed application components can communicate.
| Product | Connection type | Role in migration |
|---|---|---|
| Cloud Interconnect | Dedicated, high-availability, low-latency connection using VLAN attachments | Carry steady, high-volume traffic and large dataset transfers |
| Cloud VPN | IPsec VPN tunnel over the internet using HA VPN tunnels and Cloud Routers | Provide secure, faster-to-provision connectivity and backup access |
Interconnect and VPN traffic depends on correct regional placement and router configuration. VLAN attachments connect in a specific region, so the attachment region must be changed before dismissing that region to avoid extra region-to-region traffic. With Partner Interconnect, changing regions can mean selecting a different physical location, so a temporary backup path over the public internet is useful while provisioning is in progress. If subnet addresses change and Cloud VPN is used, routers must be reconfigured or hybrid traffic will fail.
Hybrid Subnets is a VPC routing mode that lets a VPC network share a CIDR block with a connected on-premises network during migration. If a packet matches a hybrid subnet route but its destination IP is not assigned to a resource in that VPC subnet, Google Cloud forwards the packet to the on-premises network using dynamic or static routes. This behavior lets workloads migrate incrementally without changing IP addresses, because migrated workloads in the VPC and remaining workloads on-premises can still reach each other by internal IP. After all workloads have moved, hybrid subnet routing is disabled to restore normal routing.
Enabling Hybrid Subnets requires three components working together in the same region:
allow-cidr-routes-overlap flag, and the subnet IPv4 range matches the on-premises CIDR hosting the workloads.All regional pieces must align for the overlap to work. The HA VPN tunnels or VLAN attachments, Cloud Router instances, and subnets with hybrid routing enabled must all be in the same region. For most use cases the primary IPv4 range matches the on-premises CIDR block, which keeps identity and firewall expectations stable while each machine moves.
Exam tip: VPC networks are global but subnets are regional, and Hybrid Subnets requires the tunnels or attachments, Cloud Routers, and overlapping subnet to all be in the same region.
Routing and DNS planning keeps hybrid traffic efficient and avoids broken name resolution during cutover. Cloud DNS helps decouple workload identity from specific subnet IPs, and DNS peering can route traffic for migrated workloads before the old region is dismissed. Preferring replicable, loosely coupled designs makes it easier to recreate routing and naming in a new region. Products that support multi-region or global configurations further simplify moves because they only need reconfiguration, not migration.
Traffic management also means controlling where packets travel and what they cost. On-premises connectivity can be region specific, so leaving a VLAN attachment in a dismissed region forces traffic to hairpin between regions. Data-intensive workloads need explicit review of transfer volume, bandwidth, and network flows because cloud networks bill for utilization in ways a one-time purchase of routers and cabling does not. Egress traffic leaving Google Cloud and traffic crossing regional or zonal boundaries can incur charges on services including Compute Engine, Cloud Storage, Cloud SQL, and Cloud Interconnect.
A scalable network foundation integrates connectivity, organization structure, and automation into the landing zone. In the plan phase, teams define the communication model between distributed applications and among components, select a networking architecture pattern that supports the chosen application pattern, and align it with the Google Cloud organization, project, and resource hierarchy. In the deploy phase, connectivity is established first based on the selected design and networking pattern, then applications are tested against functional and load criteria before production cutover.
Repeatability and safety come from software-defined networking and backup paths. In Google Cloud the physical network is virtualized, so networks are deployed and torn down with infrastructure-as-code tools such as Terraform for consistent results. Rollback planning includes backup communication channels when provisioning is risky, such as keeping internet-based access available while Partner Interconnect is configured. Together, early connectivity setup, region-aware routing, DNS decoupling, bandwidth and cost review, and automated deployment provide reliable hybrid connectivity for large transfers and steady-state operation.
Dependency mapping and migration sequencing is the process of discovering how workloads depend on each other and ordering their moves to Google Cloud in logical groups. A dependency map records which application calls which database, service, network, or third-party system, and the sequence uses that map to decide what moves together and in what order. This approach keeps connected components together during cutover, limits downtime, and maintains continuity while parts of the system live in source and target environments.
Dependency mapping starts with a comprehensive inventory of workloads built with Migration Center (opens in a new tab), Google Cloud's unified platform for discovery and assessment. The inventory is organized into a workload catalog matrix where each workload is scored on business criticality, whether it has dependencies or is a dependency for others, maximum allowable downtime, and migration difficulty. A migration complexity indicator of easy to migrate, hard to migrate, or cannot be migrated is added with expert help, and charts highlight how many components have dependencies.
The catalog distinguishes the number, type, and scope of dependencies across applications, data, and infrastructure. Application dependencies include calls between services, shared databases, and reliance on external systems and third-party middleware for storage, messaging, and hosting. Infrastructure dependencies include organization and project structure, network connectivity, load balancers and DNS records, identity and access controls, and runtime configuration such as secrets and keys. Tightly coupled workloads break if a dependency is unavailable, while loosely coupled workloads tolerate outages because they use a message broker, work offline, or retry.
| Workload example | Dependency position | Allowable downtime | Migration difficulty |
|---|---|---|---|
| Stateless microservices | No dependencies or dependents | 2 minutes | Easy |
| SQL database | Has dependencies or dependents | 10 minutes | Easy |
| Ecommerce workload | Has dependencies and dependents | No downtime | Hard |
The table shows why sequencing follows the map rather than business importance alone, since the stateless service can move early while the ecommerce workload must wait for its database and a zero-downtime strategy.
A migration wave, also called a batch or sprint, is a group of workloads and data that move together because they share dependencies, teams, or operational requirements. Grouping keeps a workload with the databases, message queues, and supporting services it needs, so traffic does not have to cross between the source environment and Google Cloud for longer than necessary. As teams gain experience, they refine grouping, increase batch size, and update the composition and order of batches.
Workloads are assessed against shared criteria to decide the grouping:
This grouping also produces the core migration documents, which are the technical design document, the RACI matrix that assigns who is responsible and accountable, and the timeline such as a T-minus plan. Together these documents record which batch moves when, who executes each step, and how rollback will work if a step exceeds its allowed time.
Migration sequencing orders both the waves and the workloads inside each wave. The plan is completed in an ordered sequence that moves foundational pieces first and builds skill with low-risk batches. Moving dependencies before their callers ensures the database or platform is ready when the application cuts over.
Migration sequencing follows three ordered steps:
The workloads moved first are called first-movers, and they are chosen to let teams learn with minimal blast radius. Good first-movers are non-mission-critical but commonly used, representative of wider patterns rather than edge cases, owned by motivated teams with leadership sponsorship, and able to tolerate a cutover window. A Python workload built with test-driven development is a better first-mover than a one-off Java workload with little test coverage when most of the estate is Python, because lessons apply directly to later waves.
Exam tip: Choose first-movers with the fewest dependencies, loose coupling, stateless design, and minimal refactoring, and avoid mission-critical systems and rare edge cases for the first waves.
Latency, data synchronization, and third-party integrations determine whether dependent workloads can be split across environments during a wave. Workloads with strict latency requirements must move with the databases and services they call frequently, because separation across on-premises and Google Cloud networks adds delay and network cost. Network dependencies also shape cutover order, since load balancer reconfiguration time, DNS time to live (TTL), client-side DNS caching, and connectivity such as Partner Interconnect or Cloud VPN control how quickly traffic shifts to the target.
Stateful workloads require extra sequencing because data exists in two places during migration. A stateless workload rarely needs data migration and avoids a transitory phase where data is partially in the source and partially in Google Cloud, which is why stateless microservices are preferred early. A stateful database must be synchronized and validated for size, change rate, consistency model, and proximity to applications, and workloads that cannot tolerate downtime need a zero-downtime approach such as dual writing and reading or a data-access microservice. Third-party middleware, licensed software, and compliance rules can further constrain order when a license forbids cloud execution, when sole-tenancy or regional data-residency is required, or when authentication, observability, and storage integrations must be modernized before the dependent application can operate.
Refactor modifies workloads to use cloud capabilities such as scalability and high availability, while re-architect changes how code functions such as splitting a monolith into microservices. Refactor takes longer than rehost and requires new skills, while re-architect is more complex than refactor, takes more time, and can introduce bugs that need several rounds of testing.
Cloud Interconnect provides a dedicated high-availability low-latency connection using VLAN attachments to carry steady high-volume traffic and large dataset transfers, while Cloud VPN provides a secure IPsec VPN tunnel over the internet using HA VPN tunnels and Cloud Routers for faster-to-provision connectivity and backup access. Establishing this connectivity comes first so distributed application components can communicate between the on-premises network and the Virtual Private Cloud network.
Enabling Hybrid Subnets requires connectivity through Cloud VPN or Cloud Interconnect, hybrid routing enabled on the subnet with the allow-cidr-routes-overlap flag and an IPv4 range matching the on-premises CIDR, and a migration tool such as Migrate to Virtual Machines to move workloads into the overlapping subnet. The HA VPN tunnels or VLAN attachments, Cloud Router instances, and subnets with hybrid routing enabled must all be in the same region, and after all workloads have moved hybrid subnet routing is disabled to restore normal routing.
Migration waves should be ordered by placing dependent applications, their databases, and shared platform services in the same batch, moving low-risk low-dependency batches first, and moving foundational dependencies before the applications that call them. Good first-movers are non-mission-critical but commonly used workloads with the fewest dependencies, loose coupling, stateless design, and minimal refactoring that can tolerate a cutover window.
An enterprise is planning to migrate a three-tier web application from an on-premises data center to Google Cloud. Based on workload assessments, the architecture team has chosen a mixed migration approach:
You need to establish a testing and validation protocol to verify the application's functional integrity, scalability, and performance before executing the final production cutover.
Which validation strategy should you implement?
Last updated