Website migration · 21 Nov 2026 · 7 min read
Website migration downtime: how to keep it short, or avoid it
Moving a site to a new host does not have to take it offline. The planning around DNS and the order of steps decides how long, if at all, visitors notice.
The short answer
A website can often move with little or no downtime if the new copy is built and tested first, the domain's DNS records are lowered in advance, and the switch is made at a quiet time. DNS changes spread gradually, so some visitors reach the old site for a while. Keep the old host running until the change has settled.
Where website migration downtime comes from
Website migration downtime is the period when visitors cannot reach a working copy of your site during a move. It usually comes from one of three places: the new site is not ready when the switch is made, the switch itself is clumsy, or the address system takes time to catch up. Almost all of it can be reduced by preparation, and in many cases a move can happen with no visible outage at all.
It helps to separate two different jobs. The first is copying the site to the new place: files, database, settings and email. The second is pointing the domain at the new place. The copy can take as long as it needs, because visitors are still being served by the old site. Only the second job affects what visitors see, and it can be very quick if you have prepared for it.
The general steps of a hosting move are in our website migration checklist for moving to a new host. This guide concentrates on the outage itself.
Can a site move with no downtime?
Often, yes, with a caveat. Moving a site with no downtime means that at every moment a visitor reaches a working copy, either the old one or the new one. That is achievable for brochure sites and many content sites, because both copies can be identical for the changeover period.
It is harder for sites where data changes constantly. A shop, a booking system or a site with member accounts creates new orders, bookings and sign-ups all the time. If a visitor places an order on the old site just as the new site goes live, the order may exist only on the old copy. For these sites, the usual approaches are to pick a very quiet time, to put the site into a short read-only or maintenance mode while the final data is copied, or to do a final sync of the database right before the switch. The right method depends on how your site stores data, so ask your developer to explain it. If you are deciding between platforms as part of the move, our comparison of custom ecommerce and Shopify explains how the approaches differ.
Be wary of promises of zero downtime with no conditions. A responsible plan says what happens to data during the switch, how long any pause will be, and what will be done if the move has to be reversed.
How do DNS changes cause delays?
DNS is the system that turns your domain name into the address of the server hosting your site. When you move, you change that address. The change does not reach everyone at once, because systems around the internet remember the old answer for a set time before asking again. That time is controlled by a setting on each record, usually called time to live, or TTL.
The practical result is a period, sometimes called propagation, in which some visitors still reach the old server and some already reach the new one. Nothing is broken, but the two groups see two different copies. If the copies differ, because someone published a page or an order arrived on one of them, confusion follows.
The way to shorten the delay is to lower the TTL on the relevant records well before the move. Do this ahead of time, because the old, longer value must expire first. Check your registrar or DNS host's documentation for where the setting lives and what values it accepts. After the switch, the shorter value means most visitors move to the new server quickly. Once the move has settled, you can raise the value again.
Email needs separate attention. Mail records are part of DNS, and if your email is hosted somewhere other than the website, the move must not disturb those records. Our guide to domain renewal and expiry is a helpful companion, since the same registrar settings are involved and a move is a good moment to check them.
A migration order that keeps the outage short
- List what needs to move: site files, database, media, forms, scheduled tasks, email, security certificate and any redirects.
- Lower the TTL on the domain's records in advance, and note the original values so you can restore them.
- Build the new copy at the new host, using a temporary address, and test it fully.
- Freeze changes. Agree a short period in which nobody publishes content or changes settings on the old site.
- Do a final copy of the latest files and data, particularly for sites that receive orders or form submissions.
- Confirm the security certificate is ready on the new host, so the first visitors do not see a warning.
- Change the DNS records to point at the new host, at a quiet time and when someone can watch.
- Keep the old host running, and check both copies, until the change has fully spread.
- Test forms, checkout, email and key pages on the live domain, and check redirects.
- Restore longer TTL values and cancel the old hosting only when you are sure nothing depends on it.
The most common mistake is cancelling the old hosting too soon. Keep it for a safety period, because visitors, search engines and email systems may still touch it, and because it is your quickest rollback if something goes wrong. How long depends on your TTL values and how much the old copy is still used.
Plan for a way back. If the new site fails a test after the switch, you should be able to point the domain back at the old copy in minutes. A plan with no reverse gear is a risk, not a plan.
What should I tell customers?
Tell them what they need to know, no more. If you expect no visible disruption, a message may not be necessary, though staff should know a move is happening so they can report oddities. If there will be a short pause, such as a maintenance period for a shop, say when, how long and what customers should do, and put the notice somewhere they will see it.
A short, plain message works. Say that the site will be unavailable for orders for a stated window on a stated date, apologise briefly, say how to reach you in the meantime and give a time you expect to be back. If you take orders by phone or email in other ways, say so. Avoid technical explanations, because customers want to know what affects them.
Keep the tone, name and look of your communications consistent through the change. A message that looks different from your usual style can seem suspicious. Our guide to brand consistency across channels covers keeping your messages recognisable. For email and social posts, schedule the announcement before the move, then post an update when it is done.
If your move changes addresses, tell search engines through proper redirects and check them. Visitors who follow an old link should arrive at the matching new page, not an error.
After the switch: watch, test and learn
The first day after a move is when problems show. Watch the site from outside your own network, check key pages, submit forms and place a test order if you run a shop. Set up monitoring if you do not have it, using the approach in our guide to uptime monitoring alerts, so that a failure at three in the morning reaches someone who can act.
Check that tracking still works and that search tools still recognise the site. Moves can drop verification files and tracking code without warning, which is why who holds the keys to Search Console and analytics belongs in your migration plan. Look at how search engines see the site over the following weeks, and fix any pages that show errors.
A well-run migration is dull. It follows a plan, has a rollback and ends with a short report. If you want a team to run it, the website development service at Liftup Technologies can look at your current setup and agree a plan. Ask any supplier how they will keep downtime short, what they will do about data during the switch and how they would reverse the move. The answers tell you a lot.
Related guides
- Website development
- Website migration checklist moving to a new host
- Brand consistency how to keep it across channels
- Custom ecommerce website vs shopify
- Website Uptime Monitoring: How to Set Up Alerts
- Analytics and Search Console Access: Who Should Hold the Keys
Questions and answers
Can a website move with no downtime?
Often it can. The new copy is built and tested first, DNS settings are prepared in advance and the switch is made at a quiet time, so visitors always reach a working copy. Sites that take orders or bookings need extra care to avoid losing data during the changeover.
How long does a DNS change take to spread?
It depends on the time-to-live setting on your records and on how other systems cache answers. Lowering the setting before the move shortens the delay. Some visitors may reach the old site for a while, so keep it running until the change has settled.
What should I tell customers about a website move?
If there will be a visible pause, say when it starts, how long it should last, how to reach you meanwhile and when you expect to be back. If no disruption is expected, a notice may not be needed, but tell staff so they can report problems.
Should I cancel the old hosting straight after the move?
No. Keep it for a safety period so you can roll back quickly and so visitors, search engines and email systems still reaching the old address are not left with an error. Cancel only when you have confirmed nothing depends on it.
Will moving hosts affect my email?
It can if your email records are changed by accident. Mail settings live in DNS, so copy them carefully, leave them alone if mail is hosted elsewhere and test sending and receiving after the move.
What if the new site fails after the switch?
Point the domain back at the old copy, which should still be running. That is why a rollback plan and a short DNS time-to-live matter. Fix the problem on the new host, test again and repeat the switch.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.