Quick answer
A hosting migration should move the intended website and related services without losing current data or breaking customer workflows. Prepare the destination and recovery plan before directing public traffic to it.
Before you begin
Identify the source and destination accounts, domain and DNS owners, website platform, email provider, and any external integrations. Confirm the exact migration scope and responsibilities.
What to do
- Inventory files, databases, scheduled tasks, mail dependencies, certificates, and required runtime features. Check the new plan supports the application.
- Capture verified backups and prepare the destination using an isolated preview method. Keep sensitive exports outside public directories.
- Test representative pages, administration, forms, media, and integrations on the destination. Prevent the preview copy from sending duplicate messages or live transactions.
- Plan final synchronization for new content or orders and define the DNS change window. Keep a rollback route and avoid canceling the old service prematurely.
- After the approved switch, verify public website behavior, HTTPS, email routing, and important records. Monitor for requests still reaching the old environment.
How to check the result
A migration passes when the agreed application and services work on the intended destination and recent data is accounted for. A DNS lookup or copied archive alone is not full acceptance.
If you need help
If the application needs unsupported features or a busy database cannot be synchronized safely, resolve that before switching traffic. Send redacted inventories and account references rather than transferring passwords or database exports in ordinary chat.
Related help
- Prepare a domain transfer while keeping the website and email running
- Plan DNS TTL changes before a website cutover
- Check website and email behavior after a migration
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
