A reliable migration starts with an inventory, not a DNS change. Identify the website files, databases, scheduled jobs, application versions, email arrangements and domain records that support the service. Record what will move, what will remain with its current provider and who can authorize the final switch.
Recommended workflow
- Export the active DNS zone and record the old hosting, database and email endpoints before making changes.
- Prepare the destination, copy the required data and test using a controlled preview method.
- Agree the final data synchronization and DNS change window, then perform documented post-move checks before closing the migration.
Check the destination requirements before copying production data. PHP versions, extensions, database versions, storage capacity and file permissions can affect compatibility. Confirm the purchased migration scope: a single website move is different from transferring multiple accounts, mailboxes or custom server applications. Additional systems should be agreed before work begins.
Keep a current backup and a rollback route. Plan how to handle new orders, form submissions, uploads or other writes that occur during the move. For an active application, a final synchronization or short maintenance window may be needed to avoid divergent data. Do not cancel the source hosting immediately after changing DNS; allow time to verify traffic, mail flow and application behavior at the destination.
