AWS migration readiness checklist
Heliodor | support@heliodor.cloud

Use these questions to make the first migration conversation concrete. An inventory, a named owner and a realistic change window are more useful than an assumed migration date.

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 the inventory, key dependencies and timing constraints to an initial migration discussion.

Preparation guide; not an official AWS assessment.