OnWebPoint 
At some point, most site owners face WordPress website migration: moving to a faster host, switching from a page builder to a custom theme, upgrading a legacy site, or consolidating multiple domains. Done correctly, a WordPress website migration is invisible to visitors and search engines — rankings hold, links resolve, and the site goes live without downtime. Done incorrectly, it triggers 404 errors, drops in organic traffic, broken functionality, and weeks of cleanup. This guide covers how to approach a WordPress migration in Ireland so the outcome is the first scenario, not the second.
What Counts as a WordPress Website Migration?
Migration covers several related but distinct operations, each with different technical requirements:
Host migration — moving your WordPress files and database from one hosting provider to another. The most common type, often triggered by switching to better-quality managed WordPress hosting or moving to an Irish/EU server for performance or GDPR reasons.
Domain migration — moving your site from one domain to another (e.g. oldcompanyname.ie to newcompanyname.ie). Requires URL changes throughout the database and permanent 301 redirects from every old URL to its new equivalent.
HTTP to HTTPS migration — moving from an insecure HTTP site to HTTPS. Less common now (most new sites launch on HTTPS), but older Irish business sites still on HTTP need this, and it requires correct redirect implementation and updating internal links and canonical tags.
Platform migration — moving from another CMS (Squarespace, Wix, Shopify, Drupal, etc.) to WordPress. The most complex type: content needs to be exported, reformatted, imported, and often manually edited to match WordPress structure.
Subdomain to root migration — moving from blog.yourdomain.ie to yourdomain.ie/blog/, or vice versa. Requires redirect mapping and Rank Math/Yoast URL updates.
Before You Start: The Pre-Migration Checklist
Preparation prevents most WordPress website migration problems. Before moving anything:
Create a complete backup of the existing site — both files and database — stored somewhere completely separate from the current host. This is your recovery point if anything goes wrong. Do not migrate without it.
Crawl the existing site with a tool like Screaming Frog to get a complete list of all URLs that are currently indexed and returning 200 responses. This becomes your redirect map for any URL structure changes, and your baseline for checking nothing breaks post-migration.
Record your current rankings using Google Search Console or a rank tracker. Export your current position data for your main keywords. You want a pre-migration baseline to compare against post-migration performance and catch any unexpected drops quickly.
Note your current traffic in Google Analytics or Search Console. Establish what “normal” looks like so you can identify anomalies in the week after going live.
Check for existing redirects in your current .htaccess or server configuration. These need to be replicated on the new environment or traffic from old URLs will break.
Audit your plugins. A WordPress website migration is a good opportunity to remove unused or outdated plugins rather than carrying them forward to the new environment.
The WordPress Website Migration Process: Host-to-Host
A host migration keeping the same domain and URL structure is the most straightforward type. The process is:
Set up the new hosting environment first. Install WordPress, configure PHP version (8.x), create the database, and verify the server is running correctly before touching the live site.
Copy files and database to the new server. The cleanest method is using a migration plugin like Migrate Guru (free, designed for large sites) or All-in-One WP Migration. These tools handle the file transfer and database export/import, and update the database to reflect the new server paths automatically. For large sites (>2GB), command-line migration via SSH/SFTP is more reliable than browser-based tools.
Update wp-config.php on the new server with the new database credentials. Verify the site loads correctly on the new server using a temporary URL or by editing your local hosts file to preview it before DNS change.
Lower your DNS TTL to 300 seconds (5 minutes) at least 24 hours before the planned cutover. This means that when you update DNS to point to the new server, the change propagates globally within minutes rather than hours — minimising the window where some visitors see the old site and others see the new one.
Update DNS to point to the new server’s IP. Monitor both the old and new server during propagation. Once propagation is complete (typically 5–30 minutes with a low TTL), verify the live site is loading from the new server and all functionality works correctly.
Install and configure SSL on the new host if it was not transferred. Verify HTTPS is active and the certificate is valid before considering the migration complete.
Keep the old server active for at least 48 hours after cutover as a fallback. Do not cancel the old hosting account until you have confirmed the new site is stable.
Domain Migrations and the SEO Implications
Moving to a new domain is significantly more complex than a host migration from an SEO perspective. Every URL changes, which means every piece of search equity — every ranking, every backlink, every cached page in Google’s index — needs to transfer cleanly to the new domain.
The mechanism for this is permanent 301 redirects: every URL on the old domain redirects to the corresponding URL on the new domain. This signals to Google that the content has permanently moved, and transfers the majority of link equity. The key word is “majority” — domain migrations typically cause a temporary ranking dip even when executed correctly, because Google needs time to recrawl and re-evaluate the new domain. Expect 4–8 weeks of partial recovery, with full ranking stabilisation typically taking 3–6 months.
To minimise the impact:
- Map every old URL to its new equivalent — do not redirect everything to the homepage
- Use 301 (permanent) redirects, never 302 (temporary)
- Update your XML sitemap to reflect new URLs and submit to Google Search Console on the new domain
- Add the new domain as a property in Search Console and use the Change of Address tool
- Update your Google Business Profile to reflect the new domain
- Contact owners of your most important backlinks and request they update to the new URL
- Update all internal links within WordPress to the new domain (use Search Replace DB or WP-CLI)
Do not migrate to a new domain lightly. If you are rebranding, the SEO cost is real and unavoidable — but manageable with the right preparation. If you are considering a domain change purely for aesthetic reasons without a business case, the ranking disruption is rarely worth it.
Platform Migrations to WordPress
Moving from Squarespace, Wix, Shopify, or another platform to WordPress is frequently motivated by the limitations of those platforms — lack of customisation, poor SEO control, high subscription costs, or WooCommerce requirements for complex ecommerce functionality. The comparison article on WooCommerce vs Wix for Irish businesses covers the strategic case in detail.
From a technical standpoint, platform migrations to WordPress typically require:
- Exporting content from the source platform (usually as XML, CSV, or via third-party tools)
- Importing and reformatting content in WordPress — blog posts typically import reasonably cleanly; page content usually needs manual work
- Rebuilding the site design and page layouts in WordPress (page builder or custom theme)
- Setting up 301 redirects from old platform URLs to new WordPress URLs — critically important if the URL structure changes
- Migrating any ecommerce product catalogue, order history, and customer data if moving from Shopify to WooCommerce
The redirect mapping is the most SEO-critical step. Squarespace, Wix, and Shopify all have different default URL structures from WordPress. If these are not redirected correctly, all of your existing search rankings and backlinks point to dead pages.
Testing After WordPress Website Migration
Before considering a WordPress website migration complete, run through this verification checklist:
- Homepage loads correctly on HTTPS
- All redirects are returning 301 (not 302 or 404) — test a sample of your most important old URLs
- No mixed content warnings (HTTP resources loading on an HTTPS page)
- Contact forms submit correctly and deliver to the right email address
- WooCommerce checkout processes a test order end-to-end (if applicable)
- Google Analytics and Search Console are receiving data from the new environment
- XML sitemap is accessible and submitted to Search Console
- Robots.txt is not blocking crawling (check
yourdomain.ie/robots.txt) - Page speed is comparable to or better than the old environment
- All emails (contact form notifications, WooCommerce order emails) are sending correctly
Use Google’s Rich Results Test on key pages to verify structured data transferred correctly. Run a Screaming Frog crawl of the new site and compare against your pre-migration crawl to catch any pages that returned 200 before but are now returning errors.
Common WordPress Website Migration Mistakes That Damage SEO
Not setting up redirects is the most damaging mistake. Every URL that existed on the old site and is not redirected on the new one becomes a 404 — a dead page that loses all its link equity and sends a negative signal to Google. If you have years of backlinks pointing to old URLs, this can wipe out significant ranking positions.
Migrating with robots.txt blocking crawling. It is common practice to block crawlers during development (to prevent a staging site from being indexed), but if this block is not removed before launch, Google cannot access the new site. Always check robots.txt immediately after go-live.
Changing URL structure unnecessarily. If your old site used /about-us/ and your new site uses /about/, you need a redirect. If there is no reason to change the URL structure, do not change it — keeping the same URLs is the least disruptive path for both users and search engines.
Forgetting to update Google Business Profile, social media profiles, and directory listings with the new domain (if applicable). Inconsistency between your new domain and your local citations weakens your local SEO signals.
When to Use a Developer for WordPress Website Migration
Simple host WordPress website migrations for small sites with straightforward configurations can be handled by technically confident site owners using WordPress website migration plugins. More complex scenarios — domain changes, platform migrations, large WooCommerce stores, or sites with complex redirect structures — benefit significantly from professional handling.
The cost of a botched migration can be substantial: weeks of ranking recovery, manual redirect cleanup, broken functionality that drives away customers. A post-migration SEO audit is always worthwhile to confirm everything transferred cleanly and catch any issues before they compound.
If you are planning a WordPress website migration — whether switching hosts, moving to a new domain, or migrating from another platform — get in touch for a free assessment of what is involved. WordPress website migration is a core part of the WordPress developer service — I handle the technical process end-to-end, including redirect mapping, DNS cutover, and post-migration verification.
