Map dependencies
List the application, data stores, identity, integrations and people responsible for them. A migration plan needs to account for how the system is used, not just where it runs.
Agree operational needs
Define who deploys, supports and pays for the workload. Set recovery objectives, monitoring needs and access controls in the context of the business.
Compare realistic options
Rehosting, modernisation and replacement have different costs and risks. Choose the smallest change that meets the requirement, with a realistic view of ongoing operation.
Rehearse and retain a route back
Test backup restoration, data migration and representative user journeys. Document cutover checks, responsibilities and rollback conditions before the switch.