Choose what happens to WordPress.
The phrase “WordPress to Next.js” covers two different projects. Decide which one you mean before estimating the work.
| Decision | Headless WordPress | Next.js + Payload on OffPress |
|---|---|---|
| Content editor | Keep publishing in WordPress. | Publish in the new CMS. |
| Frontend | Build Next.js pages that read WordPress data. | Rebuild pages on Next.js using the imported content. |
| Existing plugins | Backend plugins may remain useful; frontend behavior still needs integration. | Identify the required behavior and configure or recreate it. |
| Ongoing systems | Maintain WordPress and its connection to the new frontend. | Operate the new stack and its services; managed hosting handles the hosted environment. |
A page is more than its visual layout.
An article page may depend on its author, category, related posts, media, and original address. An archive needs pagination and a reliable way to include newly published content. Rebuilding the visible template is one part of that system.
Choose representative URLs before starting: the homepage, an ordinary page, a long article, a category archive, a search result, and a form or shop page. Use them as a small functional review set, then reconcile the rest of the content inventory.
- Check that the same important addresses open the right content.
- Publish a test article and check where it appears.
- Try menus, search, forms, and outbound links.
- Inspect phone layouts and keyboard navigation as well as desktop screenshots.
Rebuild the design for the new runtime.
A WordPress theme usually combines templates, styles, and behavior that expect WordPress. OffPress reconstructs the accessible website on the new stack; it does not execute the PHP theme inside Next.js.
Keep the original look for the first review if continuity matters. Once the content and functionality are accounted for, make design changes with a clearer view of what the migration itself changed.
Measure the result on your actual site.
A framework name does not guarantee a fast website or higher rankings. Images, fonts, scripts, page complexity, data access, and hosting all affect the result.
Compare representative pages under the same device and network conditions. Test loading, interaction, and the real journeys people use. A lighter homepage does not compensate for a broken contact form or missing archive.
Preview before you commit to the move.
Enter your WordPress address to start an OffPress preview. Review the result and the work still required while your existing site remains available. You can inspect the code, edit content, and ask for changes before deciding when to publish.
If keeping WordPress as the backend is a requirement, plan a headless WordPress implementation instead. OffPress’s migration path is intended for moving the website onto Payload.