A carefully planned WordPress site migration can protect your business from slow hosting, unreliable support, or a platform that no longer fits. However, a rushed move can break forms, lose tracking, interrupt email, and damage hard-earned search visibility.
This website migration checklist gives small-business owners a practical route through the change, with clear points where a WordPress professional should take over. The goal is continuity: customers should still be able to find you, enquire, book, and buy.
Key takeaways for a safer website migration
A migration is more than copying pages to a new server. Your website may connect to email, calendars, payment tools, CRM records, analytics, booking systems, and lead follow-up automations.
- Take separate, restorable copies of website files and the database before any change.
- Build and test the new site on a protected staging address before switching DNS.
- Record your important pages, enquiry routes, tracking codes, email settings, and integrations.
- Keep the existing site available until the new version passes real-world tests.
- Use direct 301 redirects if page URLs, a domain, or a site structure changes.
- Monitor Google Search Console, analytics, forms, and email for at least 30 days.
A homepage that loads normally can still hide a failed form, missing conversion tracking code, or broken booking confirmation. Test the actions that bring in work.
Decide what is moving before touching the live site
The right plan depends on what is changing. A host-only move is usually simpler because URLs stay the same. A domain change, redesign, or switch to HTTPS needs more preparation.
Identify the type of move
Write down whether you are changing:
- Hosting provider while keeping the same domain and page addresses.
- A domain name change, or a move to a custom domain or subdomain, which needs a complete redirect map and Google Search Console checks.
- Website design or web development alongside the hosting move.
- A WooCommerce, membership, or booking site where orders and appointments change throughout the day.
Also record how the move will be carried out, whether through a manual migration or a WordPress migration plugin. This choice affects testing and rollback planning.
A move before a campaign or growth phase is safer than an emergency migration after failures appear. Measure current traffic, organic traffic, uptime, page speed, PHP version, form submissions, and errors before you start. Record which pages generate enquiries.
Confirm access and ownership
The business should control its domain registrar, DNS, hosting account, Google Analytics, Google Search Console, Google Business Profile, payment accounts, and primary email addresses. Give an agency or developer appropriate access, but avoid making them the sole owner.
List every connection to the site, including CRM tools, email marketing platforms, call tracking, Social Media feeds, review widgets, paid adverts, and Systems & Automation. This inventory makes troubleshooting far quicker if something stops working.
For agency teams moving sites for clients, See how we collaborate with creative agencies when you need technical delivery without giving away client ownership.
Prepare backups, staging and a rollback plan
Most migration problems are recoverable when you have a known-good backup and a tested route back. Without either, a small issue can become costly downtime.
Capture a baseline before the move
Save screenshots or exports of key pages, current rankings, traffic, enquiry numbers, and conversion events. Note the WordPress version, PHP version, active theme, plugins, licence details, redirects, CDN settings, and server-level rules.
Also record working email addresses for contact forms, quote requests, booking alerts, order emails, and staff notifications. Digital Marketing decisions, Local SEO, and Conversion Optimisation all rely on accurate measurement. Preserve tag manager containers, analytics IDs, pixels, and call tracking.
Create backups you can restore
Take a full database backup and a separate copy of the WordPress files, including uploads, plugins, themes, and wp-config.php. Store both as a separate, restorable migration backup.
A backup plugin can help create the copy, but keep at least one version away from the live hosting account. A WordPress migration plugin may assist with copying the site, but its result still needs checking on staging.
WordPress explains the recommended migration process and advises retaining both files and database copies. For active shops, booking businesses, and membership sites, confirm how orders or appointments created after the backup point will be handled.
A professional should test restoration on staging. WordPress documents the correct backup and restoration order: restore files first, then import the database.
Protect staging from search engines
Use a password-protected staging site hosted in a separate staging environment. Do not rely on robots.txt alone. Google may not see a noindex instruction if crawling is blocked first.
Google recommends password protection or a crawlable noindex directive for blocking staging content from search. Check that staging does not send emails to customers or submit live form data.
If a final sync requires a pause, use maintenance mode briefly and plan it carefully. Do not use it throughout preparation, and ensure your tested rollback is ready.
Lower the DNS TTL before cutover if your provider allows it. This may reduce caching time for some resolvers during DNS propagation, but it cannot make every internet connection update instantly.
Move files, database and DNS with care
This phase needs a quiet period, a named decision-maker, and a rollback point. Avoid making content edits on both the old and new sites once the final copy begins.
Transfer the site and update configuration
Copy the WordPress files to the new server, create a new database, and import the database backup. Alternatively, a WordPress migration plugin can assist with the file transfer, but verify its copy before continuing.
Before either method, confirm that the new server supports the existing PHP version. Then update the database name, user, password, and database host in wp-config.php.
If the site address changes, a developer may also need to set WP_HOME and WP_SITEURL. These values must use the correct protocol and have no trailing slash. The official guide to editing wp-config.php covers these settings.
This job is best handled by a WordPress professional if you do not have secure file access, database access, or confidence editing configuration files.
Replace old URLs safely
A new domain, staging address, or HTTP-to-HTTPS move can leave old URLs inside page-builder content, image links, menus, and settings. A basic database operation can corrupt serialised data used by WordPress and plugins.
If you’re changing to a custom domain, check old-to-new redirects alongside these URL replacements. Use a serialisation-safe search and replace method such as WP-CLI’s search-replace command, after taking another database backup. Then inspect key pages for missing images, broken layouts, and links that still point to staging.
Switch DNS and keep the old site ready
Install the SSL certificate before sending live traffic to the new server. Make the DNS changes during the agreed cutover window, then check that the site loads with HTTPS and without browser security warnings.
Mixed-content warnings happen when a secure HTTPS page requests an image, script, font, or other resource through HTTP. Update every resource to HTTPS rather than ignoring the warning.
Use maintenance mode only for a short final sync, if necessary, rather than taking the old site offline prematurely. Keep the previous hosting active until the new site is stable.
If a serious fault appears, switch back using the documented rollback plan instead of attempting hurried fixes on a live site.
Protect SEO with redirects and accurate crawl signals
A good WordPress migration checklist protects every useful route to your business. Search engine visibility, referral links, Local SEO listings, and old campaign URLs can all send prospective customers to pages you may have forgotten.
Map old pages to relevant new pages
Export every current URL and match it to the closest equivalent destination. A boiler repair page should lead to the new boiler repair page, not the home page. Redirect chains create delays and make faults harder to diagnose.
Google’s site-move guidance recommends mapping old URLs to new equivalents and using direct 301 redirects for changed URLs. Keep redirects in place for at least a year, and longer where they still receive traffic.
Update search and marketing signals
Check canonical tags, internal links, structured data, the XML sitemap, and robots.txt. Submit the new sitemap in Google Search Console, then request indexing only after the live version works correctly.
For a domain name or subdomain change, submit a Change of Address request in Search Console. Don’t use it for a host-only move where URLs remain unchanged.
Update the website link in your Google Business Profile, email signature, Digital Branding materials, online directories, paid adverts, and Social Media profiles. This prevents clients and prospects landing on an outdated address.
Validate the customer journey after launch
Treat the first 30 days as structured post-migration testing. Technical issues may only appear once real people, search engines, caches, and connected services reach the new server.
Test the revenue-producing actions
Work through the site on a phone and desktop as a visitor would. A Mobile Responsive layout should support every important action, not only display the homepage neatly.
- Submit a test form and confirm it reaches the right inbox or CRM.
- Test click-to-call links, booking tools, quote forms, checkout, payment, and confirmation emails.
- Check user logins, account areas, calendar connections, and scheduled WordPress cron tasks.
- Test important pages in a private browser window after clearing caches.
- Look for broken links, 404 errors, error pages, missing images, plugin conflicts, and cookie-consent problems.
AI for Small Business tools and other connected services also need testing. Check that automated replies, lead routing, reminders, and notifications still send to the right people.
Monitor search, speed and errors
Use Google Search Console to watch indexing, sitemap processing, crawl errors, and search clicks. Compare analytics traffic and Lead Generation figures with the baseline you recorded before launch.
Run key landing pages through PageSpeed Insights, then review Core Web Vitals, server response time, caching, large images, and third-party scripts. Avoid judging a migration by a single homepage score. Test service pages and the full enquiry path.
Ongoing website care plans can provide the routine backup checks, updates, security monitoring, and support that reduce future migration risk. Website Care & Maintenance is especially useful when several plugins, custom integrations, or staff accounts need regular attention.
Frequently asked questions about WordPress migration
What causes 404 errors after a WordPress migration?
Common causes include missing pages, changed permalink settings, incomplete redirects, cached old URLs, and menus that still link to staging. First, test the page address, then check redirects and save WordPress permalinks again. A developer should inspect server rules if 404s persist.
Will changing hosting affect SEO?
A host-only change should not require redirects if the domain and page URLs stay the same. However, poor performance, downtime, blocked crawling, missing tracking, or incorrect canonical tags can affect results. Keep the old server available and monitor Search Console after launch.
Can I migrate a WooCommerce site myself?
A simple store may be manageable with reliable documentation and backups. Still, stores need additional checks for stock, customer accounts, baskets, checkout, payment gateways, order emails, and new orders during cutover. Professional help is sensible where lost transactions would create a material problem.
Keep the new site stable
A successful move keeps your website available while protecting the routes customers and search engines already use. Backups, testing, accurate redirects, and a rollback plan matter more than moving quickly.
After launch, make regular checks of forms, speed, updates, security, and search visibility. Reliable maintenance protects the website work that brings in enquiries long after the migration is complete.
