Moving a WordPress site to a new hosting provider can improve speed, security, uptime, and overall reliability. However, a migration can also cause broken links, missing files, email disruption, database errors, or lost traffic if it is handled without a clear plan. A careful checklist helps a site owner, developer, or agency move the website with less risk and more confidence.
TLDR: A successful WordPress hosting migration starts with preparation, including backups, access checks, plugin reviews, and performance benchmarks. The site owner should copy all files and the database, test the migrated site before changing DNS, and confirm that SSL, email, redirects, and caching work correctly. After launch, the website should be monitored closely for errors, speed issues, and search visibility changes.
1. Review the Reason for Switching Hosts
Before any technical work begins, the site owner should confirm why the migration is necessary. Common reasons include slow loading times, limited server resources, poor customer support, frequent downtime, weak security, or the need for better scalability. Understanding the reason helps determine what type of hosting environment is best suited for the website.
For example, a small blog may only need managed WordPress hosting, while a WooCommerce store may require a stronger VPS, cloud server, or dedicated hosting plan. The new provider should offer enough storage, bandwidth, PHP memory, database capacity, backup options, and security features for current and future needs.
2. Audit the Existing WordPress Website
A complete audit gives the migration team a clear view of what must be moved. The website may include themes, plugins, media files, custom code, user accounts, comments, form entries, analytics scripts, tracking pixels, and ecommerce records. Missing any of these items can create serious problems after the move.
- Check WordPress version: The site should run a supported version of WordPress.
- List active plugins: Any outdated, abandoned, or unnecessary plugins should be reviewed.
- Check theme files: Custom theme edits should be identified before migration.
- Review file size: Large media libraries may require extra transfer time.
- Document integrations: Payment gateways, CRMs, email marketing tools, and analytics platforms should be noted.
This audit also helps remove clutter before the site is copied to the new server. A cleaner website is usually easier to migrate and maintain.
3. Create a Full Backup Before Making Changes
A full backup is the most important safety measure in any WordPress migration. The site owner should make sure both the website files and the database are backed up. Files include themes, plugins, uploads, and core WordPress files. The database contains posts, pages, comments, settings, users, product data, and many plugin records.
Backups can be created through a hosting control panel, SSH, phpMyAdmin, a migration plugin, or a dedicated backup service. Ideally, at least two backups should be stored in different locations, such as local storage and cloud storage. The backup should also be tested, because a corrupt backup may not be useful during an emergency.
4. Prepare the New Hosting Environment
The new hosting account should be configured before the website is transferred. This reduces downtime and avoids rushed changes at launch. The hosting environment should support the required PHP version, MySQL or MariaDB version, SSL certificates, cron jobs, file permissions, and caching systems.
The site administrator should also create a new database and database user if the migration is manual. For managed WordPress hosting, the provider may create a staging area or temporary domain for testing. Server settings such as upload limits, memory limits, and execution time may need to be adjusted for larger sites.
- Confirm PHP compatibility with the current WordPress version, theme, and plugins.
- Set up SSL before or immediately after launch.
- Create SFTP or SSH access for secure file transfer.
- Check server location based on the main visitor audience.
- Review backup features offered by the new host.
5. Lower DNS TTL Before Migration
DNS changes can take time to spread across the internet. To reduce the waiting period, the site owner should lower the DNS TTL value before migration. TTL, or time to live, tells networks how long to cache DNS records. A lower value, such as 300 seconds, may help the domain point to the new host faster after launch.
This step should be completed at least several hours before the final migration, and preferably one day in advance. Once the website is stable on the new host, TTL can be increased again to a normal value.
6. Choose the Migration Method
There are several ways to migrate a WordPress site. The best choice depends on the site size, technical skill level, and hosting provider support. Some hosts offer free professional migration services, which can be a convenient option for business owners. Others provide automated migration plugins or one-click tools.
- Host-assisted migration: The new hosting provider moves the website on behalf of the customer.
- Plugin-based migration: A WordPress migration plugin packages the site and restores it on the new server.
- Manual migration: Files are transferred through SFTP or SSH, and the database is exported and imported manually.
- Staging migration: The site is moved to a temporary environment first, then pushed live after testing.
Manual migration gives more control, but it requires more technical care. Plugin-based migrations are easier, but very large websites may hit server limits. A professional or host-assisted migration is often best for ecommerce, membership, or high-traffic websites.
7. Transfer Files and Database Carefully
During the transfer, every WordPress file must be copied to the new server. This includes the wp-content folder, uploads, themes, plugins, and any custom files outside the default WordPress structure. The database should be exported from the old host and imported into the new database.
After the database is imported, the wp-config.php file must be updated with the new database name, username, password, and host. If the domain name stays the same, few URL changes may be needed. If the migration also includes a domain change, a careful search and replace process is required to update URLs without damaging serialized data.
8. Test the Website Before Updating DNS
Testing before launch is one of the best ways to prevent public errors. The site can often be tested through a temporary URL, staging domain, or local hosts file modification. This allows the administrator to view the new server version while visitors still see the old website.
The tester should browse the homepage, blog posts, contact forms, checkout pages, login pages, search results, menus, images, downloads, and admin dashboard. Forms should be submitted, ecommerce transactions should be tested in sandbox mode, and user registration should be verified if applicable.
- Check page layout across desktop, tablet, and mobile views.
- Confirm media files load correctly.
- Test internal links and navigation menus.
- Verify plugin features such as forms, sliders, popups, and memberships.
- Review error logs for PHP warnings or database issues.
9. Update DNS and Point the Domain to the New Host
Once testing is complete, the domain can be pointed to the new hosting provider. This usually involves updating nameservers or changing the A record to the new server IP address. The exact process depends on where the domain is registered and how DNS is managed.
During DNS propagation, some visitors may reach the old server while others reach the new one. For websites that receive frequent content updates, such as ecommerce stores or news sites, a short content freeze may be necessary. This prevents new orders, comments, or posts from being created on the old server after the final database copy.
10. Configure SSL, Security, and Redirects
After the domain points to the new host, SSL should be checked immediately. The website should load with HTTPS, and there should be no mixed content warnings. If images, scripts, or stylesheets still load through HTTP, they should be updated.
Security settings should also be reviewed. File permissions, firewall rules, malware scanning, login protection, and backup schedules should be enabled. If the old site used custom redirects in an .htaccess file or server configuration, those redirects must be copied or recreated on the new host.
11. Rebuild Caches and Check Performance
A migration is a good time to improve website performance. After launch, the administrator should clear old caches and rebuild new ones. This includes WordPress cache plugins, server cache, CDN cache, browser cache settings, and object cache if used.
Performance testing should compare the new host against the old baseline. Key metrics include loading time, server response time, Core Web Vitals, image delivery, database response, and checkout speed. If the website is slower than expected, the hosting provider may need to adjust PHP workers, memory limits, caching rules, or CDN settings.
12. Verify SEO and Analytics Settings
Search visibility can be affected if URLs, redirects, metadata, or indexing settings change during migration. The site owner should confirm that SEO plugins are active, XML sitemaps are working, robots.txt is correct, canonical tags are intact, and important pages are indexable.
Analytics and tracking tools should also be tested. Google Analytics, Google Search Console, advertising pixels, conversion tracking, and heatmap scripts should continue collecting data after the move. Search Console can also help identify crawl errors, indexing issues, and broken pages after launch.
13. Monitor the Site After Migration
The migration process does not end when the website loads on the new host. The first 24 to 72 hours are especially important. The site owner should monitor uptime, server logs, contact form submissions, sales, user logins, and page speed. Any issue should be documented and fixed quickly.
The old hosting account should not be canceled immediately. It is safer to keep the old server active for at least one to two weeks, depending on the complexity of the website. This provides a fallback option if missing files, old emails, or database records are discovered later.
Final Pre-Launch and Post-Launch Checklist
- Full backup created and stored safely.
- New host prepared with correct PHP, database, SSL, and access settings.
- DNS TTL lowered before launch.
- Files and database transferred completely.
- wp-config.php updated with new database credentials.
- Website tested on the new server before DNS change.
- DNS updated to point to the new hosting provider.
- SSL and redirects checked after launch.
- Caching and performance reviewed after migration.
- SEO, analytics, and tracking verified.
- Old hosting retained temporarily as a safety backup.
FAQ
How long does a WordPress migration usually take?
A simple WordPress migration may take one to three hours, while a large ecommerce or membership site may require several hours or even a full day. DNS propagation can add extra waiting time, although lowering TTL can reduce delays.
Will a WordPress migration cause downtime?
A well-planned migration can usually be completed with little or no downtime. Testing the site on the new server before updating DNS is the best way to prevent visible disruption.
Should the old hosting account be canceled right after migration?
No. The old hosting account should remain active for at least one to two weeks. This gives the site owner time to recover missing files, compare data, or roll back if a serious issue appears.
Can a WordPress migration affect SEO?
Yes, it can affect SEO if pages break, redirects are missing, HTTPS fails, or important pages become blocked from indexing. When URLs remain the same and technical settings are preserved, rankings are usually not harmed.
Is a migration plugin enough for moving a WordPress site?
A migration plugin is often enough for small and medium websites. However, large sites, WooCommerce stores, multisite networks, and custom applications may need manual migration or professional support.
What is the most important step in a hosting migration?
The most important step is creating and verifying a complete backup before any changes are made. A reliable backup protects the website if the transfer fails or data is lost.