Guides · Migration · 3 November 2026 · 6 minute read

How to move a website to a new host with no downtime

Illustration: black moving boxes on a trolley, one of them red

To move a site without downtime, copy everything to the new host while the old one keeps serving visitors, test the copy privately, lower your DNS TTL beforehand, then change DNS at a quiet hour. Keep the old account running for several days so you can roll back, and treat email as a separate cutover.

Most hosting moves go wrong for one of three reasons. Someone changes DNS before the new site is tested, email stops arriving, or data created during the move is lost. Each is avoidable with a plan and a calm order of operations.

This guide assumes a cPanel-to-cPanel move, which is the most common case. The principles apply to other setups.

The principle

The old host and the new host can both serve your site at the same time. Visitors reach whichever one DNS points to. If you build and test the copy while DNS still points to the old server, nobody sees a gap. The switch is one change, made at a quiet hour, with the old server still running as a fallback.

Before you start: the inventory

List what is on the old account.

  • Websites and their folders, including add-on domains and subdomains.
  • Databases and their users.
  • Email accounts, forwarders, auto-responders and filters.
  • DNS records: A, CNAME, MX, TXT for SPF, DKIM and DMARC, and anything else.
  • Cron jobs, and any scripts that run on a schedule.
  • SSL certificates, and which are installed manually.
  • Anything outside the site: payment gateways, API keys tied to your server’s IP address and firewall allowlists.

Most surprises come from items outside the website folder. Check the DNS zone carefully, because that is where forgotten services hide.

Step 1: Choose the window

Pick a low-traffic time. For many Singapore businesses that is early morning or a weekday evening. Avoid Fridays and public holidays, because if something needs fixing you want the support team of both hosts to be at work. Zension’s support runs Monday to Friday, 9am to 6pm SGT, so a Tuesday to Thursday cutover leaves you a working day on either side.

For a shop, pause or freeze orders for a short period, or plan how you will reconcile orders placed during the move.

Step 2: Take a full backup

Make a complete backup of the old account and download it to a place you control. Include files, databases and email. Do this even if the new host will copy the account for you. A backup you hold is your last line of defence.

Step 3: Lower the TTL

Find the DNS TTL on your A record and any record you will change. Reduce it to a short value, such as 300 seconds, at least a day before the switch. The old, longer TTL must expire first, so lowering it on the day does nothing. After the move, raise it again.

Step 4: Copy to the new host

Set up the new account and copy:

  1. Files. Use the host’s account transfer tool if there is one, or download and upload.
  2. Databases. Export from the old server and import to the new, then create matching database users. Update configuration files with new credentials if they differ.
  3. Email. Create the mailboxes, then copy messages using an IMAP sync tool so that old mail appears in the new accounts.
  4. Cron jobs and settings. Recreate scheduled tasks and PHP settings.

If your provider performs the migration, ask for a written list of what will be moved and what will not. Zension’s engineers migrate sites at no charge, one site on Essential, up to five on Business and up to 15 on Corporate. Our website migration page explains the process.

Step 5: Test the copy before DNS changes

You can view the new copy while the world still sees the old one by editing the hosts file on your own computer. It overrides DNS for your machine only.

  1. Find the new server’s IP address in the welcome email or control panel.
  2. Add a line to your hosts file that maps your domain to that IP.
  3. Open the site in a private browser window and test it thoroughly.
  4. Remove the line afterwards.

Test with a checklist:

  • Home page, key pages and images.
  • Forms, and that the email they send arrives.
  • Login and admin areas.
  • Checkout, with a test order if you have a shop.
  • Redirects and error pages.
  • Sitemap and robots file.

If a page works only on one host, find out why now.

Step 6: Prepare email

Email is the part that can lose messages, so handle it deliberately.

  • Lower the TTL on your MX records too.
  • Create the mailboxes and copy existing mail before the switch.
  • Check SPF, DKIM and DMARC records for the new sending server. Mail from a new IP can be rejected if these are missing or wrong.
  • Decide whether mail and website move at the same moment. Splitting them can be safer: move the website first, confirm it is stable, then move mail.

See our email comparison if you are considering changing where email lives at the same time.

Step 7: Switch DNS

At the quiet hour:

  1. Take a final backup of the old site, and for a dynamic site, put it into read-only or maintenance mode for a few minutes.
  2. Copy any changes made since your first copy: new orders, comments, uploads.
  3. Change the A record, or the nameservers, to the new server’s details. If you use the old host’s DNS, copy every record to the new zone first.
  4. Check the site from several networks, including a mobile connection.
  5. Watch the access logs on both hosts as traffic moves across.

A short TTL means most visitors reach the new server within minutes. A few resolvers may be slow, which is why the old account stays live.

Step 8: Check the certificate

HTTPS certificates are usually issued automatically once the domain resolves to the new server. Confirm that the padlock shows and that there are no mixed content warnings. If you use an organisation validated certificate, make sure it is installed on the new host. Our ssl certificates page lists the options.

Step 9: Post-move checks

Work through this list on the day and again after a week.

  • Contact form and order emails arrive.
  • Mail sends and receives on phones and desktop clients.
  • Scheduled tasks run.
  • Backups are running on the new host.
  • Google Search Console and analytics show no spike in errors.
  • Payment gateway callbacks succeed.

Step 10: Keep a rollback

If something breaks, change the DNS record back to the old IP. The short TTL means that takes minutes to spread. This is why the old account must stay active and unchanged. Do not cancel it, delete files or let it expire until the new host has run cleanly for at least a week.

What can go wrong

  • Data written during the move. Orders and sign-ups made on the old site after your copy are missing from the new one. Freeze, or reconcile.
  • Hard-coded IP addresses. Some integrations rely on your server’s IP address and need updating.
  • Forgotten subdomains. Staging sites, webmail aliases and old campaign pages disappear if you do not copy them.
  • Mail from the wrong place. Email from a new IP can land in spam until SPF and DKIM are right.
  • Expired domain. Check your domain’s renewal date. A migration is a poor time to lose it. Our domain requirements guide covers keeping the registration safe.

When to get help

If the site takes orders, handles email for a team or has complicated integrations, have the new host do the work and review their plan. A good provider will describe the same steps in this guide, with a named engineer.

How Zension handles it

Migration by our engineers is free. We copy your site, test it on our servers before DNS changes, and agree the cutover time with you. See website migration or our web hosting plans for details.

Quick answers

Is zero downtime really possible?
Yes for a website, because the old and new servers both serve the site until DNS changes. The risk is in data that changes during the move, such as orders and form entries, which needs a plan.
How long should I wait before cancelling the old host?
Keep it for at least a week after the switch, longer if mail is involved. Cancel after you have confirmed that DNS, email, forms and scheduled jobs all work on the new host.
What is a DNS TTL?
TTL, or time to live, is how long resolvers may cache a DNS record. A short TTL such as 300 seconds means a change spreads faster.
Do I need to move my domain registration too?
No. You can change where the website and email are hosted by editing DNS, while the domain stays with its current registrar. Moving the registration is a separate decision.

Written by the engineering team at Zension Private Limited, a Singapore web hosting company since 2007. Corrections are welcome at enquiry@zension.com.

Website migration

Hosted in Singapore, moved in by our engineers, and renewed at the price you signed up at.

Find out more