How to Move a Website to Another Host

A safe hosting move copies and tests the website before public traffic is switched. The exact commands depend on the platform, but the control sequence is consistent: inventory, backup, compatibility, copy, private testing, synchronisation, DNS change, verification and rollback readiness.

Step 1: Confirm the scope

Decide whether the move includes:

• website files and databases;
• email mailboxes;
• DNS hosting or nameservers;
• domain registration;
• CDN or firewall;
• certificates;
• scheduled jobs and background processes;
• staging sites and backups.

These services can be separate. Do not move email or the registrar merely because web hosting is changing.

Step 2: Record the current configuration

Export the DNS zone and note software versions, document root, database names, users, permissions, cron jobs, rewrite rules, environment variables, PHP or runtime settings, mail routes and external integrations. Capture screenshots or configuration exports where useful.

Step 3: Create and verify backups

Back up files, databases and any private storage to a location independent of both hosts. Check archive integrity and database size. Ideally restore the backup to a test location. A successful download is not proof that restoration will work.

Step 4: Prepare the new environment

• Use supported software versions compatible with the site.
• Create databases and least-privilege users.
• Set storage, permissions and runtime limits.
• Install certificates or prepare automatic issuance.
• Configure backups and monitoring before launch.
• Protect temporary access from search indexing and unauthorised visitors.

Step 5: Copy files and databases

Use a transfer method appropriate to the size and platform. Preserve hidden files, permissions and symbolic links where relevant. Import the database and update environment-specific configuration without performing broad search-and-replace operations unless URLs or paths genuinely change.

Step 6: Test privately

Use a temporary hostname or local hosts-file override so the real domain points to the new server only for the tester. Check:

• home, deep pages and media;
• login and administrator actions;
• forms and email notifications;
• search, uploads and downloads;
• booking, payment and webhooks in safe test modes;
• scheduled tasks;
• HTTPS and redirects;
• server and application logs.

Step 7: Plan changing data

For active shops, communities or booking sites, decide how new orders, accounts and submissions created after the first copy will reach the new database. Options include a short maintenance window, replication or a final database synchronisation. The method must prevent missing or duplicate transactions.

Step 8: Switch traffic

Change only the required DNS records or nameservers according to the plan. Preserve email and verification records. DNS caches update at different times, so both old and new environments may receive traffic temporarily.

Step 9: Verify externally

• Resolve the domain from more than one network.
• Confirm the certificate and hostname.
• Submit real test forms.
• Test critical transactions.
• Check email sending and receipt.
• Review logs and monitoring.
• Confirm Search Console access and index controls.

Step 10: Retain a controlled rollback period

Keep the old host and backups for the agreed period. Prevent accidental editing of both sites. If rollback is required, consider data created after the switch before sending traffic back.

Common mistakes

• Changing nameservers without preserving the full DNS zone.
• Forgetting scheduled jobs, webhooks or private files.
• Testing only the home page.
• Moving email unintentionally.
• Closing the old account immediately.
• Using an untested backup as the only recovery route.
• Combining the host move with unnecessary URL changes.

Official search reference

Google Search Central: changing web hosting without URL changes

The next practical step is to complete the configuration and DNS inventory before transferring any production data.