{"id":50847,"date":"2022-11-21T00:00:00","date_gmt":"2022-11-21T00:00:00","guid":{"rendered":"https:\/\/www.techopedia.com\/aws-cloud-migration-dos-and-donts\/"},"modified":"2022-11-16T20:43:48","modified_gmt":"2022-11-16T20:43:48","slug":"aws-cloud-migration-dos-and-donts","status":"publish","type":"post","link":"https:\/\/www.techopedia.com\/aws-cloud-migration-dos-and-donts\/2\/34892","title":{"rendered":"AWS Cloud Migration: Dos and Don’ts"},"content":{"rendered":"

Moving an IT infrastructure<\/a> from one place to another is like moving a human: It's always stressful! But you can minimize this stress by using lessons learned from others' experiences.<\/p>\n

I've seen quite a few cloud migrations<\/a> in my career and, in this article, I would like to share some simple thoughts to help DevOps engineers<\/a>, architects, managers and anyone else who may be involved in their organization's move to the cloud. (Also read: <\/strong>Cloud Migration Strategy: 10 Mistakes to Avoid<\/strong><\/a>.)<\/strong><\/p>\n

But first, some disclaimers:<\/p>\n

    \n
  1. This article focuses primarily on AWS cloud<\/a> migration because I have a specialization in this subject. However, this information may be applicable to other cloud providers as well.<\/li>\n
  2. This article focuses mostly on migration from on-premise<\/a> to public cloud<\/a> because these migrations are, in my opinion, much more difficult than cloud-to-cloud migrations.<\/li>\n
  3. What works for one organization might be bad for another. While I'll tell you what's better to do and whaat to avoid in cloud migrations, please filter that through your critical thinking and remember that everybody has their own background and experience.<\/li>\n<\/ol>\n

    With that said, here are the dos and don'ts of AWS cloud migration:<\/p>\n

    Dos<\/span><\/h2>\n

    1. Conduct a Cloud Readiness Assessment<\/h3>\n

    If a person migrates to a new location, they should consider that:<\/p>\n