CMS websites

WordPress website migration

A WordPress migration can mean moving an existing WordPress site to a new host, moving to a new domain, or moving content onto WordPress from another platform. Each carries the same core risks: content or media left behind, broken links, lost search visibility, forms and email that stop working, and downtime during the switch. A careful migration starts with an inventory, maps every URL that will change, uses permanent redirects, tests the new setup before switching and checks thoroughly afterwards.

This page explains the kinds of migration, the steps, redirects and search guidance from Google, testing, the cut-over and what to watch afterwards. LetGetGrow builds, redesigns and maintains WordPress and Webflow websites, with the scope, cost and timeline of each project set out in a custom quotation.

Service overview · Web & E-commerce · Custom quotations only

Illustrative diagram

  1. Inventory
  2. Backup
  3. Move and map
  4. Test
  5. Switch
A WordPress migration. Inventory, backup, move, test, switch.

Kinds of WordPress migration

Illustrative comparison
MigrationWhat changesMain risks
New host, same domainServer and filesDowntime, email and DNS settings
New domainEvery URLSearch visibility, links
Onto WordPress from another platformContent structure and URLsContent left behind, layout changes
Restructure during the moveMany URLs and templatesRedirect gaps

Start with an inventory

List every page, post, media file, form, user account, plugin and integration on the current site, along with redirects that already exist. Export the list of URLs from a sitemap or a crawl. The inventory is the checklist for confirming nothing was left behind, and the basis for mapping URLs.

URL mapping and redirects

Google's guidance for site moves with URL changes is to map each old URL to its new equivalent and use server-side permanent redirects, such as 301 or 308, directly to the final destination. Google states that permanent redirects do not cause a loss in PageRank. Update internal links to the new URLs and submit a sitemap listing them. If only the host changes and URLs stay the same, no redirects are needed.

Changing domain

Moving to a new domain changes every URL. As well as redirects, Google's Change of Address tool in Search Console applies to moves from one domain or subdomain to another, though not to a switch from HTTP to HTTPS. Keep the old domain registered so its redirects keep working.

Steps in a migration

  1. Inventory

    Pages, media, forms, plugins, URLs.

    Output: Inventory list

  2. Backup

    Full copy of files and database.

    Output: Restorable backup

  3. Move and map

    Content to new setup; URL map.

    Output: Site on new setup

  4. Test

    Pages, forms, redirects, email.

    Output: Test results

  5. Cut-over and check

    DNS switch, monitoring.

    Output: Live and verified

Example: moving a practice site to a new domain

Illustrative example — not a client case study

Situation: A physiotherapy practice rebrands and moves its WordPress site to a new domain.

  1. An inventory lists all pages and blog posts; a spreadsheet maps each old URL to the new domain.
  2. Permanent redirects are set from the old domain; internal links and the sitemap are updated.
  3. The Change of Address tool is used in Search Console, and the old domain is kept registered.

What this shows: Old links continued to reach the right pages after the rebrand. This example is illustrative.

Migration checks

Before

  • Inventory complete
  • Backup restorable

During

  • Redirects mapped one-to-one
  • Forms and email tested

After

  • No unexpected error pages
  • Sitemap with new URLs submitted

Testing before the switch

Test the site on its new setup before visitors are sent there: every template, forms delivering to the right inboxes, search, logins, media, and a sample of redirects. If email runs on the same domain, check that changing DNS will not interrupt it.

The cut-over

Choose a quiet time, freeze content edits on the old site, take a final backup, switch DNS or redirects, and check the live site straight away. DNS changes can take time to reach everyone, so keep the old setup running until traffic has moved.

After the move

Google notes that rankings may fluctuate temporarily during a move and that it can take time for new URLs to be picked up. Watch for error pages and missing redirects in Search Console and analytics, and fix gaps quickly.

Moving onto WordPress

Content from another platform rarely maps perfectly. Decide how pages, posts, categories and media map to WordPress content types, test an import on a sample first, and expect some manual tidying of formatting.

Media and file paths

Images and documents are often linked by full addresses inside page content. When the domain or folder structure changes, those links can break even if the files moved. Check that media paths have been updated throughout the content, and that PDFs and downloads linked from other sites are redirected too.

Questions about WordPress website migration

What is a WordPress migration?

Moving a site to a new host or domain, or moving content onto WordPress.

Do we need redirects?

Yes, for every URL that changes, using permanent redirects.

Will we lose rankings?

Google notes temporary fluctuation is possible; careful redirects help.

What is the Change of Address tool for?

Moves from one domain or subdomain to another.

Can email be affected?

Yes, if DNS changes are made without checking email settings.

Should we keep the old domain?

Yes, so its redirects keep working.

Sources referenced

Platform features, guidance and rules change. We check the current versions before committing to an approach. This page is general information, not legal advice.

Request a Custom Quote

Ask about WordPress website migration

Project details

Enquiry about: WordPress website migration

Fields marked with an asterisk are required.

What do you want to achieve, what exists today, and any deadlines or constraints.

Include your country code.

Request a quote