Agentic Website

WordPress to Next.js migration

Convert WordPress to Next.js.

Move your pages, posts, design, media, important URLs, and search signals into an agent-ready codebase your team owns. Start with a 1-1 clone of your homepage, review it, then migrate the rest of the site.

Copy Migration PromptSee how the migration works

A complete WordPress migration

Move the content, design, and features people depend on.

A WordPress site combines content, a theme or page builder, Media Library files, permalink rules, SEO fields, and plugin-powered features. A complete move gives each part a clear home in the new website.

WORDPRESS EXPORT + LIVE SITEwordpress-export.xml
WXR
Posts, pages, custom fields, and taxonomiesexport
Theme, blocks, and page-builder designrecreate
Media files and asset referencesmove
Plugins, forms, SEO fields, and redirectsreconnect

Why other migration methods fail

01

The pages arrive. The theme and builder design stay behind.

The published layout comes from templates, theme styles, blocks, and page-builder settings that need to be recreated in the new components.

02

The posts move. Custom content has nowhere to go.

Custom post types, ACF fields, taxonomies, and relationships need a matching content model and route plan.

03

The form still renders. The plugin workflow is gone.

Lead delivery, spam protection, emails, and automations need to be reconnected and tested.

04

The new blog works. Old permalinks lead to missing pages.

Every post, archive, category, tag, and changed path needs a clear destination or direct redirect.

The better end state

Same website. More room to move.

Visitors keep the content and experience they know. Search engines keep the paths and signals that matter. Your growth team gets an owned repository it can update with an AI coding agent and review before every release.

Keep

The content and experience people already rely on.

  • Content and brand design
  • Posts, pages, and media
  • Valuable public URLs
Gain

A site your team and its agents can keep improving.

  • Owned code and deployment
  • Agent instructions and context
  • Reviewable releases

What needs to move

Account for every part of your WordPress site.

List the content, design system, custom fields, media, plugin jobs, and URLs before the build begins. Each item gets a clear next step.

01

Pages, posts, and templates

Every public route and the content behind it

List pages, posts, archive pages, author pages, category pages, tags, drafts that matter, and the templates that turn each content type into a public route.

  • Public route list
  • Post and page exports
  • Archive pages
02

Theme and page builder

The design created by your theme, blocks, or builder

Record the live layouts and responsive behavior. Map Gutenberg blocks, Elementor sections, reusable blocks, headers, footers, typography, and spacing into Next.js components and design tokens.

  • Theme styles
  • Builder layouts
  • Reusable components
03

Custom content and fields

Custom post types, taxonomies, and field relationships

Find content created by plugins or custom code, including ACF fields and relationships. Give each field, slug, archive, and reference a clear place in the new content model.

  • Custom post types
  • ACF fields
  • Taxonomies and references
04

Media Library

Images, files, captions, alt text, and source URLs

Download the files the site uses, keep useful filenames and alt text, update content references, and confirm that the new site no longer depends on temporary WordPress media URLs.

  • Original files
  • Alt text and captions
  • Updated asset links
05

Plugins and site features

Forms, search, memberships, commerce, and automation

List what each active plugin does for visitors and the marketing team. Rebuild the required experience or connect a replacement for forms, search, email, redirects, gated content, and payments.

  • Plugin job list
  • Form delivery
  • Feature replacements
06

URLs and search

Permalinks, metadata, schema, redirects, and crawl settings

Keep valuable post and page URLs, map category and tag paths, carry SEO fields forward, add direct redirects, and check canonicals, structured data, robots rules, and the sitemap.

  • Permalink map
  • SEO plugin fields
  • Redirect and crawl checks

Step-by-step migration plan

Move your WordPress site in five clear steps.

Each step ends with something your team can review before the next one begins.

  1. 01

    List what exists

    List every public route and the WordPress setup behind it.

    Crawl the live site, export the available content, record the theme or page builder, list custom content types, and write down the job of each active plugin.

    OutputRoutes, content exports, assets, theme details, and plugin jobs
  2. 02

    Plan the content

    Choose what will keep using WordPress.

    Keep WordPress as the content editor for a headless setup, or move the content into files or another CMS. Choose a new home for forms, search, redirects, and every feature the site still needs.

    OutputContent source and replacement plan for each site feature
  3. 03

    Review the first clone

    Clone the homepage and one content-heavy route first.

    Build the homepage and one representative post, archive, or custom content page. Review the design, responsive behavior, content fields, and internal links before expanding.

    OutputDesktop and mobile review of two working routes
  4. 04

    Move the rest

    Build the remaining routes and reconnect the site features.

    Apply the approved components, migrate the remaining content and media, reconnect forms and integrations, and add metadata and redirects for each route.

    OutputComplete preview with content and integrations working
  5. 05

    Go live

    Run final checks, move the domain, and monitor the launch.

    Test pages, forms, search, analytics, redirects, canonicals, robots rules, and the sitemap. Connect the domain, then watch search traffic and lead delivery.

    OutputLaunch report, redirect monitoring, and issue list

Copyable migration prompt

Start in a new Claude Code or Codex terminal.

Let your coding agent clone the starter, or run the setup in your CLI. Add your current WordPress website and copy the ready-to-use steps.

migration-prompt.txt
I want to migrate my WordPress website ([YOUR WEBSITE URL]) to Next.js using this starter: https://github.com/Synscribe/launch-template.

Clone the starter into a new folder and open it. Read README.md and AGENTS.md, then run /site-clone with my source URL. Follow the skill and stop at the first review checkpoint.

One detail first

What WordPress website are you moving?

The migration is the starting point

Keep the new site easy to edit and maintain.

The Agentic Website Template gives marketing teams the instructions, reusable components, search foundations, and launch checks to keep improving the site after the move.

Read the Agentic Website manifesto

Clone any design

Turn your WordPress theme or page-builder design into clean components.

The clone workflow follows the website visitors already know, including custom layouts, responsive behavior, and important interactions. Approved patterns become reusable Next.js components for the rest of the migration.

  • Theme and builder layouts
  • Responsive states
  • Reusable sections

Stay visible

Help search engines and AI tools understand every important page.

Important copy and links arrive in the page HTML. Clear routes, metadata, structured data, sitemaps, and discovery files help crawlers find and understand the new site.

  • Server-rendered content
  • Explicit public routes
  • Discovery foundations

Keep marketing moving

Let your marketing team work directly with its coding agent.

Project instructions, goals, design tokens, brand voice, example content, and reusable components give Claude Code, Codex, or Cursor useful context for the next page request.

  • Rules stored with code
  • Reusable page patterns
  • Reviewable changes

Maintain it with confidence

Review every update before it reaches customers or crawlers.

The launch checklist and audit keep checking identity, public URLs, discoverability, forms, placeholders, and production settings as the site grows.

  • One launch checklist
  • Automated site audit
  • Safe preview defaults

Before you move

WordPress migration questions

01Is this an automatic WordPress to Next.js converter?+

This is a structured migration workflow for an AI coding agent and a human reviewer. The agent records the public site and available exports, maps WordPress content and plugin jobs, rebuilds representative routes, and compares the result before the work expands.

02Can I keep WordPress as the CMS?+

Yes. WordPress can remain the content backend while Next.js becomes the public website. Posts, pages, media, users, categories, tags, and other configured content can be read through the WordPress REST API or a GraphQL plugin. You can also move the content into another CMS or repository files during the migration.

03What does the standard WordPress export include?+

The WordPress export creates a WXR XML file containing posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, users, and navigation menus. The live design, theme behavior, and plugin-powered features still need their own migration plan.

04What happens to Gutenberg or Elementor layouts?+

The migration records the published pages and rebuilds the design as reusable Next.js components. Gutenberg stores block content in post content, while page builders add their own templates, settings, and plugin dependencies. Review representative pages before converting the rest of the site.

05What happens to custom post types and ACF fields?+

Map each custom post type, taxonomy, field, relationship, archive, and public URL. Custom post types must be configured for REST access when WordPress remains the content backend. ACF field groups also have a setting that controls whether their values appear in REST responses.

06Will moving from WordPress affect SEO?+

Any site move can cause temporary search changes. Keep useful permalinks, add direct permanent redirects for changed paths, carry SEO titles and descriptions forward, update internal links, preserve structured data, and monitor the launch in Search Console.

07What happens to WordPress plugins and forms?+

Record the job each plugin performs. Forms need a submission service and lead destination. Search needs an index. Memberships, commerce, comments, multilingual content, and automation each need an owned implementation or a connected service before launch.

Checked against current WordPress and plugin guidance

Keep the content. Change who controls the website.

Move from WordPress to an agent-ready Next.js codebase.