How to Migrate WordPress to New Domain

Migrating your WordPress site to a new domain doesn't have to be stressful—but it does require precision. Whether you're rebranding your South African business, consolidating multiple sites, or moving away from a domain that no longer reflects your brand, this process involves updating database references, DNS records, and hosting configurations. Done incorrectly, a domain migration can trigger 404 errors, break your SEO rankings, and leave visitors landing on a blank page. In this guide, I'll walk you through the exact steps we use at HostWP when handling migrations for our clients, with practical advice for avoiding common pitfalls.

The core principle is simple: WordPress stores your domain URL in multiple places (settings, database content, and redirects), so you must update all of them simultaneously. A rushed migration is far more costly than a slow, methodical one. At HostWP, we've migrated over 500 South African WordPress sites since 2018, and I've seen firsthand that the difference between a smooth transition and a disaster is planning and order of operations.

Create a Full Backup Before You Start

The single most important step is creating a complete backup of your WordPress installation—database, all files, and theme/plugin settings. I cannot overstate how critical this is. If anything goes wrong during the migration, a clean backup is your escape hatch. At HostWP, all client accounts include daily automated backups stored separately from the live environment, which has saved countless migrations from becoming nightmares.

You have two options: use your hosting provider's backup tool (fastest and safest), or manually download via FTP/SFTP and export the database via phpMyAdmin. If you're on HostWP, log into your control panel and download a full account backup—this takes 2–3 minutes and includes everything. If you're manually backing up, download the wp-content, wp-admin, wp-includes folders and the root files (wp-config.php, .htaccess, index.php), then export the database as an SQL file.

Store your backup on your local machine and in cloud storage (Google Drive, Dropbox, or OneDrive). South African internet can be unpredictable during load shedding periods, so having a local copy means you're not dependent on download speeds when you need to restore. Never attempt a domain migration without this safety net in place.

Update WordPress URL Settings in Admin

Once your backup is secure, log into your WordPress admin dashboard on your old domain and navigate to Settings → General. You'll see two fields: WordPress Address (URL) and Site Address (URL). Both should currently show your old domain. Change both to your new domain and click Save. WordPress will attempt to log you out, which is normal.

Here's the critical part: do not try to log back in yet if you haven't updated your DNS or domain settings on your hosting. If your DNS isn't pointing to your host yet, the new domain will return a connection error. Instead, move to the next step—updating your database—then return to verify these settings once DNS is live.

Faiq, Technical Support Lead at HostWP: "I've seen sites break because someone updated the WordPress URL before their DNS was ready. The easiest way to avoid this: update your hosting settings and DNS first, then change the WordPress URL. That way, the domain resolution is already in place when you make the change."

If you do get locked out, you can reset these values directly in the database or via WP-CLI if you have SSH access. Most managed hosting (including HostWP) provides SSH access, allowing you to run a quick WP-CLI command: wp option update siteurl 'https://newdomain.co.za' (replace with your actual domain).

Search and Replace Your Domain in the Database

WordPress stores your domain URL in dozens of places within the database: post content, featured images, widget settings, plugin options, and metadata. You must search your entire database for the old domain and replace it with the new one. This is where mistakes happen, so follow carefully.

Use a plugin like Better Search Replace (free, 2 million+ installations) or WP Migrate Lite (more comprehensive). If you prefer command line, WP-CLI offers the fastest option: wp search-replace 'olddomain.com' 'newdomain.co.za' --all-tables. In our experience at HostWP, this single command handles 95% of domain references in one pass.

If using a plugin, follow these rules: (1) always run a test first (most plugins show how many replacements would occur before confirming), (2) ensure you're searching the old domain in the correct format (include http:// or https://), and (3) backup again after running the replacement. For South African sites especially, watch for domains with special characters or mixed http/https references, which can cause mixed content warnings in Chrome or Firefox.

One common mistake: forgetting to replace serialized data. WordPress stores some settings as PHP-serialized strings, where a simple text search won't work. Better Search Replace handles this automatically; if you use a basic find-and-replace, you'll leave broken references behind. After running the replacement, spot-check a few posts and pages in the editor to confirm all URLs updated correctly.

Update DNS Records and Nameservers

Now your WordPress database is updated, but your domain isn't pointing to your host yet. Log into your domain registrar (GoDaddy, Namibia-based Hetzner, or wherever you registered the domain) and update the nameservers to match your hosting provider's. If you're moving to HostWP, we'll provide two nameserver addresses during onboarding. Replace your old nameservers with ours and save.

DNS changes can take 1–48 hours to propagate globally, though in South Africa (and with fibre providers like Openserve or Vumatel), you typically see changes within 2–6 hours. You can check propagation using mxtoolbox.com or whatsmydns.net—enter your new domain and verify that the nameservers match your host. Once propagation is complete, your domain will resolve to your new hosting IP address.

If you're keeping the domain registrar the same but just changing hosts, you might only need to update DNS A records instead of nameservers. Ask your new host (e.g., HostWP support) for the correct A record IP address and update it in your registrar's DNS panel. This is faster and avoids nameserver propagation delays. For sites with POPIA compliance requirements (personal data protection), make sure you're moving to a host that explicitly supports South African data residency—HostWP's Johannesburg infrastructure ensures your data stays within ZA borders.

Install SSL on Your New Domain

Your new domain needs an SSL certificate to serve HTTPS traffic. If you're moving to HostWP, we provide a free Let's Encrypt SSL certificate for every domain, installed automatically. If you're moving to another host, check whether SSL is included. Most managed WordPress hosts in South Africa (including HostWP, Xneelo, and Afrihost) bundle SSL at no extra cost.

If your old domain had an EV (Extended Validation) SSL certificate or a paid wildcard certificate, you'll need to reissue or transfer it to your new domain. Contact your certificate provider or hosting support for the exact process. For most small businesses, a standard free SSL from Let's Encrypt is more than sufficient and autorenews every 90 days.

After DNS propagates and your domain is live on your host, request the SSL certificate through your hosting control panel. On HostWP, this is one click in cPanel. Wait 10–15 minutes for issuance, then update your WordPress URL settings to use https:// (not just http://). Test your site in a browser and confirm the green lock icon appears in the address bar. If you see a red warning or "mixed content" error, you likely have hardcoded http:// URLs still in your database—run the search-and-replace again for any remaining old domain references.

Test, Verify, and Clean Up Redirects

Before announcing your new domain publicly, test every critical function: homepage loads, navigation links work, images display, forms submit, and your ecommerce checkout (if applicable) processes payment. Open your site on mobile and desktop. Run a quick speed test on GTmetrix or Google PageSpeed—if your new host has better infrastructure (like HostWP's LiteSpeed + Redis caching), you should see improvements. Check your SSL certificate validity and WHOIS information.

Next, set up 301 redirects from your old domain to your new one. This tells search engines (and visitors) that your content has permanently moved, preserving your SEO rankings. In WordPress, use a plugin like Redirection (free, highly rated) or ask your host to set up server-level redirects in .htaccess or nginx. A 301 redirect looks like this in .htaccess: Redirect 301 / https://newdomain.co.za/. This ensures anyone landing on the old domain is automatically sent to the new one.

Monitor your Google Search Console and analytics for the first 2–4 weeks. You'll see traffic initially split between old and new domains as the 301 redirect kicks in and Google re-indexes. After 30 days, old domain traffic should drop to near zero. At HostWP, we've found that sites with proper 301 redirects retain 95–98% of their SEO rankings post-migration; sites without redirects often see a 20–30% ranking dip in the first month.

Finally, once traffic is fully migrated and you're confident in the new domain, you can let the old domain expire or keep it parked with the 301 redirect indefinitely. Keeping the old domain alive with a redirect is a safer long-term strategy for brand reputation and SEO.

Frequently Asked Questions

1. Will my SEO rankings drop after migrating to a new domain?

Not if you implement 301 redirects correctly. Google treats a properly redirected domain migration as a content move, not a deletion, so rankings typically recover within 4–6 weeks. We've seen clients at HostWP maintain or even improve rankings post-migration because their new host is often faster than their old one.

2. How long does a WordPress domain migration take?

The technical steps (backup, database updates, DNS changes) take 30–60 minutes. However, DNS propagation adds 1–48 hours, so plan for a full 24-hour window from start to stable operations. Keep your old site live during this period as a safety net.

3. Can I migrate to a new domain without downtime?

Yes. Update your WordPress settings and database while your site is still on the old domain, then switch DNS over once everything is tested. Your site experiences downtime only during the DNS switch (usually under 1 minute in South Africa with Openserve fibre), or not at all if you use a staging approach.

4. What if I mess up the domain migration?

Restore your backup immediately. Backups take the stress out of migrations—if anything breaks, you're back to your starting point in 5–10 minutes. This is why we emphasise backup before every major change.

5. Do I need to update anything in my plugins or themes after migrating?

Most plugins and themes pull the domain URL from WordPress settings, so no. However, check any hardcoded URLs in custom code, contact forms, or API integrations. Some WooCommerce extensions or membership plugins may require re-authentication with your new domain in their settings.

Sources

• WordPress.org — Moving WordPress
• Google PageSpeed Insights
• MXToolBox — DNS Propagation Checker