Insight · Web Development

How to migrate a website to a new host without downtime

Move a website to a new host step by step: full backup, copy files and database, test on a temporary address, lower TTL, switch DNS and keep SEO.

Folded-paper crate full of small polygon blocks carried along a red paper path from a grey platform to a blue platform

Changing hosts is one of those jobs that looks simple until a contact form stops sending, half the images go missing or email vanishes along with the old account. The reasons to move are familiar: the site is slow, support never answers, renewals jumped, or the hosting sits in an old agency's account. The move itself follows the same order every time, and the work that keeps visitors from noticing happens before the DNS switch.

Disclosure: some links in this guide are partner links. If you buy through them, MMIX may earn a commission; your price stays the same.

Marketing MIX has moved client websites between hosts since 2012. These are the steps we follow on every migration, from small brochure sites to online stores.

What a migration involves

A website has three parts that can live in different places: the files and database (on the web host), DNS (at the registrar, the host or a service such as Cloudflare) and email (at the host or at a mail provider). A migration moves the first part. DNS only changes at the end, so traffic goes to the new server once it is ready. Email moves only if it was on the old host.

Write down where each part lives before you start. Most migration problems trace back to a part nobody knew about: a mailbox on the old host, a subdomain for a booking tool, or a scheduled task that sent invoices every night.

Free site review: two fields

Your site and how to reach you. We send back what to fix first and a one-month plan, by email or text.

By sending, you agree that Marketing MIX uses these details to answer you. Privacy. The request is deleted automatically 180 days after it arrives.

Step-by-step: migrating a website

Step 1: Take an inventory of the current setup

Log in to the current host and note:

  • the CMS and its version (WordPress, Joomla, a custom app), the PHP version and the database type;
  • every domain and subdomain the account serves;
  • where the nameservers point, and where email is hosted;
  • cron jobs, redirects in the server configuration and any SSL certificate in use;
  • disk usage, which tells you how long the copy will take.

Our guide to DNS records helps you read what the DNS panel shows.

Step 2: Make a full backup

Download all site files and export the database. On a cPanel host, the backup tool can create one archive of the home directory plus a database dump. For WordPress, a backup plugin or the hosting panel both work. Store the copy outside the old host, and check that the archive opens and the database file is complete. This backup is your rollback plan if anything goes wrong.

Step 3: Prepare the new hosting account

Pick a plan that fits the site. For a typical small business site, Namecheap shared hosting covers most needs. For heavier traffic or custom software, a VPS gives you more control. For a WordPress site where you would rather skip server work, a managed plan such as EasyWP is another option; our managed WordPress hosting guide compares the approaches.

Note where the host's datacenters are. Namecheap, for example, offers locations in the United States, the United Kingdom and the European Union. For a Canadian audience, the US locations are usually the closest. Then create the database and its user, and set the same PHP version the site runs today.

Step 4: Copy files and import the database

Upload the files through the file manager, SFTP or the host's import tool. Import the database dump through phpMyAdmin or the command line. Then update the configuration file (wp-config.php for WordPress) with the new database name, user, password and host.

If the domain stays the same, the content needs no search-and-replace. If you are also changing the domain, run a proper search-and-replace on the database with a tool that handles serialized data, such as WP-CLI for WordPress.

Step 5: Test the site on the new server

Preview the site on the new server before anyone else sees it. Many hosts give a temporary URL. A more reliable method is a hosts-file entry on your own computer that points the domain to the new server's IP address, so you see the real site at its real address while everyone else still reaches the old one.

Check the homepage and key pages, contact forms, logins, the cart and checkout, image uploads, search and any page that pulls data from another service. Compare speed with the old host using PageSpeed Insights once the site is live.

Step 6: Lower the TTL and switch DNS

The TTL tells other servers how long to cache a DNS record. A day before the switch, lower the TTL on the website's A records to a few minutes. On the day of the move, point the A record (or the nameservers) to the new host.

Keep the MX records and the email TXT records exactly as they are, unless email is moving too. If it is, set up the mailboxes at the new provider first and follow our guide to creating a business email address. If the old host also sent mail for your domain, review SPF with the SPF, DKIM and DMARC setup guide.

Step 7: Install SSL and check after the switch

Once DNS points to the new server, issue the SSL certificate there. Most hosts include a free certificate from Let's Encrypt or a similar authority. Load the site over https in a private window and fix any mixed-content warnings. If you see a "Not secure" warning, the SSL certificate guide covers the usual causes.

Over the next few days, test forms and email again, watch the server's error log, and check the Pages report in Google Search Console for new crawl errors.

Step 8: Keep the old host running for a while

Leave the old account active for at least one to two weeks. Some visitors and resolvers may hit the old server until their cache expires, and a forgotten piece is easier to recover while it still exists. Before you cancel, take a final backup and confirm nothing still points to the old IP address.

What to check and common mistakes

  • Email moved by accident. Changing nameservers without copying the MX records breaks email. Copy every record to the new DNS provider first.
  • Different PHP version. A plugin or theme that worked on the old server fails on the new one. Match the version, then upgrade on purpose later.
  • Search engines blocked. A staging setting or a leftover robots.txt rule that blocks crawling can slip into production. Check both right after the switch.
  • Forms that stop sending. The new server may block PHP mail. Send form messages through an SMTP service or the mail provider.
  • Old host cancelled too soon. Wait until traffic, forms and email have run cleanly for a week or two.
  • No rollback. Keep the backup and the old DNS values written down, so you can point back within minutes.

When to hand it off

A small site with one admin and no email on the host is a good do-it-yourself project. It gets riskier with an online store, a membership area, custom code, or when nobody knows what runs on the old server. Our website rescue and migration service handles the inventory, the copy, the testing and the switch, and keeps rankings in view throughout.

Prefer to hand it off? MMIX sets up domain, hosting, email and DNS for you — since 2012. Tell us about your project and we will reply with a plan.

↘Next move

READY TO BE FOUND BY HUMANS AND MACHINES?

Free first step

Free site review and a one-month plan

Send your site address. We look at the site, your ads and your search presence and send back what to fix first and a one-month plan. Ads management is quoted after the review.

Or reach the studio directly
+1 613 867 7767Messengerinfo@mmix.biz