Cloud migration assessment
Migration dates fail when dependencies, identity, data volume and rollback are still implicit. This engagement writes those items down against the target provider.
Who this engagement is for
Companies moving a production system to a public cloud, or between clouds, who need a readiness assessment before a date is committed.
Information required to begin
- Source environment (on-prem, colo or another cloud)
- Target provider and region constraints
- Application dependency list or CMDB extract if it exists
- Data volume, change rate and acceptable downtime
Engineering process
- Consultation to confirm the migration unit (one system, not the whole estate)
- Readiness review using the published checklist
- Written roadmap and risk register
Deliverables
- Current-state assessment of the migration unit
- Migration roadmap with gates
- Risk register including rollback
Provider-specific scope
- AWS Migration Hub and documented landing-zone prerequisites
- Azure Migrate and Cloud Adoption Framework ready state
- Google Cloud Migration Center where applicable
- Alibaba Cloud migration tooling for the source you actually have
Limitations
- Assessment is not a cutover. Implementation is a separate phase.
- We do not guarantee zero downtime.
What is not included
- Physical data-center decommission
- Application rewrite
Author
Written by Ankit Mehta. Methods used in this engagement are documented in the related guides below.