Skip to content

Your WordPress move.
A clear checklist.

Know what to bring, what to test, and what needs separate setup. Start a preview, then work through the move without losing track of the details.

Start with a free preview. Keep your original website live.
AI credits and hosting explained

The short answer

WordPress migration checklist

A migration is ready when you have reconciled the content, reviewed the design, tested the business workflows, and planned the domain change and rollback. Use the checklist below for the whole move, rather than treating a finished homepage as proof of completion.

01 / Before you start: make an inventory.

Keep a simple record of each item, who owns the review, its status, and any unresolved issue. Export or back up the source before making changes.

  1. Collect important URLs

    Use the sitemap, navigation, analytics, and known external links. Include landing pages, older articles, PDFs, category pages, and other useful destinations.

  2. Count content separately

    Pages, posts, media files, products, and private records are different inventories. A page-layout count is not a record count.

  3. List plugins by behavior

    Record what each one does for visitors or staff, which external services it uses, and the data it stores.

  4. Identify access and ownership

    Confirm who controls the domain, DNS, hosting, assets, email service, payment provider, and integrations.

02 / In the preview: compare the site.

Choose representative pages first, then check the inventory. Keep the old website available while you review.

  • Read imported text and check headings, links, images, downloads, and embeds.
  • Compare the homepage, ordinary pages, articles, archives, and special layouts on desktop and phone.
  • Open the CMS and create a test article. Check its layout and where it appears.
  • Match important page addresses and compare titles, descriptions, canonical tags, and indexability.
  • Log missing records and files explicitly; do not assume an attractive preview means the whole archive is present.

03 / Before launch: prove the workflows.

Assign each business-critical journey a person who can confirm it works. Keep private-data transfer work separate from the public-page review.

03 / Before launch: prove the workflows.
WorkflowAcceptance check
Contact formSubmit realistic valid and invalid inputs; confirm delivery and any consent or follow-up action.
NewsletterVerify signup, subscriber handling, sending-domain setup, and unsubscribe behavior. Existing lists need separate planning.
StoreConfigure payments and check the purchase journey, confirmation, and delivery. Plan historical orders and subscriptions separately.
Members or customersVerify access rules, account setup, recovery, and private content. Do not assume old passwords transfer.
Navigation and searchCheck mobile menus, internal links, search results, and important empty/error states.

04 / At launch: make the switch deliberately.

Choose a quiet period and decide how content changes made during migration will reach the replacement. Avoid two teams unknowingly publishing into different systems.

  1. Agree the final content state

    Use a short content freeze or a documented final update. Reconcile anything added since the preview was prepared.

  2. Record the rollback route

    Keep the prior hosting and DNS configuration available. Name the person who decides whether to revert.

  3. Connect the domain

    Apply the host’s domain instructions, preserve email records, and confirm HTTPS and the preferred hostname.

  4. Run live checks

    Test old URLs, forms, key pages, assets, and business workflows on the real domain.

05 / After launch: watch the real result.

Check for missing pages, unexpected redirects, failed forms, and delivery problems. Verify analytics and Search Console access on the live domain, and compare results with the baseline you recorded before the move.

Do not cancel the old hosting just because DNS now points elsewhere. Confirm that files, data, integrations, and rollback requirements have been addressed, then archive what you need and retire the old service deliberately.

A useful review record: item → original address → new address → owner → tested result → issue or follow-up.

Keep the details close.

A few good questions

Before you
press on.

What should I check first?

The content inventory and your most important visitor journeys. They define the scope. Start the visual review with representative layouts rather than only the homepage.

Can I keep publishing while the migration runs?

You can keep the source live, but new edits need a plan. Use a final content reconciliation or a short publishing freeze so late changes are not missed.

Is the preview the same as launching?

No. A preview lets you review the replacement. Publishing, configuring the domain, and testing the live site are separate steps.

How long will the migration take?

The scope determines the work: content volume, access, layout variety, integrations, and private data all matter. Use the preview and inventory to establish what remains instead of relying on a universal completion time.

Keep what matters. Build what’s next.

See your own site.
Then decide.

Start with a free preview while your WordPress website stays live. Review the result and any follow-up work before choosing hosting and moving your domain.

Starting with a new idea? Build from scratch