September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Check out the below links. May prove helpful.
This is not comprehensive, but here are a few things to consider.
From a project management perspective, make sure the basics are well covered, especially stakeholder analysis and a communications plan. If there is any downtime, make sure it is communicated/coordinated well in advance, and often. Someone is going to want to have an event that requires your software during your downtime, no matter how much notice you give.
From a technical perspective, rehearsal migrations and thorough testing will be critical. This will also help you to establish, and communicate, the amount of downtime.
Make sure you also have a clearly defined post go-live support plan, especially if multiple locations are impacted by the change. This should include separate plans for the period immediately following go-live, the following week (more or less), and, if needed, a plan to transition to normal support (handoffs, knowledge transfer, etc...).
Andrew, the links are comprehensive! They will definitely help me to define the key points of the migration and plan it.
Aaron, Thank you for the top level overview. Seems like your bits of advice are valuable for any type of migration, not only to AWS.
This is very interesting...Can anybody provide a high level and detailed WBS template for such a migration to the Cloud (Transition & Transformation phases, ....)
For example what do you do in Day one and so on....
How to start ? How and What to communicate ?
I speaking about infrastructure but also about applications move or rebuilt....
Please login or join to reply