Move a website without making it a fire drill
A hosting migration is easier when you separate copying the site from changing where visitors are sent. Prepare the new environment first, test it, then make the DNS change.
Before the move
Make a current backup of website files and databases. Record DNS settings, email configuration, PHP or runtime versions, scheduled tasks, redirects, SSL needs, and any third party integrations.
Test before changing DNS
Copy the site to the new host and test important pages, forms, logins, checkout flows, images, scripts, and email related functions. Keep the old hosting active during the cutover so you have a fallback.
After the switch
Confirm HTTPS, forms, analytics, Search Console access, redirects, and email delivery. Watch error logs and important business actions. Do not cancel the old account until you are confident the new copy is complete.
Do not forget email and DNS
A website can appear to migrate successfully while email or a third party service breaks because a DNS record was missed. Record the existing DNS zone before making changes. Pay particular attention to mail records, verification records, subdomains, and services that point somewhere other than the web server.
Plan a rollback
Keep the old hosting active until the new site has been tested after the DNS change. A rollback plan gives you somewhere to return if an important function was missed during testing.
Need a host with migration options?
InMotion currently advertises migration tools and transfer help across parts of its hosting lineup.
Check InMotion Hosting