How to Move a Website to a New Host

A successful hosting migration is mostly preparation. The file transfer may take minutes, but a rushed move can break forms, email, redirects, analytics, or domain settings that were never written down. Treat the project like a controlled change: inventory what exists, create a recoverable backup, test the copy, and only then direct visitors to the new server.

Before you choose the migration date

Pick a quiet period for the site. Avoid launching the move during a promotion, billing deadline, enrollment period, or any week when losing leads would be unusually expensive. If several people manage the website, name one person to approve the final DNS change and one person to test the result.

Confirm what the new host will actually migrate. “Free migration” can mean one WordPress site, files and database only, or a more complete service. Ask whether email accounts, DNS records, subdomains, staging sites, cron jobs, redirects, SSL certificates, and non-WordPress applications are included.

Build a complete website inventory

Primary domain, parked domains, subdomains, and domain registrar
Website files, databases, uploads, and configuration files
Email addresses, forwarding rules, mailing lists, and authentication records
DNS records for the website, email, verification services, and third-party apps
SSL, CDN, firewall, caching, and security services
Analytics, tag managers, search verification, payment tools, forms, and webhooks
Redirects, scheduled jobs, staging copies, and developer access

This inventory becomes the testing plan. It also prevents the common mistake of moving the visible website while leaving an essential background service behind.

Create a backup you control

Do not rely only on the source host’s backup interface. Download a full copy of the site files and database, and export any settings that live outside the website. For email migrations, confirm whether messages are stored on the server and whether they require a separate export or synchronization.

A backup is useful only if it can be restored. Record the software version, database credentials, PHP requirements, and any special server rules the site depends on. Our web-hosting backup guide explains the difference between account backups, application backups, and independent copies.

Copy first, switch later

Keep the original site online while the new copy is being built. Use a temporary address, hosts-file preview, or staging domain supplied by the new provider. The goal is to test the new environment without sending real visitors there.

Check the homepage, important landing pages, login, search, navigation, forms, downloads, images, checkout, account areas, mobile layout, and error pages. Verify that analytics fires once, confirmation emails arrive, payment webhooks work, and protected pages remain protected. Compare a sample of old and new URLs rather than assuming the homepage represents the whole site.

Plan the DNS change

DNS tells browsers and email systems where to find the service. Before the migration, record every existing DNS entry. When it is time to switch, change only the records required for the website unless the migration also includes email or another service.

Some visitors may reach the old server while DNS updates spread. Keep both copies online and avoid making competing content changes during that period. For a store or membership site, consider a short maintenance window or a final database synchronization so orders and account activity are not split between two servers.

Test immediately after launch

Load the site from more than one network and device.
Confirm HTTPS works without certificate or mixed-content warnings.
Submit every important lead, contact, and checkout form.
Verify email sending and receiving.
Check analytics, conversion tags, and search-console verification.
Crawl or manually inspect priority URLs for missing pages and redirects.
Watch error logs, uptime monitoring, and performance for unusual changes.

Keep a rollback path

Do not cancel the old account immediately. Keep the source site and independent backup until the new version has been stable long enough to cover normal visitor, form, and billing activity. Document how to point DNS back if a serious issue appears.

The Hosting Review Lab migration rule

Never let a migration promise decide the entire hosting purchase. It is valuable help, but the destination still needs appropriate resources, usable backups, clear renewal pricing, responsive support, and an upgrade path. Start with our Best Web Hosting shortlist or the guide to choosing a host for a small business, then verify the migration scope in writing.