Business & ownership
- Name the business service, application owner and technical decision-maker.
- Record why the move is happening and any fixed renewal or exit dates.
- Identify acceptable downtime and the business checks needed after cutover.
Application & dependencies
- List servers, databases, storage, scheduled jobs and external integrations.
- Map network dependencies, certificates, DNS and identity providers.
- Confirm operating-system, database and software licence constraints.
Target environment
- Choose account ownership and a proposed region based on requirements.
- Plan network connectivity, permissions, logging and cost allocation.
- Capture performance and storage baselines for initial sizing.
Migration & acceptance
- Choose a representative pilot and define success criteria.
- Record data reconciliation, test owners and rollback triggers.
- Prepare cutover, communication and operational handover runbooks.
Bring this to your next discussion
Bring the inventory, key dependencies and timing constraints to an initial migration discussion.
Explore the related service