Moving a WordPress website to a new hosting provider is often a smart way for a business, blogger, or agency to improve speed, reliability, support, and scalability. However, a successful migration involves more than copying files from one server to another. The domain, DNS records, and SSL certificate must all be handled carefully so visitors can reach the site securely without downtime or warning messages.
TLDR: A WordPress migration works best when the site files, database, domain settings, DNS records, and SSL certificate are planned in the correct order. For example, a small online store moving from shared hosting to managed WordPress hosting may reduce average page load time from 4.2 seconds to 1.8 seconds, but only if DNS and SSL are configured properly. The site owner should back up the site, test it on the new host, update DNS, and verify HTTPS before considering the move complete.
What Happens During a WordPress Host Migration?
A WordPress website has two main technical parts: files and a database. The files include themes, plugins, uploads, and the WordPress core. The database stores posts, pages, settings, users, comments, product data, and other dynamic content.
When a site is moved to a new host, both parts must be transferred. The new host must then be told how to serve the site under the correct domain name. If the domain and DNS settings are not updated correctly, visitors may still land on the old server, see an error page, or experience mixed security warnings.
Step 1: Prepare a Full Backup
Before any migration begins, a full backup should be created. This includes the WordPress files, the database, email records if relevant, and configuration files such as wp-config.php. A backup protects the site owner if something goes wrong during the transfer.
A migration is much safer when the old hosting account remains active until the new site has been tested. The site owner should avoid canceling the old hosting plan immediately, because DNS propagation can take time and rollback may be needed.
- Files: Themes, plugins, uploads, and WordPress core files.
- Database: Posts, pages, settings, users, and WooCommerce data.
- Configuration: PHP version, server rules, redirects, and caching settings.
- Email details: MX records and mailbox settings, if email is connected to the domain.
Step 2: Move WordPress Files and Database
The migration itself can be done manually, through a hosting control panel, with command-line tools, or by using a migration plugin. Many new hosting providers also offer free migration services, especially for WordPress websites.
In a manual migration, the site files are uploaded to the new server, and the database is imported into a new database on that server. The wp-config.php file must then be updated with the new database name, database user, password, and host.
After the files and database are in place, the site should be tested before the public DNS is changed. Many hosting providers offer a temporary URL or staging link. Another option is to edit the local hosts file on a computer so the domain temporarily points to the new server only for testing.
Step 3: Understand the Domain’s Role
The domain name is the human-readable address of the website, such as example.com. It is usually registered through a domain registrar, which may be separate from the hosting company. The domain does not physically contain the website; it points visitors to the server where the site is hosted.
During a migration, the domain can stay with the same registrar. The site owner usually does not need to transfer the domain registration to the new host. In many cases, only the DNS records need to be updated. This approach is often cleaner because the domain remains independent from hosting.
If the domain is also transferred to a new registrar, that process is separate from the website migration. A registrar transfer can take several days and may temporarily lock certain domain settings. For this reason, many professionals prefer to migrate the website first and transfer the domain later, if necessary.
Step 4: DNS Explained
DNS, or Domain Name System, works like the internet’s address book. It tells browsers where a domain should go. When someone enters a domain name, DNS records point that request to the correct web server, mail server, or other service.
The most important DNS records during a WordPress migration are:
- A record: Points the domain or subdomain to an IPv4 address.
- AAAA record: Points the domain to an IPv6 address, if used.
- CNAME record: Points one hostname to another hostname, often used for www.
- MX record: Controls email delivery for the domain.
- TXT record: Used for verification, security, SPF, DKIM, and other services.
For many WordPress moves, the main task is updating the A record for the root domain and possibly the CNAME for the www version. If the site uses a content delivery network, DNS may point to the CDN instead of directly to the hosting server.
Nameservers vs DNS Records
There are two common ways to point a domain to a new host. The first is to change the domain’s nameservers to the new host’s nameservers. The second is to keep the existing DNS provider and update individual DNS records.
Changing nameservers gives the new host control over DNS management. This can be simple, but it may overwrite or disrupt existing records if they are not copied correctly. Updating individual records is more precise and is often preferred when the domain already has email, verification, analytics, or third-party services configured.
For example, if a company uses Google Workspace or Microsoft 365 for email, its MX records must remain unchanged. Accidentally replacing DNS zones during migration can break business email even if the website itself works properly.
Step 5: DNS Propagation and Downtime
After DNS is updated, changes do not always appear everywhere instantly. The update must propagate across internet service providers and DNS resolvers. This can take from a few minutes to 48 hours, although many changes are visible much faster.
To reduce downtime, the site owner can lower the DNS TTL, or time to live, before migration. A lower TTL tells DNS resolvers to refresh the record more frequently. For example, reducing TTL from 24 hours to 300 seconds one day before migration can make the final switch faster.
During propagation, some visitors may see the old server while others see the new one. This is why both hosting accounts should remain active until traffic clearly reaches the new server.
Step 6: SSL and HTTPS Explained
SSL certificates allow a website to load securely over HTTPS. Without SSL, browsers may show a “Not Secure” warning. For eCommerce, memberships, lead forms, and login pages, HTTPS is essential.
After moving to a new host, the old SSL certificate usually cannot simply be reused unless it was manually installed and the private key is available. Most modern hosts offer free SSL through services such as Let’s Encrypt. The certificate should be issued after the domain points to the new server, because the SSL provider must verify that the domain is correctly connected.
Once SSL is active, the WordPress site should force HTTPS. This can be done through hosting settings, WordPress configuration, or redirects. The site should also be checked for mixed content, which occurs when a secure page loads images, scripts, or stylesheets over insecure HTTP links.
Final Checks After Migration
After DNS and SSL are working, the site owner should perform a complete review. Important pages should load correctly, forms should send messages, checkout pages should work, and admin login should be accessible. Broken links, missing images, caching problems, and redirect loops should be resolved before the old hosting account is closed.
- Confirm the domain loads from the new server.
- Check both www and non-www versions.
- Verify HTTPS and browser padlock status.
- Test contact forms, search, login, and checkout.
- Review email delivery and DNS records.
- Update caching, CDN, and security plugin settings.
FAQ
How long does it take to migrate a WordPress site to a new host?
A simple WordPress site can often be migrated in a few hours. Larger sites, WooCommerce stores, membership platforms, or websites with custom server settings may take longer, especially if testing is required.
Will the domain need to be transferred to the new host?
No. The domain can usually stay with the current registrar. In most cases, only DNS records or nameservers need to be updated to point the domain to the new hosting server.
Can a WordPress migration happen without downtime?
Near-zero downtime is possible when the site is copied first, tested on the new server, and DNS is switched only after everything works. Keeping the old host active during propagation also reduces risk.
Why is SSL not working immediately after migration?
SSL may not work until DNS points to the new server and the certificate is issued successfully. Propagation delays, incorrect DNS records, or mixed content can also cause HTTPS issues.
What should be checked before canceling the old hosting account?
The site owner should confirm that the domain resolves to the new host, SSL works, email remains functional, forms submit correctly, and all key pages load without errors.
