Moving a WordPress website to a new host, domain, or server is one of those tasks that sounds straightforward until you realise your organic traffic is on the line. Get it right and your site loads faster, runs more securely, and keeps every hard-earned ranking. Get it wrong and you could spend months clawing back lost visibility.
This guide walks you through the entire WordPress migration process, from pre-migration planning to post-launch monitoring, with a focus on protecting your search engine rankings at every step.
Overview
- A WordPress website migration can involve switching hosting providers, moving to a new domain, redesigning your theme, or restructuring URLs. Each scenario carries distinct SEO risks that require different safeguards.
- Whether you migrate a WordPress site manually or use a backup plugin, SEO planning around redirects, testing, and timing is what actually protects rankings.
- A complete backup of all WordPress files, database tables, and wp-config.php from the old site is non-negotiable before you touch anything on the live server.
- Updating internal URLs, implementing 301 redirects, and thoroughly testing on the new server before DNS changes are critical steps to avoid traffic loss.
- Cude Design offers done-for-you WordPress site migration and managed hosting for UK businesses that need zero downtime and preserved SEO.
Why Plan a WordPress Website Migration Carefully?
A WordPress website migration is any major move involving your existing site. That could mean switching to a new web host, spinning up a new server, moving to a new domain, or launching a completely redesigned WordPress installation. Some businesses do all of the above at once, which significantly multiplies risk.
UK businesses are migrating more frequently than ever. Common triggers include slow shared hosting that slows page load times, recurring downtime, poor customer support, security vulnerabilities, or a full rebrand that requires a new domain. Many are also moving from legacy platforms or heavyweight page builders to leaner, faster setups running modern PHP 8.x.
The SEO risk is real. Search rankings can drop sharply if old URLs return 404 errors instead of redirecting, if the site goes offline during a Google crawl window, or if canonical tags and tracking scripts are misconfigured on the new server. According to industry data, using the wrong redirect type (302 instead of 301) can delay ranking recovery by 6 to 18 months.
At Cude Design, we have handled migrations for over 100 UK businesses across 15+ years. This article reflects a practical, agency-side process rather than textbook theory.
Pre-Migration SEO & Technical Checklist
Before you download a single PHP file or touch any site files, work through this checklist:
- Schedule wisely. Run the WordPress migration during low-traffic hours. For UK audiences, late evening or early Sunday morning minimises disruption. Keep the old site live as a rollback option for at least 7 to 14 days.
- Benchmark current performance. Export keyword rankings, top landing pages, impressions, and clicks from Google Search Console and Google Analytics 4. You will compare these figures post-migration to spot problems early.
- Crawl the existing site. Use a crawler like Screaming Frog to capture every URL, status code, canonical tag, and internal link. This crawl forms the foundation of your redirect map, especially if the migration involves a new domain or changes to the URL structure.
- Audit robots.txt, XML sitemaps, and canonical tags. Document any noindex rules or custom directives so they can be replicated on the new WordPress installation.
- Lower DNS TTL. At your domain registrar, reduce the TTL value (e.g. to 300 seconds) at least 48 hours before the switch. This shortens the propagation window when you finally point DNS to the new host.
- Confirm rollback plan. Know exactly how you will revert if something goes badly wrong.
Backing Up Your Old WordPress Site Safely
No migration should begin without a verified, complete backup of your current WordPress site. If something breaks mid-transfer, this backup is your insurance against data loss.
What to back up:
- The entire WordPress files directory, including wp-content (themes, plugins, uploads and media files), WordPress core files, and the htaccess file.
- The full MySQL database, exported as a SQL file containing all database tables, including plugin-specific tables.
- Your wp config.php file, which holds database credentials, authentication salts, and environment-specific settings.
Two approaches:
| Method | Best for | Tools |
|---|---|---|
| Manual backup | Developers, complex sites | FTP client (e.g. FileZilla) + phpMyAdmin |
| Plugin backup | Non-technical users, smaller sites | UpdraftPlus, Duplicator, WPvivid Backup Plugin |
Whichever method you choose, store at least two copies of every backup file: one on your local workstation and one in cloud storage. A simple 3-2-1 backup rule covers you against hardware failure, accidental deletion, and corrupted archives.
Before proceeding, test a small restore on a staging or local environment. A backup you cannot actually restore is no backup at all.
Choosing the Right Web Host and New Server Setup
The success of a site migration depends heavily on where you are migrating to. A poor hosting environment will undo all the SEO gains you are trying to protect.
What to look for in a host:
- Fast SSD storage and modern web server architecture (HTTP/2 or HTTP/3)
- PHP 8.x support (ideally 8.2+)
- Free SSL via Let’s Encrypt or equivalent
- Daily automatic backups and easy restore
- WordPress-aware support staff who understand plugin conflicts, caching layers, and database optimisation
- Staging environments for pre-launch testing
For SMEs, a managed WordPress host removes the burden of security hardening, core updates, and performance tuning. This is a significant step up from generic cheap shared hosting, where resources are split across hundreds of accounts.
If you run a WooCommerce store or membership site, the new server must be sized for traffic spikes and heavy database load, not just brochure-site requirements. Consider object caching (Redis or Memcached) and adequate CPU and memory allocation.
Cude Design provides UK-based managed WordPress hosting and can set up the hosting environment, staging, and security hardening before the migration starts.
How to Manually Migrate a WordPress Website (Old Host to New Host)
This section is a step-by-step roadmap for manual migration, aimed at readers comfortable with FTP, phpMyAdmin, and basic server tools. If you prefer a plugin-based approach, skip ahead to the next section.
This process applies to standard single-site WordPress installations. WordPress multisite network migrations are covered in a later section. Follow each step in order: export the database, copy files, create the destination site database, adjust wp-config.php, then make DNS changes and test.
Step 1: Export the Database from the Old Site
Log in to the old host’s control panel (cPanel, Plesk, or equivalent) and open phpMyAdmin. Locate the correct WordPress database, which you can identify from the DB_NAME value in your current site’s wp-config.php.
Select all database tables and choose Export > Quick > SQL. This downloads an SQL file containing all posts, pages, WordPress users, settings, and plugin data.
Name the file with today’s date, for example, site-database-2026-06-09.sql, and save it in your dedicated migration folder. Double-check the file size to confirm it is not empty and that no errors appeared during export.
Step 2: Download All WordPress Files from the Old Server
Open an FTP or SFTP client such as FileZilla. Connect to the old web host using the hostname, username, password, and port provided by your hosting account.
Navigate to the WordPress root directory (commonly public_html, www, or a named subdirectory). Download all the files and folders. The wp-content directory, which contains your WordPress themes, plugins, and media files, is essential, but the safest approach is to download the entire folder structure so nothing is missed.
Once downloaded, compress everything into a single zip file (e.g. site-files-2026-06-09.zip) on your local machine. This makes the upload process to the new server faster and more reliable.
Step 3: Create a New Database on the New Web Host
On the new hosting provider, create a fresh MySQL or MariaDB database along with a database user and a strong, unique password.
In a typical cPanel workflow:
- Create the database.
- Create the database username and password.
- Assign the user to the database with all privileges.
Record these four details carefully: database name, database username, database password, and database host (often localhost, though some hosting providers use a custom hostname). You will need them shortly.
Step 4: Upload Your WordPress Files to the New Server
Connect to the new server via your ftp client and navigate to the correct document root, such as public_html or /var/www/html.
Upload the zip file you created earlier. Then extract it via the host’s file manager or SSH to restore the original directory structure. Delete any placeholder index.html or one-click installer files to avoid conflicts with the migrated WordPress installation.
Large uploads can take several minutes depending on file sizes. Verify that all the files and folder names match your backup before moving on.
Step 5: Import the Old Database into the New Database
Open phpMyAdmin on the new host and select the empty database you just created. Click the Import tab and upload the SQL file exported from the old site.
Ensure the character set and collation match typical WordPress defaults (usually utf8mb4_unicode_ci). Wait for the success message and confirm that all expected tables (wp_posts, wp_options, wp_users, plus any plugin-specific tables) have been created.
Take a quick screenshot of the list of imported tables for your records. This documentation is useful for future troubleshooting.
Step 6: Update wp-config.php for the New Environment
Locate wp config.php in the new server’s WordPress root and open it with a code editor via FTP or the host’s file manager.
Update these four lines to match the new database credentials:
- DB_NAME – your new database name
- DB_USER – your new database username
- DB_PASSWORD – the password you set
- DB_HOST – usually localhost, but check with your new host
Leave the authentication keys and salts intact unless you have a specific security reason to rotate them. Do not alter the table prefix unless you fully understand the implications across all plugin settings and custom queries.
Save a backup copy of the original file (e.g. wp-config-before-migration.php) in case a rollback is needed.
Step 7: Test the Site on the New Server Before DNS Changes
Many hosts provide a temporary URL or staging URL so you can access the new WordPress installation before changing DNS. Use this to browse key pages: homepage, service pages, blog posts, contact forms, and checkout if WooCommerce is installed with WordPress installed on the new server.
Check for:
- Missing images or media files
- Broken menus and navigation
- Plugin errors or white screens
- The correct site URL in WordPress Settings > General
Temporarily disable caching plugins and any CDN integrations during testing. Cached assets from the previous host can give you a false sense that everything is working.
Step 8: Point DNS to the New Web Host
Obtain DNS details from the new host (nameservers or an A record IP address) and update them at your domain registrar.
DNS propagation can take anywhere from a few minutes to 24 hours. During this window, some visitors will see the old site and others the new site. Keep the old site online and unchanged for at least a week after the switch so you have a rollback option.
Monitor server logs and analytics during the first 24 to 72 hours to confirm traffic is flowing to the new hosting server and that there are no major 404 spikes.
How to Use a Backup or Migration Plugin Safely
Not everyone wants to manually migrate a WordPress site. If you are less comfortable with FTP and phpMyAdmin, a migration plugin can handle much of the heavy lifting in just a few clicks.
Popular options:
- Duplicator (free version available)
- All-in-One WP Migration
- WPvivid Backup Plugin
- UpdraftPlus
The general workflow is straightforward: create a backup or migration package on the current site, install wordpress on the new host, install the same plugin there, and import the backup. The plugin handles the database and website files and often automatically runs a search-and-replace on URLs.
However, plugin-based migration has limits. Very large sites with heavy media libraries, complex WooCommerce catalogues, or membership platforms with custom database tables can exceed upload limits or trigger PHP timeouts. Manual migration or agency-led migration is safer for these scenarios.
If your WordPress site is mission-critical and you lack in-house technical expertise, consider a professional migration service like Cude Design. Plugin-related pitfalls and unexpected downtime can cost more than the migration itself.
Protecting SEO During and After WordPress Migration
This is where many website migration projects fall apart. The files transfer fine, the design looks correct, but organic traffic nosedives because SEO signals were not preserved.
Keep URL structures identical where possible. If your current WordPress site uses /blog/post-name/ and the new site defaults to /post-name/, you have just broken every indexed URL. Re-save permalink settings on the new site to match the old structure exactly.
Set up 301 redirects for any URLs that must change. Map old URLs from your crawl export to their new equivalents. Implement redirects via the htaccess file, web server config, or a reputable SEO plugin. Never use 302 (temporary) redirects for permanent moves.
Update internal links and canonical tags. Run a search-and-replace across the site’s database to swap old URLs for new ones, using a tool that safely handles serialised data. Update hreflang tags if you run multiple sites targeting different regions.
Submit updated XML sitemaps to Google Search Console immediately after launch. Monitor coverage reports and crawl errors daily for the first two weeks. If you are moving to a new domain, use the Change of Address tool in Search Console.
Expect minor fluctuations. Industry data shows well-executed migrations recover 80 to 90 per cent of rankings within 4 to 8 weeks. Steep, sustained drops beyond 8 to 12 weeks usually indicate redirect gaps, canonical issues, or broken links that require urgent attention.
Real-world results back this up. Red Band UK saw organic traffic rise approximately 24.8 per cent and revenue increase around 36.7 per cent within two months of migrating from Magento to WordPress, thanks to a full crawl audit and 1,500+ redirects. PeopleShift preserved 100 per cent of organic traffic when moving 500+ pages to a new domain. Le Boat consolidated 22 domains into one WordPress multisite network and saw daily clicks jump 67 per cent in 90 days.
Handling Special Cases: New Domain Names and WordPress Multisite
Some migrations go beyond a straightforward move of a WordPress site from one host to another on the same domain.
Moving to a new domain (e.g. from .co.uk to .com) significantly increases SEO risk. Every backlink pointing to the old domain needs to transfer its equity via 301 redirects. Use the Change of Address tool in Google Search Console to notify Google of the move. Maintain the old domain with active redirects for at least 12 months, ideally longer.
Outdoor Toys migrated from .co.uk to .com and, after an initial dip in visibility, recovered and exceeded pre-migration traffic by over 28,500 monthly sessions.
WordPress multisite network migrations are a different beast entirely. Multiple sites share WordPress core files and a single database with site-specific prefixes. When extracting a single sub-site from a multisite setup, you must export only the relevant site-ID database tables and the correct uploads folder, then adjust internal links and domain mapping.
Consolidating multiple sites into a multisite is equally complex, especially when hreflang, canonical tags, and backlink equity span multiple domains.
Complex WordPress multisite network migrations should be handled by experienced developers or agencies such as Cude Design, particularly when there are many subsites, custom integrations, or multilingual configurations.
Post-Migration Checks, Monitoring, and When to Call in Help
The migration process is not finished when the new site goes live. The first 48 to 72 hours are critical for catching issues before they snowball.
Immediate quality-assurance checklist:
- Test contact forms, login and registration flows, site search, and checkout or payment gateways
- Verify downloadable files, member areas, and email sending from the new server
- Clear all caching layers: plugin cache, server cache, CDN cache
- Re-save permalink settings in WordPress to flush rewrite rules on the new hosting environment
- Check SSL configuration and mixed-content warnings
- Confirm that both www and non-www versions redirect correctly to a single canonical URL over HTTPS
- Review PHP error logs for 500 errors, database connection issues, or deprecated function warnings
Ongoing monitoring (weeks 1 to 6):
- Track keyword rankings and organic traffic in Google Search Console and GA4
- Monitor crawl errors and indexation status
- Watch server performance: response times, uptime, Core Web Vitals scores
- Compare current metrics against the benchmarks you recorded pre-migration
Minor fluctuations in search engine rankings during weeks one through four are normal. If traffic has not begun recovering by week six to eight, audit your redirect map, canonical tags, and backlink status.
If your entire site serves as a lead generation or revenue engine and you would rather not risk any of this, Cude Design offers stress-free WordPress site migration and managed hosting for UK businesses. We handle staging, SEO planning, rollback strategies, and out-of-hours migration windows so your transition is smooth and low-risk. Book a free consultation if you prefer expert handling.
WordPress Website Migration FAQ
How long does a WordPress migration usually take from start to finish?
A simple brochure-style WordPress site can often be migrated in one to three hours, including backup, file transfer, database import, and basic testing. Larger WooCommerce stores, membership platforms, or sites with extensive media files may require a half-day or full-day window.
These timelines include DNS propagation, which can introduce a few hours of overlap during which both the old and new sites may serve visitors. Careful planning and lowered DNS TTL values minimise visible downtime.
Will I lose my Google rankings if I move my WordPress site to a new host?
Switching hosting providers on the same domain with identical URLs rarely causes ranking loss, provided the site remains accessible and loads quickly on the new server. The risk increases substantially when you change URL structures or move to a new domain.
Correct 301 redirects, updated sitemaps, and thorough testing before the DNS switch are the primary safeguards. If you migrate your WordPress site cleanly, most rankings recover within four to eight weeks.
Do I need to reinstall all my themes and plugins after migration?
If you copied all WordPress files correctly, including the full wp-content directory, there is usually no need to reinstall WordPress themes or plugins on the new server. Everything travels with the file transfer.
That said, migration is a good opportunity to audit your plugin stack. Remove anything unused, abandoned by its developers, or flagged as insecure. Update remaining plugins to versions compatible with the PHP version running on your new hosting server.
What about email accounts linked to my old hosting package?
Website migration and email migration are separate processes. Moving your WordPress files and database does not automatically migrate email inboxes, contacts, or settings.
If your email is hosted with your current hosting account, plan the email migration alongside the site move. Many businesses use this as an opportunity to migrate to dedicated email services such as Microsoft 365 or Google Workspace. Make sure the DNS records for MX, SPF, and DKIM are correctly updated at your domain registrar to prevent email delivery interruptions.
When should I ask an agency like Cude Design to handle the migration?
Consider professional help if your site is mission-critical for lead generation or revenue, uses complex integrations (WooCommerce, CRM connections, membership systems), runs on a WordPress multisite network, or lacks in-house technical staff.
An experienced agency like Cude Design can provide staging environments, detailed SEO planning, tested rollback strategies, and out-of-hours server migration windows. The cost of professional migration is almost always less than the cost of lost traffic, broken links, and weeks of recovery caused by a botched DIY move. WP Engine and other managed WordPress hosting platforms also offer migration assistance, but a hands-on agency covers SEO strategy alongside the technical transfer.
