Move a Small Business Site to a New Host Without Downtime
The usual story goes like this. The owner of a small shop is unhappy with their host, signs up somewhere new, asks a freelancer to "move the site", and on Thursday evening the DNS is switched.

The usual story goes like this. The owner of a small shop is unhappy with their host, signs up somewhere new, asks a freelancer to "move the site", and on Thursday evening the DNS is switched. Friday morning, half the customers see the new site, half see the old one, two orders placed overnight exist only on the old server, and the contact form on the new one sends nothing because email settings were never copied. Nobody is sure which version is real.
None of this is necessary. A small business website can move to a new host with no visible downtime and no lost orders, if the steps happen in the right order and the switch is planned a couple of days ahead. I have moved more than eighty sites for clients, and the ones that went badly almost always skipped the same two steps: lowering the DNS TTL early, and testing the new copy before switching.
Why moves cause downtime in the first place
When someone types your domain, their device asks the DNS system where the site lives. The answer is an IP address, and it comes with a TTL, a "time to live" that tells resolvers how long they may remember it. Many registrars set this to 14,400 seconds (four hours) or even 86,400 (a full day). When you change the address, resolvers that remembered the old one keep sending people there until their copy expires.
That is why "propagation takes up to 48 hours" became such a common phrase. It is not really the internet being slow. It is cached answers waiting to expire. If you lower the TTL to 300 seconds (five minutes) a day or two before the move, the old answer expires quickly and the switch takes minutes instead of hours.
The second cause is change during the move. If a shop takes orders while files and database are being copied, those orders land on the old server after the copy was made. For a brochure site, this does not matter. For a WooCommerce shop or a booking site, it does.
The move, step by step
This is the order I follow for a typical WordPress site on shared or managed hosting. Allow two short sessions, one to prepare and one for the switch, two days apart.
- Two days before: lower the TTL. In your DNS settings, change the TTL on the main A record (and the www record) to 300 seconds. Note the old values so you can restore them later.
- Take a full backup and keep it off both servers. Files plus database, downloaded to your own computer or cloud storage.
- Copy the site to the new host. A migration plugin such as Duplicator or All-in-One WP Migration handles most small sites; many hosts also offer free migration. Make sure the database, uploads folder and any custom files come across.
- Test the new copy before anyone sees it. Edit the hosts file on your computer (on Windows it lives in
C:\Windows\System32\drivers\etc\hosts) and add a line pointing your domain to the new server's IP, for example203.0.113.10 yourshop.com.bd. Your browser now loads the new site while everyone else still sees the old one. Click through every important page, submit the contact form, and place a test order if you run a shop. - Set up email and SSL on the new host. Install the SSL certificate (most hosts issue a free Let's Encrypt one) and check how the site sends email. Contact forms often fail after moves because the new server's mail settings differ; an SMTP plugin connected to your email provider fixes this.
- On the switch day, freeze changes. For a shop, pick the quietest hour from your analytics, often early morning. Put a short maintenance notice on the checkout, or pause new orders for 20 to 30 minutes.
- Copy the database one last time, so any orders or posts from the last two days come across, then change the DNS A record to the new IP.
- Watch both servers for an hour. Thanks to the low TTL, most traffic moves within ten minutes. Check the old server's order list once more for stragglers.
- A week later: raise the TTL again and cancel the old plan. Not before. Keep the old hosting for at least seven days as a fallback.
What usually breaks, and how to catch it
In my notes from past moves, three problems account for most of the trouble. Email from contact forms, as mentioned above. Hard-coded links: older sites sometimes have image or page addresses written with the full old domain or a temporary hosting address, which a search and replace tool like Better Search Replace fixes. And PHP versions: if the new host runs PHP 8.3 and an old plugin was written for PHP 7.4, you can get a white screen. Check the PHP version on both hosts before moving, and match it first, then upgrade later as a separate step.
Email hosting deserves its own warning. If your business email lives with your web host, moving the website means moving the mailboxes too, which needs its own plan. I strongly prefer to keep email with a separate provider so a website move never touches it.
Where I disagree with "let the host migrate it for free"
Free migration offered by the new host is genuinely useful, and I recommend accepting it for simple sites. But it is often described as a complete solution, and it is not. The host's team copies the files and database. They usually do not lower your TTL in advance, do not test your contact form, do not know your shop's quiet hours, and will switch the DNS whenever their queue reaches your ticket. I have seen a host's migration team switch a pharmacy's site at 7 p.m. on a weekday, the busiest ordering hour.
Use the free migration for the copying, and keep control of the timing and the testing yourself. Ask them to copy the site but not touch the DNS; you will switch it once you have tested through the hosts file.
Before you pick the new host
A move is a good moment to check whether you need a different kind of hosting, not only a different company. If the old site was slow because the plan was too small, the comparison in how renting a Minecraft server explains web hosting plans helps you size the new one. After the move, set up monitoring right away so you hear about any trouble before customers do; the guide on uptime monitoring and game health bars takes about twenty minutes to follow.
If you are planning a move this month, do just step one today: lower the TTL to 300 seconds. It costs nothing, changes nothing visible, and makes every later step safer.
FAQ
How long does it take to move a website to a new host?
For a small WordPress site, the copying takes one to three hours and the switch itself under thirty minutes, if the TTL was lowered beforehand.
Will my Google rankings drop after changing hosts?
Not if the domain, page addresses and content stay the same and the site stays online. A faster new host can help slightly.
What is DNS TTL?
The number of seconds that resolvers may cache your domain's address. Lowering it before a move makes the change take effect quickly.
Do I need to move my domain when I change hosts?
No. The domain can stay with your registrar; you only change the DNS records to point at the new server.
More from the blog
WordPress Care
Questions to Ask Before Hiring Someone to Maintain WordPress
Most small business owners hire WordPress help the same way: a cousin recommends someone, the price sounds fair, and the first...
Games
What Online Game Health Bars Teach About Uptime Monitoring
In Valheim, when your character gets hungry, cold or wet, small icons appear in the corner of the screen long before your...
Games
What Budget Phone Gamers Teach Shops About Lightweight Sites
Walk past any tea stall in Dhaka in the evening and you will see someone playing Free Fire or PUBG Mobile on a phone that cost...