Skip to content

Convert WordPress
to Payload CMS.

Give your existing website a new foundation. Preview your site on Payload and Next.js, then review the content, design, and features before you move.

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

The short answer

WordPress to Payload

A WordPress-to-Payload migration moves your content into a different CMS and rebuilds the website that presents it. OffPress brings those tasks into one preview-and-review workflow; your WordPress theme and plugins are not installed inside Payload.

See the starting point

Your site. A new foundation.

woodside.farm
Woodside Farm rebuilt on OffPress
Woodside Farm on its original platform
Original siteOn OffPress

Drag to compare. Use arrow keys when focused.

Familiar design Next.js + Payload underneath

Separate captures of the original sites and their OffPress migration previews. Dynamic content, animation, and capture timing can create small differences. Review your own migration before launch.

Examples rebuilt in our account. These are migration previews, not customer endorsements.

A new CMS behind a familiar website.

Payload is a code-configured CMS and application framework with a content admin and APIs. In an OffPress site, Payload manages content, Next.js presents your pages, and Postgres stores the structured data.

The useful result is a website you can keep publishing to. Check both an imported page and a newly created article. Seeing old content in the preview is only one part of proving that the new editorial workflow fits.

Map the content, not just the homepage.

Use this as a review map. The source site and its access settings determine what is available to import; a custom data model may need separate work.

Map the content, not just the homepage.
In WordPressOn the new siteWhat to review
Pages and postsPage and article records with their rendered content.Count important records and inspect text, embeds, links, and dates.
Media libraryFiles and images used by the imported content.Check downloads, captions, alternative text, and missing or blocked files.
Permalinks and SEO fieldsPage routing and search metadata.Open old addresses and compare titles, descriptions, and canonicals.
Categories and authorsContent organization and bylines where available.Check relationships, archive pages, and pagination.
ACF, custom post types, and pluginsA separate scope of fields and behavior to assess.Confirm access to underlying data and test the replacement workflow.

Make the move in reviewable steps.

Keep your source website accessible while OffPress reads it and you compare the result.

  1. Enter your WordPress address

    Start the migration flow with your live website URL. Private or blocked content needs separate access or input.

  2. Review the first preview

    Compare representative pages on desktop and phone. Check navigation and the article layout, not only the homepage.

  3. Resolve the remaining scope

    Verify the content inventory, configure forms and services, and plan any private-data transfers.

  4. Publish when the site is ready

    Choose hosting, connect your domain, and recheck important URLs and visitor journeys on the live site.

Bring the behavior you need.

A WordPress plugin can provide presentation, content structure, or a business process. Those are different migration tasks. A contact form needs working delivery; a store needs configured payments; a member area needs access rules and accounts.

Historical orders and subscriptions, existing subscriber lists, and customer passwords are not things to assume from a public preview. Record them explicitly and arrange their transfer or replacement before retiring WordPress.

Keep building after the move.

Use Content Admin for publishing and record edits. Use Site Design when you want AI to change the presentation or add behavior, then review the result. Developers can work with the underlying collections and code.

Start with a free preview and review the current credit allowance. Additional AI work uses credits, and publishing on your domain requires a hosting plan. The amount of follow-up work depends on your site’s scope.

Keep the details close.

A few good questions

Before you
press on.

Is this the same as importing a WordPress XML file?

No. The OffPress starting point is your website address and the accessible content and design. A WXR/XML migration is a separate technical approach. Do not assume hidden fields or private records are available from a public URL.

Can Payload keep my WordPress URLs?

The migration aims to carry page addresses across. Verify the actual paths, including dated posts, nested pages, and archives. Where an address changes, configure and test a suitable redirect.

Does an ACF field automatically become a Payload field?

Do not assume it does. Custom fields and relationships need accessible source data and an appropriate target model. Review that scope separately from how the public page looks.

Do I need to use code to edit an article?

You can edit content through the CMS. More complex changes to models or behavior can be made through Site Design or by working with the code. Review a new article as well as migrated content.

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