lenexa.bot Website Studio
DocsWebsite Studio

WordPress

How a WordPress move works

The steps of a WordPress move in Website Studio, from the export file to redirects and the worth-a-look list, and the two decisions you make.

Published Updated

Lenexa.AI3 min readApplies to: All plans

How does the crew move my WordPress posts?

It depends on your site's size and setup, but the steps are the same. The Lead Developer collects your posts, usually from a WordPress export file you download in two minutes, and converts them all at once with tested scripts. Then it checks the result, writes a redirect for every old address and lists the posts worth a look. You decide where old category, author and tag addresses go and how you'll post afterward. Nothing changes on your live site until you give the go-ahead.

Worth a look: the short list of moved posts the conversion flagged for a person to check, such as a missing image or a form from an old plugin. It is a review list, not a failure.

Facts as of October 2026.

Start the move

Move my blog at example.com/blog off WordPress onto a new design. Keep every post and keep every old link working. Show me the design before you build it.

Lenexa plans it as a design card for the blog's look and one move card for all the posts. The Website Designer designs the blog with a few sample posts; the Lead Developer moves everything.

The steps

  1. Get your posts

    The crew first tries to read the posts from your live site. Often it can't reach it from the Studio, and then the card asks for your export file: "In your WordPress admin, open Tools, then Export, choose All content, and click Download Export File." Attach that file to your message to Lenexa.

    Needs you: add your WordPress export file
  2. Convert every post at once

    Tested scripts convert all the posts in one go, with their titles, dates, authors, categories, tags and images. The crew doesn't retype posts one by one, which keeps the move fast and the cost low.

  3. Map old addresses to new ones

    The crew writes a mapping sheet: each old address and its new one. It asks where old category, author and tag pages should go, with the options and a recommendation.

    Needs you: decide where category, author and tag addresses go
  4. Check and write redirects

    A verify step checks every converted post. Then the crew writes redirect rules for every changed address. Deployment adds them on your host when it publishes.

  5. Review the worth-a-look list

    Lenexa tells you how many posts were flagged, the three that matter most and why, and where the full list is. Typical reasons: an image that was already missing on the old site, a complex table kept as a table, or a form from an old plugin that didn't come over.

    Needs you: review the posts worth a look
  6. Publish when you say so

    Deployment publishes only after your go-ahead. You can ask for it to go to a separate folder first, check it there, then switch.

    Needs you: give the go-ahead

What a move costs

It depends on the size of the blog. For scale: in the NameHero field note, the scripted move of 1,227 posts took about an hour and about $6.50 of AI usage. Design, featured images and the writing area were extra.

Questions Lenexa will ask

  • Where should old category, author and tag pages go? Keep them as pages, or send them to the closest new page.
  • How will you add posts after the move? By asking Lenexa, or with a writer login for your team. See new posts after a move.