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.
| In WordPress | On the new site | What to review |
|---|---|---|
| Pages and posts | Page and article records with their rendered content. | Count important records and inspect text, embeds, links, and dates. |
| Media library | Files and images used by the imported content. | Check downloads, captions, alternative text, and missing or blocked files. |
| Permalinks and SEO fields | Page routing and search metadata. | Open old addresses and compare titles, descriptions, and canonicals. |
| Categories and authors | Content organization and bylines where available. | Check relationships, archive pages, and pagination. |
| ACF, custom post types, and plugins | A 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.
Enter your WordPress address
Start the migration flow with your live website URL. Private or blocked content needs separate access or input.
Review the first preview
Compare representative pages on desktop and phone. Check navigation and the article layout, not only the homepage.
Resolve the remaining scope
Verify the content inventory, configure forms and services, and plan any private-data transfers.
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.

