Published 5 October 2026

Moving a WordPress website to a new hosting provider does not require a new WordPress installation if you are keeping the same domain and URLs. The safer approach is to copy the site files and database, test the new copy before changing DNS, and keep the old hosting active until the new site and email have been checked.

This guide is for site owners changing hosting infrastructure while keeping their public URLs the same. If you are changing your domain or page URLs as well, you will also need a URL mapping and redirects; that is a different kind of site move.

Before the move: know what must be transferred

A WordPress site has two essential parts: its files and its database. Files include WordPress itself, themes, plugins, uploads and configuration files. The database holds content and settings. A copy of only one part may not produce a working, current site.

For an active ecommerce site, the database can change while files are being copied. Agree a short content or order freeze, or use a migration process that accounts for changes made during the move. Otherwise, the new copy may miss recent orders or customer updates.

Copy the site and test it before changing DNS

Your migration method depends on the hosting control panel and the access available. A cPanel account transfer may be possible when the providers support it; otherwise, a migration tool or a careful manual transfer may be used. WordPress’s official migration guidance also calls for transferring both the site files and database, and updating configuration if database details change.

  1. Copy the files and export the database. Confirm the backup is complete and readable before relying on it.
  2. Create or import the database on the new account. Record its database name, user and password, then update wp-config.php if those details differ from the old account.
  3. Test the new copy using a temporary method. Use a provider-supported preview or hosts-file test where available. Check the homepage, several internal pages, images, login, forms and any important checkout flow.
  4. Check HTTPS and WordPress settings. Confirm the site loads securely, the WordPress and Site Address settings are expected, and permalinks work. Do not replace the live site’s URLs with a temporary testing hostname.
  5. Remove launch-only restrictions. If the test copy was blocked from crawling or set to noindex, make sure those restrictions will not remain on the live site after launch.

Do not cancel the old hosting account just because the new copy loads on your computer. DNS caches can send visitors to either location for a period after a change, so the old account may still receive visits or email.

Switch DNS carefully, including email records

DNS is the system that directs a domain to services such as a website or mail server. The website’s A or AAAA records and email’s MX records serve different purposes. Changing nameservers or copying a DNS zone without checking its contents can unintentionally affect business email or other services.

  1. Review the current DNS zone. Record the website records, MX records and any important TXT or CNAME records used for email verification, security or third-party services.
  2. Confirm where email should go. If email remains with a separate mail provider, preserve its MX records and related settings. If email is moving too, verify mailboxes and routing on the new service before switching.
  3. Change only the intended DNS settings. Follow the instructions from the domain or DNS provider. If practical, lowering the relevant record’s TTL ahead of the move can help cached records refresh sooner, but it does not make propagation instantaneous.
  4. Test from more than one connection. Open the site on mobile data and another network, check that HTTPS works, and send and receive test emails if mail settings were involved.

After launch: verify before closing the old account

Keep both hosting accounts available while DNS changes are taking effect. Google notes that a temporary change in crawl rate can occur after a hosting change; monitor Search Console and check that Google can access the new hosting. A short-lived crawl fluctuation is not by itself proof that the migration failed.

When migration assistance is useful

A straightforward site with stable content may be manageable by its owner. Professional help is worth considering when the site handles orders, has a large database, uses WordPress Multisite, depends on custom server settings, or needs email moved at the same time. Ask whoever performs the move to explain what will be copied, how the new version will be tested, how DNS and email will be handled, and how the old account will be retained during the transition.

HostCupid Web Solutions Private Limited, a Chennai-based provider operating since 2018, offers hosting and website migration assistance. If you are considering a move, compare the migration plan and the hosting resources with your site’s needs; no provider can guarantee a search ranking outcome from a hosting change alone.


Sources

Portrait of Ananya Krishnan, HostCupid editorial persona
Published by
Ananya Krishnan

HostCupid Editorial Team

Writes practical guides on web hosting, WordPress, website migrations and day-to-day website operations for Indian businesses.

Editorial persona representing the HostCupid content team.

← More HostCupid Insights