Collect information and access
Identify the providers for domain, hosting and email. List subdomains, databases, scheduled tasks and external services. Confirm panel access before migration begins. Share passwords only through an agreed channel. Include forms, payments and other functions in the project description so that the required checks can be prepared.
Prepare current backups
The backup should contain files and database data from a suitable point in time. For a shop, agree how orders created during the work will move. Email needs its own synchronisation plan. Check that archives are readable and contain the required configuration. Keep original data until the new environment is verified.
Test the destination
Review PHP, database, extension and permission compatibility. Try important journeys: sign-in, forms, search and purchase. Do not accidentally enable real payments or bulk messages during testing. Agree how to check integrations requiring the correct domain or approval from an external provider. Record problems before making the final switch.
Plan switching and verification
Agree on timing, final synchronisation and any interruption. Account for TTL and DNS caching. After switching, check the site, HTTPS, email and scheduled tasks. Write down the conditions for returning to the previous configuration. Do not cancel the old service until the new data and operation are confirmed.