Guide · 7 min read

How to Move Your Website to a New Host Without Downtime (India)

In short

To move a website to a new host without downtime, keep the old hosting active, take a full backup of files, database and email, and set the site up on the new host. Lower your DNS TTL a day ahead, test the new copy through your computer's hosts file, then switch DNS. Cancel the old plan only after everything, including email, works.

Moving to a new host sounds risky, but the method that avoids downtime is simple: build a complete working copy on the new server first, check it privately, and only then point your domain at it. Most migration problems come from doing these steps in the wrong order, such as cancelling the old plan first, or forgetting that email has to move too.

Key takeaways

  • Do not cancel your old hosting until the new site and email have been running smoothly for at least a week.
  • A website is files, a database, email and DNS. Plan each one separately.
  • Lower your DNS TTL a day before, test using your hosts file, and only then switch.
  • Moving hosting does not require transferring your domain. That is a separate, optional step.

Before you start: what a website move involves

A website move has four parts: files, database, email and DNS. Missing any one of them is how sites go down or emails go missing.

PartWhat it includesHow it moves
FilesHTML, images, themes, plugins, uploadsA cPanel backup, or download and upload by FTP or File Manager
DatabaseWordPress posts, pages, users, ordersExport as a .sql file and import on the new host
EmailMailboxes and stored messagesRecreate the accounts, then copy messages over IMAP
DNSWhere the domain pointsChange A records or nameservers at the very end

Also note anything custom: cron jobs, redirects in .htaccess, subdomains, and third-party services tied to the old server, such as an SMTP service or a payment gateway that allows only certain IP addresses. If you are moving because a renewal price jumped, compare renewal prices rather than introductory offers before you choose the new host; our guide to web hosting costs in India explains how.

Step 1: Take a full backup, and check it

Take a complete backup from the old host before you change anything, and keep a copy on your own computer. A backup you have never opened is a hope, not a backup.

  • cPanel to cPanel: a full backup from cPanel's Backup section contains files, databases and email accounts, and can often be restored on the new cPanel server in one go.
  • WordPress: a migration plugin such as Duplicator, All-in-One WP Migration or UpdraftPlus packages files and database together. Check the free version's size limits before relying on it.
  • Manual: download public_html by FTP or File Manager, and export each database from phpMyAdmin as a .sql file.

Check that the ZIP opens and that the .sql file is not empty. If your old provider offers only a site builder with no cPanel access, ask them for an export early. Some builders cannot export a usable site at all, in which case the honest answer is a rebuild.

Step 2: Lower your DNS TTL a day ahead

Lower the TTL (time to live) on your domain's A and MX records to 300 seconds at least 24 hours before the move. Networks then re-check your DNS every five minutes instead of holding on to the old address for hours.

The TTL is set in your DNS zone, wherever your DNS is currently managed, usually at the old host or at your domain registrar. If the TTL is currently 86400 (one day), the new value only takes effect once the old one has expired, which is why you do this a day early. You can set it back to a normal value after the move.

One limitation: if you change nameservers rather than records, your TTL setting does not control the switch. Nameserver changes depend on the domain registry and can take 24 to 48 hours to settle everywhere. For the smoothest move, keep DNS where it is and change only the A record, or make sure the old and new hosts both serve the same working site during the changeover.

Step 3: Set up the site on the new host

Recreate the site on the new hosting exactly as it was: the same files, the same database contents and the same PHP version.

  1. Add the domain to the new hosting account. It is usually the main domain you signed up with.
  2. Upload the files into public_html.
  3. Create a new database and database user, then import the .sql file through phpMyAdmin.
  4. For WordPress, update wp-config.php with the new database name, user and password. The site address stays the same because the domain is not changing.
  5. Set the PHP version to match the old host. Upgrade PHP later as a separate step, so you know which change caused any problem.
  6. Recreate cron jobs, subdomains and email accounts, using exactly the same addresses.

From this point, freeze changes on the old site: no new posts, and for a store, consider a short maintenance window so that no orders land in the old database after you copied it. If the site runs on WordPress, this is also a good moment to check the plan size: most WordPress sites suit our Linux 2 GB cPanel plan, and a busy WooCommerce store may want Linux Gold (5 GB).

Step 4: Test the new site using your hosts file

Your computer's hosts file lets you see the site on the new server, at your real domain, before anyone else does. You add one line that maps your domain to the new server's IP address, and only your computer follows it.

  • Windows: open Notepad as Administrator and edit C:\Windows\System32\drivers\etc\hosts.
  • Mac and Linux: run sudo nano /etc/hosts in Terminal.

Add a line such as 203.0.113.10 yourbusiness.in www.yourbusiness.in, using the IP address from your new hosting welcome email. Save the file, restart the browser and test every important page: the home page, contact form, login, checkout, search and image-heavy pages. The browser may show a certificate warning at this stage because SSL has not yet been issued on the new server; that is expected. Remove the line when you have finished testing.

Step 5: Switch DNS and watch both servers

When the new copy works, change the A record (or nameservers) to point at the new server. With a 300-second TTL, most visitors move over within minutes to a few hours.

  • Issue the free SSL certificate on the new host as soon as the domain points there. In the usual setup, Let's Encrypt can only verify your domain after DNS has switched.
  • Keep the old hosting running and unchanged for at least a week, in case anything was missed.
  • Check the site on mobile data as well as office Wi-Fi, since they use different DNS resolvers.
  • If the URLs have not changed, there is nothing to do for SEO. Just watch Google Search Console for crawl errors over the next week.

Moving email without losing messages

Email is the part of a migration that most often goes wrong, because old messages live on the old server and new mail starts arriving at the new one as soon as the MX records change.

  • Create every mailbox on the new host, with the same address, before switching.
  • Copy old messages over IMAP: add both the old and new accounts in Thunderbird or Outlook and drag the folders across, or use an IMAP migration tool if there are many mailboxes.
  • For a few hours after the switch, some mail may still arrive at the old server. Keep the old mailbox reachable and check it before you cancel.
  • Update phones and Outlook with the new incoming and outgoing server settings.
  • If your email runs on Google Workspace or Microsoft 365, leave the MX records alone; only the website moves. If you are changing nameservers, copy every MX, TXT (SPF, DKIM, DMARC) and CNAME record to the new DNS first.

Domain transfer is a separate, optional step

Moving your hosting does not require moving your domain. A domain can stay with its current registrar and point to any host; transferring it is a separate decision you can make later, or never.

If you do want to transfer it, do it after the website move has settled, not on the same day. You will need the domain unlocked and its authorisation (EPP) code from the current registrar, and a domain usually cannot be transferred within 60 days of registration or of a previous transfer. For most extensions, a transfer also adds a year to the registration. If you do decide to move the domain, check the renewal price at the new registrar first; see our domain prices (+ 18% GST).

Want help with the move? Ask us, and we will scope it honestly

If you would rather not do this yourself, we can help move your site. Every site is different, so tell us what you have: WordPress or HTML, a store or not, how many email accounts, and where it is hosted now. We will tell you plainly what is involved, what it would cost, and whether you need a bigger plan or simply the same size somewhere else.

Call or WhatsApp +91-95851-60363 (English, Tamil or Hindi), email info@avancezone.com, or use our contact page. AvanceZone Technology has been hosting websites since 1998, and we would rather you moved once, properly, than twice in a hurry.

Frequently asked questions

Will my website go down when I change hosting?

It does not have to. If you set up and test the site on the new host while the old one is still running, then switch DNS with a low TTL, visitors see either the old copy or the new one, and both work. Downtime usually comes from cancelling the old plan too early or switching before testing.

How long does it take to move a website to a new host?

A small HTML or WordPress site can usually be copied and tested in a few hours. Allow a day beforehand to lower your DNS TTL, and a week afterwards with the old hosting still active. Large stores, many mailboxes or unusual setups take longer and are best switched at a quiet time.

Do I need to transfer my domain when I change hosting?

No. The domain and the hosting are separate. Your domain can stay with its current registrar and simply point to the new host through DNS or nameserver changes. Transferring the domain is optional, and it is best done after the website move is complete and settled, not on the same day.

Will changing hosting affect my Google rankings?

Not if the URLs, content and page speed stay the same, because Google follows the domain, not the server. Avoid changing URLs, design and hosting all at once, keep the old host running until the switch is complete, and check Google Search Console for crawl errors during the following week.

What happens to my emails when I move hosting?

Mailboxes and old messages stay on the old server unless you move them. Create the same addresses on the new host, copy messages over IMAP, update the MX records, and keep checking the old mailbox for a few hours after the switch. If you use Google Workspace or Microsoft 365, leave the MX records alone.

Can I move a WordPress site without a plugin?

Yes. Download the files from public_html, export the database from phpMyAdmin, upload both to the new host, create a new database and update wp-config.php with its details. Migration plugins simply automate these steps. A manual move is often more reliable for large sites, where plugins can hit upload or time limits.

WhatsApp