What's the most important step in a WordPress migration?
The single most important step in any WordPress site migration checklist is testing everything on a staging environment before switching DNS — this keeps the live site fully functional throughout the process and lets you catch broken plugins, missing redirects, or configuration errors while visitors are still unaffected. Skipping staging is the most common cause of avoidable downtime.
Why most migration problems happen before or after, not during
It's tempting to think of a migration as a single event — moving files from one server to another. In reality, the file transfer is usually the easy part. The steps that prevent downtime and lost SEO happen in the planning stage, and the steps that catch silent breakage happen after launch. Skipping either end of that timeline is where most wordpress migration steps go wrong. If you're coming from Wix rather than another WordPress host, there are no files to transfer at all, so read how a Wix to WordPress migration works first.
Pre-migration: preparation (steps 1-6)
- Take a full backup of files and database on the current host, and confirm you can actually restore it — an untested backup isn't a real backup.
- Audit your plugins and themes for anything outdated, abandoned, or redundant; migrations are a natural point to retire what you no longer use rather than carrying dead weight to the new host.
- Document custom code and integrations — payment gateways, CRM connections, custom post types — so nothing gets missed when rebuilding on the new environment.
- Set up a staging environment on the new host and do the actual file/database transfer there first, keeping the live site untouched.
- Update internal configuration on staging — database credentials, file paths, and any hardcoded URLs — so the site functions correctly before it's public-facing.
- Lower your DNS TTL (time to live) a day or two ahead of the planned cutover — a shorter TTL means resolvers cache your record for less time before checking for an update, so the eventual switch propagates faster.
Migration day: the cutover (steps 7-11)
- Do a final content sync to capture anything published or changed since the initial staging transfer — new posts, comments, orders if you run WooCommerce.
- Install and configure SSL on the new server before going live, so visitors never hit an insecure-connection warning — most hosts can issue a free, automated TLS certificate through Let's Encrypt, so there's no cost reason to skip this.
- Test the staging site thoroughly one more time — forms, checkout flow if applicable, page speed, and key user paths — with fresh eyes before flipping DNS.
- Switch DNS to point to the new host, ideally during a low-traffic window, and keep the old server running untouched as a fallback.
- Monitor propagation and confirm the new server is serving traffic correctly as DNS updates roll out across resolvers.
Post-migration: verification (steps 12-15)
- Test all redirects, especially if any URL structures changed, to make sure old links land on the correct new pages rather than 404ing.
- Run a full broken-link and image check across the site — migrations frequently break relative paths or media references that aren't obvious from a quick glance.
- Resubmit your XML sitemap in Google Search Console — this helps Google discover and process the site's URLs faster after a move than waiting for a routine crawl — and verify the new host isn't accidentally blocking crawlers via a stray
robots.txtrestriction carried over from staging. - Re-run a performance check (Core Web Vitals, load time) on the new host to confirm the migration actually delivered the performance improvement you expected, not just a change of address.
Checklist at a glance
| Phase | Key risk if skipped | Steps |
|---|---|---|
| Pre-migration | Data loss, missed dependencies | 1-6 |
| Migration day | Downtime, broken SSL, rushed testing | 7-11 |
| Post-migration | Lost SEO rankings, broken links, silent errors | 12-15 |
How do you migrate without losing SEO?
Keep URLs identical wherever you can, 301-redirect every URL that must change, lock the staging site so it can't be indexed, resubmit your XML sitemap in Search Console after launch, and check that canonical tags point to the live site. Most ranking drops after a migration come from skipping one of these, not from the move itself.
Search engines index URLs, not servers, so a host change on its own shouldn't affect rankings. The risk comes from what changes alongside it: URL structures, redirect handling, an indexed staging copy, or a robots.txt left blocking everything after testing.
Keep your URL structure
If a page lived at /services/web-design/ before the move, it should live there afterwards. Every backlink, bookmark and search result points at your current URLs; change them without redirects and those signals are lost.
Build a 301 redirect map before cutover
- Export every existing URL from your XML sitemap, Google Search Console and your analytics landing-page report. Combining sources catches pages missing from any one of them.
- Match each old URL to its new destination, including pages being merged or removed. Send those to the closest relevant page, not the homepage.
- Use 301 (permanent) redirects, not 302s. Google says a permanent redirect is a strong signal that the new URL should be canonical; a temporary one isn't.
- Test every redirect after launch and check that each resolves in one hop, not a chain.
- Keep the redirects for at least a year, and indefinitely where practical. Google's site-move guidance asks for at least a year.
Lock the staging site
Protect staging with a password or IP restriction, not just a robots.txt disallow. Google says a disallow isn't a way to keep a page out of search results, and a disallowed URL can still be indexed if it's linked from elsewhere. If a staging URL was indexed, request its removal in Search Console once it's shut down.
Resubmit the sitemap and check canonicals
Submit the updated XML sitemap in Search Console after launch, which helps Google find the changed URLs faster. Check that canonical tags point at the live domain: rel="canonical" is a strong signal for which URL Google treats as the main one, so a canonical still pointing at staging or the old domain can undercut rankings.
Post-migration testing and SEO monitoring
| Check | Tool | Why it matters |
|---|---|---|
| Redirects resolve in one hop | Redirect checker or manual test | Keeps backlinks and link equity |
| Sitemap resubmitted | Google Search Console | Speeds up re-crawling |
| No staging URLs indexed | site: search, Search Console |
Prevents duplicate content |
| Canonical tags correct | Page source, crawler | Consolidates signals on the right URL |
| Crawl errors and page indexing | Google Search Console | Catches pages Google can't reach |
| Forms, checkout and key paths | Manual test | Catches silent breakage a visual check misses |
Watch these for at least a few weeks after launch. Google says a medium-sized site can take a few weeks for most pages to move over in search, and larger sites take longer.
Mistakes that turn a simple checklist item into a real problem
Even with a full site migration plan in hand, a few specific mistakes account for most avoidable migration headaches. Knowing them ahead of time makes it much easier to spot when a "simple" step is quietly at risk.
Skipping the backup restore test
Taking a backup is not the same as confirming it works. A surprising number of migration disasters trace back to a backup file that turned out to be incomplete, corrupted, or password-protected in a way nobody remembered — discovered only when it was needed. Restoring the backup to a throwaway environment before you rely on it costs very little time and removes this risk entirely.
Rushing the plugin audit
It's tempting to skip step 2 and just carry every plugin over as-is, especially on a site that's been running for years. Old, abandoned plugins are disproportionately likely to break on a new server environment or PHP version, and tracking down which one caused an error after the fact takes far longer than auditing them up front.
Treating DNS TTL as an afterthought
Lowering DNS TTL only makes a difference if it's done far enough in advance — changing it the same day as cutover doesn't help, because resolvers around the internet keep serving your old record until their own cached copy expires, and a longer TTL means that takes longer. This step needs to happen on its own timeline, separate from the rest of migration day.
Declaring victory too early
The most common post-migration mistake is stopping verification once the site visibly loads correctly. Broken redirects, blocked crawlers, and missing form integrations often don't show up in a quick visual check — they show up in analytics dips or lost leads weeks later. Running through steps 12-15 in full, not just a glance at the homepage, is what actually closes the loop.
For the timeline, see how long a website migration takes; if you're still deciding whether to move, see the signs you've outgrown your hosting.
FAQ
robots.txt after migration is frequently forgotten, because the site "looks fine" to a human visitor even when a crawler-blocking setting carried over from staging. This can quietly hurt search visibility for weeks before anyone notices.robots.txt block. Keep URLs and speed the same or better and those risks go away.Run the free WordPress Migration Cost & Downtime Estimator →
WordPress Migration Cost & Downtime Estimator
Estimate the cost and downtime of moving your site.
Written by
Founder, ToolsForge
Founder of ToolsForge and a WordPress & WooCommerce developer. Builds the free calculators on this site and writes the guides behind them — every guide pairs real, sourced numbers with a tool so you can run your own.




