1. Inventory the live system
List domains, application files, database, storage, email dependencies, scheduled tasks and external services. Confirm account ownership and the available backups.
Migration process
Rehearse before sending visitors to the new home.
The changeover needs an agreed sequence, test list and person responsible for the recovery decision.
2. Prepare a protected destination
Check runtime compatibility and configuration. Transfer a suitable copy through the agreed protected process and test it without creating duplicate public sites, charges or customer messages.
3. Rehearse the important tasks
Check sign-in, forms, uploads, purchases or other relevant actions with controlled records. Compare the stored results and background jobs, not just the visible page.
4. Agree on the final data plan
Decide whether writes need a pause and how last-minute records or uploads will be transferred. Define the point where going back would also require reconciling new information.
5. Switch and verify
Make the authorized routing changes in the agreed window. Repeat the acceptance checks, review errors and confirm the new system is receiving the intended work.
6. Close the move deliberately
Retain the recovery material for the agreed period. Confirm backups, operating instructions and responsibility for the destination before decommissioning any old service under a separate agreed step.
Dates are easier to assess after the inventory.
Send the current site, destination and deadline without credentials.