Sooner or later, most WordPress sites need to move. The current host has become slow, support takes days to answer, the price keeps going up or the site has simply outgrown a shared hosting plan. Sometimes the move is bigger than a new server: a new domain after a rebrand, a switch from HTTP to HTTPS or the merger of two sites into one. Whatever the reason, the idea of moving a working website makes many owners nervous, and with good reason.
A WordPress migration touches everything at once: files, database, domain settings, email and search rankings. Done carefully, visitors never notice anything except a faster site. Done in a hurry, it can mean broken pages, lost orders, missing emails and a drop in Google traffic that takes months to recover. This guide explains how to plan a migration, move the site, switch the domain over and protect your SEO along the way. It is written for business owners planning their first move and for agencies that move client sites regularly.
When It Makes Sense to Move
Not every problem needs a migration. Slow pages are often caused by heavy plugins, unoptimized images or a bloated database, and fixing those may be enough. A move makes sense when the limits come from the hosting itself: shared servers that slow down at peak times, old PHP versions you cannot change, no staging environment, poor backups or support that cannot help when something breaks.
There are also moves that have nothing to do with performance. A rebrand may require a new domain. A business may consolidate several small sites into one stronger site. An agency may bring client sites onto a single platform so they are easier to maintain. Each of these has different risks, so it helps to be clear from the start which kind of move you are making.
| Type of Move | What Changes | Main Risk |
|---|---|---|
| New host, same domain | Server, files and database location | Downtime, broken email, missing files |
| New domain, same host | All URLs on the site | Lost rankings without proper redirects |
| HTTP to HTTPS | Protocol in every URL | Mixed content, redirect loops |
| Merging sites | Content and URL structure | Duplicate content, lost pages |
| New host and new domain | Everything at once | Hard to diagnose problems |
If you can, avoid changing everything at the same time. Moving to a new host first and changing the domain later, after the new server has proven stable, makes it much easier to see what caused a problem if one appears.
Plan the Migration Before You Touch Anything
The most successful migrations are mostly planning. Before any files move, write down what the site has today and what must work after the move. This list becomes your checklist for testing later, and it catches the details people forget, such as an old email forwarder or a cron job that sends invoices every night.
Start with an inventory of the current setup: the WordPress and PHP versions, the plugins and theme, the size of the files and database, scheduled tasks, custom server rules in `.htaccess` or the server configuration, and any integrations with payment gateways, CRMs or email platforms. Note where email is hosted, because many small businesses run their mailboxes on the same hosting account as the website and only discover this when the old account is closed.
Then crawl the current site with an SEO crawler and export a full list of URLs, page titles and status codes. Save a copy of your Google Search Console performance data as well. These records give you a baseline to compare against after the move, so you can prove that every page made it across and spot any drop in traffic quickly.
Finally, choose a migration window. For most business sites that means a quiet period with low traffic, never the day before a big campaign or a holiday sale. For online stores, plan a short content freeze, a period when no products are edited and, if possible, no orders are taken, so that nothing created on the old server is lost during the switch.
Take a Complete Backup First
Every migration starts with a full backup of the existing site, kept somewhere independent of both the old and the new host. A complete backup includes all WordPress files, the full database and any custom configuration files. If something goes wrong at any point, this copy lets you restore the original site exactly as it was.
It is worth testing that the backup actually works. A backup file that cannot be restored is only a false sense of security. If your current host provides backups, download your own copy anyway, because access to the old host may end before you are sure the new site is perfect. Our guide on how to back up a WordPress site explains what a complete backup should contain and how often to take one.
Moving Files and the Database
The core of the migration is copying two things: the files and the database. The files include WordPress core, the `wp-content` folder with your themes, plugins and uploads, and configuration files such as `wp-config.php`. The database holds all your content, settings, users and orders.
There are three common ways to move them. A migration plugin packages the site into an archive and unpacks it on the new server, which works well for small and medium sites. A manual migration copies files over SFTP and exports and imports the database through phpMyAdmin or the command line, which gives you more control and handles larger sites. A server-to-server transfer with command-line tools moves everything directly between hosts and is the fastest option for big sites. The official WordPress documentation on moving WordPress covers the manual approach step by step.
Whichever method you use, the new server needs the right environment before the import: a compatible PHP version, enough memory, the same PHP extensions and a database with the same character set. If the new host runs a much newer PHP version than the old one, test the site carefully, because outdated plugins can break on newer PHP.
After the import, update `wp-config.php` with the new database name, user and password. If the domain is changing, the database also needs a careful update, which is the most technical part of the whole migration.
Search and Replace Without Breaking Data
WordPress stores full URLs throughout the database: in post content, image links, menus, widgets and plugin settings. When the domain or protocol changes, all of those references need to be updated. The temptation is to run a simple text replacement on the exported database file, and that is one of the most common causes of broken migrations.
The problem is serialized data. Many plugins and themes store settings as PHP serialized strings, which include the length of every piece of text. As the PHP documentation on serialize shows, the stored length must match the actual text exactly. If a plain find-and-replace changes a URL from 20 characters to 25, the stored length becomes wrong, the data can no longer be read and widgets, theme settings or page builder layouts silently disappear.
The safe approach is to use a tool that understands serialization. The WP-CLI command search-replace updates URLs across the whole database and recalculates serialized lengths automatically, and it offers a dry run so you can see how many changes it will make before applying them. Most good migration plugins do the same. Always run the replacement on a backup copy first if you are unsure.
Test on the New Server Before Switching DNS
At this point, the site exists on the new server, but visitors still see the old one, because the domain still points to the old host. This is the perfect moment to test, since nothing you find can affect real visitors yet. You can preview the new site by editing your computer’s hosts file or by using a temporary URL from your hosting provider.
Work through the checklist you wrote during planning:
- Open the homepage, key service pages, blog posts and the contact page.
- Log in to the dashboard and check that plugins, menus and widgets look right.
- Submit every form and confirm the emails arrive.
- For stores, add products to the cart and complete a test checkout in test mode.
- Check that images load from the new server, not from the old domain.
- Confirm that scheduled tasks, backups and caching are set up on the new host.
- Compare a sample of pages with your crawl from before the move.
If you use a staging site, the same habits apply here: test like a visitor, not like an administrator, and do not switch over until every item on the list works.
Switching DNS With Minimal Downtime
When the new site has passed testing, it is time to point the domain at the new server. This happens through the domain’s DNS records, usually by changing the A record, and sometimes the AAAA record for IPv6, to the new server’s IP address.
DNS changes do not take effect everywhere instantly. Each record has a TTL, a time to live, which tells networks how long to cache it. A day or two before the migration, lower the TTL on the records you will change to something short, such as five minutes. Then, when you make the switch, most visitors will reach the new server within minutes rather than hours. Cloudflare’s explanation of DNS records is a good reference if these terms are new to you.
Be careful not to touch records you do not intend to change. MX records control where email is delivered, and TXT records hold email authentication and domain verification settings. Changing the wrong record can stop email or break verified services. After the switch, issue an SSL certificate on the new server. Many hosts do this automatically with Let’s Encrypt, but it can only complete once the domain points to the new server.
For online stores, keep the old server untouched for a few days after the switch. If an order slips through on the old server while DNS updates, you can still find it and add it to the new site.
Protect Your Rankings After the Move
A migration to a new host with the same domain and the same URLs usually has no effect on rankings, as long as the site is fast and every page works. Google simply crawls the same pages at a new address. The bigger SEO risk comes when URLs change, for example with a new domain, a new URL structure or the move to HTTPS.
In those cases, every old URL needs a 301 redirect to its new equivalent, one to one, not everything to the homepage. Google’s guide to site moves with URL changes explains the recommended process, and its documentation on redirects and Google Search explains why permanent server-side redirects are the strongest signal. For a domain change, also use the Change of Address tool in Search Console once the redirects are live.
After the move, watch Search Console closely for the next few weeks:
- Submit the new XML sitemap and check that it is read without errors.
- Check the Page indexing report for new 404 errors and fix any missing redirects.
- Run URL Inspection on your most important pages.
- Compare clicks and impressions with the baseline you saved before the move.
A short dip in some rankings during the first weeks is normal when URLs change, while Google processes the redirects. A drop that continues beyond that usually points to missing redirects, blocked pages or content that did not make it across.
How Webueno Handles Migrations
Every Webueno hosting plan includes site migration: a full transfer of the website, a database search and replace that handles serialized data correctly, and URL and path corrections so nothing points to the old server. Our team handles the move, so you do not need to touch files, databases or DNS records yourself unless you want to.
Sites move onto their own VPS servers powered by DigitalOcean, with a choice of data center locations, Redis object caching, a cloud firewall and free Let’s Encrypt SSL with automatic renewal. Multiple PHP versions are available per site, which matters when an older site needs time before it can run the newest PHP. Hosting add-ons such as daily offsite backups with up to 30 days of history, uptime monitoring and malware scanning can be switched on per site after the move.
For agencies, migrations are a natural moment to bring client sites under one roof. Once sites are on Webueno hosting, updates, backups, monitoring and support requests are managed from one dashboard, and agencies earn a 10% share of the hosting revenue for the sites they bring. If a site needs extra work before or after the move, such as PHP compatibility fixes or speed optimization, that work runs through the same ticketing and credit system.
Make Your Next Move the Easy Kind
Migrations feel risky because they are rare and because many things change at once. With a written plan, a complete backup, a proper search and replace, testing before the DNS switch and close monitoring afterwards, they become routine. Most problems that appear after a move can be traced back to a step that was skipped or rushed.
If your site has outgrown its current hosting, or you want a team that handles the whole move for you, create a free Webueno account and request a migration. We will plan the move with you, transfer the site and make sure everything works before the domain switches over.
Frequently Asked Questions
These are the questions we hear most often from site owners and agencies planning a WordPress migration.
Will Moving My WordPress Site Affect SEO?
Moving to a new host with the same domain and URLs usually has no effect on rankings. Changing the domain or URLs needs one-to-one 301 redirects and close monitoring in Search Console.
How Long Does a WordPress Migration Take?
Small and medium sites usually move within a few hours, plus time for testing. DNS changes reach most visitors within minutes if the TTL was lowered beforehand.
Can I Migrate WordPress Without Downtime?
Yes, nearly. Build and test the site on the new server first, lower the DNS TTL, then switch. Visitors move to the new server with little or no interruption.
Why Do Widgets or Settings Disappear After a Migration?
Usually because URLs were replaced with a plain text search and replace, which breaks serialized data. Use WP-CLI search-replace or a migration tool that handles serialization.
Will My Email Stop Working When I Change Hosts?
It can if your mailboxes are on the old hosting account or if MX records are changed by mistake. Check where email is hosted before the move and only change the records you need.
Do I Need a New SSL Certificate After Migrating?
Yes. The new server needs its own certificate. Many hosts issue a free Let’s Encrypt certificate automatically once the domain points to the new server.