A WordPress migration checklist breaks a site move into three phases: back up your files and database and prepare the new host before you start, move and verify the data during the transfer, then test URLs, redirects, SSL, and search visibility after cutover. Follow the phases in order and your site moves without downtime or lost rankings.
That checklist runs in four phases: pre-migration backup and audit, the file and database transfer itself, DNS cutover, and post-launch verification. For a typical business site under a few gigabytes, a migration plugin such as All-in-One WP Migration or Duplicator completes the transfer in roughly 1 to 2 hours, while a fully manual move through phpMyAdmin and FTP usually takes 3 to 6 hours. The one exception is multisite installs or sites needing server-level configuration changes, which a plugin cannot handle and require manual migration regardless of size.
GEENXT’s June 2026 keyword research found a combined 2,350 monthly searches across 10 WordPress migration queries, most carrying a keyword difficulty of 8 or lower, which is why this checklist covers plugin migrations, manual moves, and Squarespace-to-WordPress transfers in one place.
Most migrations that go wrong fail for boring reasons: a missing backup, a skipped redirect, a caching plugin left running during the transfer. This checklist walks through every phase in order, whether you plan to move the site yourself with a plugin, do the whole thing manually, or hand it to a professional migration service. Work through it top to bottom and nothing gets skipped.
What Is a WordPress Migration and Why Does It Matter?
A WordPress migration is the process of moving a WordPress site from one hosting environment to another: a new hosting provider, a new server at your current host, or a new domain. It covers two things at once, your WordPress files (themes, plugins, uploads) and your WordPress database (posts, pages, settings, orders). Both have to arrive intact and stay in sync for the migrated site to actually work.
Businesses migrate for predictable reasons. The current hosting plan is too slow or too small, support quality has dropped, or the site has simply outgrown shared hosting and needs managed WordPress infrastructure instead. Sometimes the move is a full platform switch, like going from Squarespace to WordPress. Whatever the trigger, the stakes are the same: your traffic, your rankings, and your customers’ experience all ride on the move going cleanly.
A move is also a natural moment to fix problems you have been putting off. Since you are already testing everything anyway, pair the move with the routine in our WordPress maintenance checklist for business websites so the site lands on the new host in better shape than it left the old one.
How Long Does a WordPress Site Migration Take?
How long it takes depends mostly on size and method. Moving a small site to a new host with a plugin-assisted transfer typically takes 1 to 2 hours of hands-on work. A larger business site moved manually takes 3 to 6 hours including testing. The real wildcard is DNS propagation: once you point your domain at the new host, the global update can take up to 48 hours to reach every visitor, though most people see the new server within a few hours if you lower the TTL in your DNS records ahead of time.
Plan the cutover for your lowest-traffic window. For most business sites that is a weekend night in your customers’ time zone, which buys you a quiet stretch to test the migrated site before Monday traffic shows up.
Pre-Migration Checklist: Before You Move Anything
Preparation decides whether the rest of the migration is routine or an emergency. Complete every item here before you migrate your WordPress site.
- 1. Take a full backup. Create a complete copy of your WordPress files and database and store it off the server you are leaving. This backup is your undo button if anything goes wrong during the migration. Our WordPress backup strategy guide covers where those copies should live.
- 2. Set up the new hosting account. Choose the new hosting provider, confirm PHP and database versions match or exceed the old site, and collect your credentials: control panel, SFTP or FTP, and database access. If the domain is changing too, register the new domain now.
- 3. Audit before you pack. Delete unused themes and plugins, clear spam comments, and remove orphaned tables. Less WordPress data migration means less to transfer and less to break.
- 4. Document your setup. Note active plugins, custom code, cron jobs, and email routing tied to the current host. Update your PHP version safely first if the new host requires it; our guide on how to update WordPress safely shows the order that avoids breakage.
- 5. Choose the right time and inform your audience. Schedule the move for a low-traffic window and warn customers if any downtime is possible.
- 6. Enable maintenance mode and freeze changes. Stop publishing content and pause WooCommerce orders where possible, so no data is created after your backup.
- 7. Disable caching, security, and redirect plugins. These are the plugins most likely to interfere with the migration. Cached URLs, firewall IP rules, and old redirect chains all confuse the new environment; reactivate them one at a time after the move.
During the Migration: Moving Files and the Database
This is the core of any WordPress site migration. If you use a migration plugin, it automates most of these steps; doing the move manually gives you full control. Either way, this is what has to happen, step by step:
- Export your website files. Download the whole WordPress folder from the current host over SFTP or FTP: core files, wp-content with your themes, plugins, and uploads, and any custom directories.
- Export the database. In phpMyAdmin (or WP-CLI), export the full WordPress database as a single SQL file. This file and the files export together form the complete copy of your WordPress site.
- Create a new database on the new host. In the new control panel, create a new database plus a database user with full privileges, and record the name, user, and password.
- Upload files and import the database. Upload the website files to the new server’s web root, then import the SQL file into the new database. Large sites may need the upload split or a compressed archive.
- Update your wp-config.php file. Point the configuration at the new database name, user, password, and host. A mismatch here causes the classic “error establishing a database connection” screen.
- Update URL references. If the domain changed, run a search-and-replace so every URL in the database points at the new domain, including serialized options. Skipping this leaves broken links and mixed-content warnings across the site.
- Test on the new server before DNS. Use your hosts file or a staging URL from the host to load the site on the new infrastructure while the world still sees the old one. Treat this like the dress rehearsal in our WordPress staging checklist: click through key pages, log in, submit a form.
- Point your domain to the new host. Update the DNS records (usually the A record or nameservers) so the domain resolves to the new server. Propagation starts now, and both servers should stay live until it completes.
The official WordPress documentation keeps a detailed reference for each step; see the WordPress.org guide to migrating a site for the canonical procedure.
Post-Migration Checklist: Test the Migrated Site
The migration is not really done until everything below checks out on the new host. Work through this in the first 24 hours after migrating your site:
- Load the site and log in. Confirm the homepage, key landing pages, and wp-admin all load from the new server, not a cached copy of the old site.
- Re-save permalinks. Settings, then Permalinks, then Save. This rebuilds rewrite rules and fixes most 404s immediately after a move.
- Hunt for broken links and missing images. Crawl the site or spot-check top pages. Broken links usually trace back to an incomplete URL search-and-replace.
- Verify SSL. Issue or import the certificate on the new host and confirm every page loads over HTTPS with no mixed-content warnings.
- Test forms, checkout, and email. Send a test through every contact form and, on WooCommerce sites, place a test order. Confirm outbound email still delivers from the new server.
- Confirm 301 redirects. If URLs or the domain changed, every old address must return a permanent redirect to its new equivalent, one hop, no chains.
- Update Google Search Console. Verify the new property if the domain changed and submit your XML sitemap so crawlers find the new structure quickly.
- Re-enable and re-test plugins. Turn caching, security, and redirect plugins back on one at a time, checking the site after each.
- Watch traffic and rankings for two weeks. Compare analytics against the pre-move baseline. A brief wobble is normal; a sustained drop means a redirect or indexing problem worth investigating.
- Keep the old site for 30 days. Do not cancel the old hosting account until DNS propagation is long finished and two clean weeks of data confirm a successful migration.
Plugin vs Manual Migration: Which Should You Use?
Should you use a plugin or migrate the site manually? The honest answer: a migration plugin is the right default for most business owners, and manual migration is the right tool for when the plugin route hits a wall.
| Approach | Best for | Watch out for |
|---|---|---|
| Migration plugin (e.g. All-in-One WP Migration, Duplicator, UpdraftPlus) | Standard sites up to a few GB; same-domain host moves; non-technical owners | Upload size limits on the new host; some hosts block import plugins |
| Manual migration (SFTP + phpMyAdmin) | Large or complex sites, multisite, server-level customizations | Every step is on you: wp-config.php edits, URL replace, file permissions |
| Host or agency migration | Business-critical sites; owners who want zero risk | Quality varies; many hosts offer a free migration, agencies add testing and rollback |
A migration plugin compresses steps one through six into an export file and an import screen. All-in-One WP Migration alone powers millions of site migrations, which says a lot about how reliable the plugin route has gotten. Choose manual when your site exceeds plugin limits, when the new environment needs different configuration, or when a failed import leaves you no choice anyway.
Migrating to WordPress From Squarespace or Another Platform
Not every move is host to host. “Migrate website to WordPress” is one of the most common searches in this space, usually from owners leaving a closed builder, and a Squarespace to WordPress migration is the most frequent version of that move. If you are still deciding whether to leave a hosted builder at all, our Webflow vs WordPress comparison walks through that choice before the migration begins. The checklist above still applies, but the export phase changes because closed platforms only let part of the content out.
To migrate Squarespace to WordPress: export the XML file Squarespace provides (posts, pages, and galleries), import it through the WordPress importer on your new hosting, then rebuild what the export leaves behind, including menus, product catalogs, and design. Images stay hosted on Squarespace after import, so run an image importer to pull them into your new media library before you cancel the old subscription. The same pattern holds when you move off Wix, Shopify, or Webflow: content exports, design does not, and 301 redirects from the old URLs decide whether your rankings survive the switch.
How to Protect Your SEO During a WordPress Migration
Search engines tolerate clean moves. Google’s own documentation on site moves with URL changes is explicit: map every old URL to its new equivalent with a 301 redirect, keep the redirects live for at least a year, and tell Google Search Console about the change of address when the domain moves.
In practice, SEO-safe migrations come down to four controls. First, keep URLs identical whenever you can; a pure hosting move with unchanged URLs carries near-zero ranking risk. Second, when URLs must change, build the redirect map before the move, not after. Third, preserve titles and meta descriptions so nothing gets rewritten by accident during the transfer. Fourth, watch crawl errors in Google Search Console daily for the first two weeks and fix anything wrong while trust is still fresh. Handled that way, a staged move protects the ranking equity you have already built.
When to Use WordPress Migration Services
DIY makes sense for a small site and a confident owner. A migration service earns its fee once the numbers get bigger: an eCommerce store where an hour of downtime costs real revenue, a content site whose organic traffic is the business, or a stack of custom code nobody has fully documented. A professional team stages the move, tests everything twice, and owns the rollback plan if something goes wrong.
That is exactly the work our WordPress support plans cover: managed migration, staging, backups, and post-move monitoring so the transition happens without surprises. If you would rather hand off the whole checklist than execute it yourself, start there.
Frequently Asked Questions
What is a WordPress migration and why is it necessary?
A WordPress migration moves your site’s files and database from one server, host, or domain to another. It becomes necessary when your current host limits performance, cost, or support, when you rebrand onto a new domain, or when you leave a closed platform and migrate your WordPress website onto infrastructure you control.
How long does a WordPress site migration take?
A typical WordPress site migration takes 1 to 2 hours of hands-on work using a migration plugin, or 3 to 6 hours if you migrate manually through phpMyAdmin and FTP, for an average business site under a few gigabytes. That is separate from DNS propagation, the time it takes the internet to recognize your site’s new server address, which can theoretically take up to 48 hours worldwide. In practice most visitors reach the new server within a few hours, especially if you lower your domain’s DNS TTL (time to live) setting a day before the move, since a shorter TTL tells other servers to recheck your DNS records sooner. Larger sites, multisite networks, or manual server-level changes can extend either estimate.
Should I migrate my WordPress site manually or with a plugin?
Use a WordPress migration plugin for standard sites under a few gigabytes; it automates the export, transfer, and import with the least room for error. Migrate the site manually when it is very large, uses multisite, or needs server-level changes a plugin cannot handle. When neither fits, a host or agency migration is the safer path.
What are the SEO risks of a WordPress migration?
The main risks are lost rankings from missing 301 redirects, indexing gaps from an unsubmitted sitemap, and duplicate content if both old and new sites stay live without redirects. Keep URLs unchanged where possible, map redirects before the move, and monitor Google Search Console for the first two weeks.
What should I check after migrating my WordPress site?
Test the migrated site immediately: homepage and key pages, wp-admin login, permalinks re-saved, SSL active, forms and checkout working, images loading, and redirects returning 301s. Then verify Google Search Console, resubmit the sitemap, and compare traffic against your pre-migration baseline for two weeks.
How can I minimize downtime during a WordPress migration?
Move your WordPress site onto the new server and test it fully before touching DNS, lower your DNS TTL a day ahead, and keep both servers running through propagation. Done in that order, visitors are served by the old site until the new one answers, and effective downtime rounds to zero.
What are common issues during a WordPress migration?
The classics: database connection errors from a wrong wp-config.php value, 404s fixed by re-saving permalinks, mixed-content warnings from an incomplete URL replace, broken links and images, email that stops sending from the new server, and import failures when a plugin hits the new host’s upload limit.
Can I migrate a Squarespace site to WordPress myself?
Yes. Export the XML file from Squarespace, import it into WordPress with the built-in importer, then pull images across with an image importer and rebuild menus and design by hand. Budget extra time for redirects from old Squarespace URLs so search engines follow your content to the new site.
If a migration is part of an ongoing support engagement, GEENXT’s Freelance Web Support SLA Template covers how to document scope and response times, and the Resources Hub has more free checklists like this one.
