---
title: "Discussion on \"I Migrated a Product from AWS to GCP — Here's What I'd Do Differently\" | Hashnode"
description: "Discussion on \"I Migrated a Product from AWS to GCP — Here's What I'd Do Differently\". A chronological account of migrating a live product from AWS to GCP — compute, database, secrets, and CI/CD — with honest lessons at each step"
url: "https://hashnode.com/posts/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently/6a69533aba3a27735ad8fd2c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [I Migrated a Product from AWS to GCP — Here's What I'd Do Differently](https://blog.madhav.dev/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently?utm_source=hashnode&utm_medium=feed)

A chronological account of migrating a live product from AWS to GCP — compute, database, secrets, and CI/CD — with honest lessons at each step

Jul 29 · 5 min read · blog.madhav.dev  
Read the article

-   [#gcp](https://hashnode.com/tag/gcp)
-   [#aws](https://hashnode.com/tag/aws)
-   [#cloud-migration](https://hashnode.com/tag/cloud-migration)
-   [#devops](https://hashnode.com/tag/devops)
-   [#backend-engineering](https://hashnode.com/tag/backend-engineering)

## Written by

[Madhav Bhasin](https://hashnode.com/@madhavbhasin)

@madhavbhasin · Noida, India

  
[View profile](https://hashnode.com/@madhavbhasin)

Production patterns for backend engineers who are tired of hello-world tutorials.

Senior full-stack engineer and engineering lead with 5+ years building cloud-native systems at scale. I write about the things the docs don't cover — GCP, FastAPI, Terraform, event-driven architecture, and AI-powered backends. No hello-world demos.

## Responses 2

Markdown supported · ⌘↵ to post

[Nahid Mahmud](https://hashnode.com/@nahidmahmud555)

[Jul 29](https://hashnode.com/posts/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently/6a69533aba3a27735ad8fd2c/comment/6a698179b767141471eb3aae)

Love the practical examples. Are there any specific pitfalls or anti-patterns you'd warn beginners to avoid here?

[Madhav Bhasin](https://hashnode.com/@madhavbhasin)

[Aug 4](https://hashnode.com/posts/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently/6a69533aba3a27735ad8fd2c/comment/6a698179b767141471eb3aae#reply-6a71900ba8231247706d2922)

Three that actually hurt us:

Migrate and refactor separately. When something breaks mid-migration you won't know which change caused it. Move first, clean up after.

Don't assume equivalent services behave the same. SQS and Pub/Sub are both "message queues." The delivery guarantees and retry behaviour are different enough to surprise you.

Write a rollback plan per service, not just for the database. When a Cloud Run service had issues post-deploy, we were improvising. A one-page runbook per service removes the stress.

Good rule of thumb: if a decision feels rushed mid-migration, it probably is.
