---
title: "Comment by Nahid Mahmud on \"I Migrated a Product from AWS to GCP — Here's What I'd Do Differently\" | Hashnode"
description: "Love the practical examples. Are there any specific pitfalls or anti-patterns you'd warn beginners to avoid here?"
url: "https://hashnode.com/posts/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently/6a69533aba3a27735ad8fd2c/comment/6a698179b767141471eb3aae"
---

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

Comment [I Migrated a Product from AWS to GCP — Here's What I'd Do Differently](https://hashnode.com/posts/i-migrated-a-product-from-aws-to-gcp-here-s-what-i-d-do-differently/6a69533aba3a27735ad8fd2c)

[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.
