Small business owner at a desk reviewing migration notes next to a laptop while planning to move her website to a new hostMoving your website to a new host can feel like a risky technical project. With a little preparation, it’s usually a series of manageable steps, not a reason to panic.

You might be changing hosts because costs have climbed, support is hard to reach, or your site feels slow. Perhaps you have security concerns, or the developer who managed everything has disappeared. Those are understandable reasons to review your hosting.

But “the grass might be greener” isn’t much of a plan by itself. First, name the problem you want to solve. Then check that the new host can address it. A clear reason helps you compare providers and avoid moving the same problem somewhere new.

Keep your domain name

The decision that matters most is often the simplest: keep the same domain name. Your domain is your web address. Hosting is where your website’s files and related services live. Email is another service, even when it uses the same domain.

These pieces are connected, but they aren’t one thing. In many migrations, you change where the website lives without changing the address customers type into their browsers.

You usually do not need to transfer your domain registration to a new company just to move hosting. Keeping the domain where it is can reduce unnecessary changes. For more on protecting domain access, read why your domain lock matters.

Make an inventory before the move

Before anything changes, write down what your website depends on. You don’t need to understand every setting. You do need a list someone can check.

Include these items:

  • Domain and access: Which company is the registrar? Who controls its login and recovery email?
  • Domain Name System (DNS) records: Where are the current records managed? Ask for a copy of the full set.
  • Email: List mailboxes, forwards, aliases, and whether email is included with your current hosting.
  • Website data: Note the files, databases, and any special configuration your site needs.
  • Secure Sockets Layer (SSL) certificate: Confirm how the new host will provide and install the certificate.
  • Scheduled tasks: Ask whether any recurring jobs run behind the scenes. These are sometimes called cron jobs.
  • Connected services: List payment processing, contact forms, newsletters, analytics, bookings, and other outside accounts.
  • Paid themes and plugins: Record their names and check whether licences are tied to the old host or a particular account.

A hosting control panel may show some of these services. If you’re unsure where to look, see what your hosting control panel actually does. A simple inventory can prevent a small forgotten setting from becoming a very inconvenient surprise.

Take your own backup first

Before anyone touches the live site, make a full backup and copy it somewhere you control. Ideally, keep it somewhere separate from both hosting accounts.

Don’t rely only on the new host’s migration tool. Those tools can be useful, but your own copy gives you another way back if something goes wrong. Check that the backup includes both the website files and its database.

Ask how the backup can be restored, too. A backup is much more reassuring when you know it can actually be used. Our guide explains what website backups cover, and what they don’t.

Test the new copy before changing DNS

Ask the new host or developer to provide a temporary or preview address. This lets you inspect the migrated website before visitors are sent to it.

Check more than the homepage. Try important pages, images, logins, contact forms, and any checkout or booking steps. Forms may look fine but fail to deliver messages. A checkout may load but not complete correctly. Images might be missing because their files didn’t make the trip.

Think through a real customer visit. Can someone find a service, fill out your form, and receive a useful response? Find problems on the private copy, not after the public switch. If testing could trigger real orders or messages, ask how to avoid duplicate notifications or charges.

Lower the DNS timer ahead of time

About a day before the planned switch, ask whoever manages your DNS to lower the records’ time to live (TTL) value.

TTL is a cache timer. It tells internet services how long to remember where your website lives before checking for updated directions. A shorter timer can help more visitors pick up the new server sooner after the change.

This step doesn’t move the website or guarantee an instant switch. It simply reduces how long some services may keep using older directions. If you’re unsure which records to adjust, ask your host or developer. Avoid changing unrelated records.

Point the domain to the new server

When the new copy is ready, the person managing DNS changes the relevant records so they point to the new server.

For a while, some visitors may reach the new site while others still see the old one. That can happen because internet services update their stored directions at different times. It’s usually temporary.

Keep this period in mind if your site accepts orders, bookings, or other information that changes often. Ask your developer whether new activity needs to be paused or copied over during the switch. Don’t assume both copies will automatically stay in sync.

Give email special attention

Email is the part people often forget. Mailboxes, saved messages, forwards, and aliases do not always move with the website. If you use hosting-based email, the mail service may be changing too. If your email uses a separate provider, it may need to remain untouched.

Before the switch, confirm which company hosts each mailbox. Ask who will recreate the accounts, whether existing messages will be copied, and how to check both sending and receiving. Include shared addresses such as info@ and addresses that forward to staff.

Mail-related DNS records need careful handling. Mail exchange (MX) records direct incoming email. Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC) records help other providers verify email sent from your domain.

If these records are missing or copied incorrectly, messages may fail or land in spam. Ask for the existing email-related records to be copied exactly unless your email provider gives different instructions.

Losing access to a working mailbox during a website move is one of the most common self-inflicted problems. Confirm the email plan before the switch, not after an important message goes missing.

Keep the old host as a fallback

Don’t cancel the old hosting account as soon as the new site appears to work. Keep it available while you check the new setup and confirm that nothing still depends on it.

Give the new site time to run cleanly for a couple of weeks before cancelling the old service. The right timing can depend on your setup, so ask your host or developer what they recommend.

Check the site after the switch

During the first days, test the parts your customers rely on:

  • Submit forms and confirm messages arrive at the right address.
  • Check logins, images, and important pages.
  • Test email sending and receiving from each relevant mailbox.
  • Review notices in Google Search Console, if you use it.
  • Visit the site using its secure address and check for browser warnings.

Your site should show a working padlock and certificate on its secure pages. If you see a warning, contact your host or developer rather than telling visitors to ignore it. Learn more in our plain-language guide to the SSL certificate and padlock.

If something looks wrong, record what you saw and when. Our calm first-hour website outage checklist can help you gather useful details before contacting support.

Keep a record and ask clear questions

Write down what changed and when. Keep the important logins and provider details together in a secure place, with access for the right person in your business.

If your current developer holds the keys, request a written handover of the domain and hosting accounts before you start. You should know who controls each account and how your business can regain access.

Finally, ask the prospective host what its migration help actually covers. Does it include email? Testing? DNS changes? Fixes if a feature fails? Clear answers make it easier to plan a calm, careful move. You don’t have to do every technical task yourself, but you should know what is being moved and who is responsible for each piece.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail