Skip to content

Keep your design.
Move beyond WordPress.

Start with the website people already recognize. Preview it on a new foundation, compare the details, and decide what you want to improve next.

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

The short answer

Move without a redesign

You can change your website’s platform without choosing a new visual identity at the same time. OffPress starts from the accessible design of your existing site. Review the reconstruction at different screen sizes and test its behavior before treating it as ready.

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 migration and a redesign solve different problems.

Migration changes the foundation. Redesign changes the presentation. Combining them can be sensible, but it makes it harder to tell whether a missing section or changed page address was intentional.

If your existing design still serves your visitors, carry it into the first preview. Record deliberate design changes separately. You can then evaluate the new CMS without asking the team to approve a new identity at the same time.

Review representative pages, not just the hero.

Choose a page from each important layout. Compare at the same viewport width and account for changing banners, animations, and dynamic content.

Review representative pages, not just the hero.
Page or elementCompare the appearanceTest the behavior
Header and navigationLogo, spacing, typography, and mobile layout.Menus, keyboard focus, and destination links.
ArticleBody width, headings, captions, images, and embeds.Inline links, sharing links, related articles, and new-post layout.
Archive or listingCards, grouping, ordering, and page controls.Pagination, filters, and newly published content.
Form or shop pageLabels, fields, product detail, and feedback states.Submit a test; configure delivery or payments separately.

Keep the details that make the site yours.

Fonts, image crops, icons, spacing, and content length affect the overall impression. Make sure important assets are available from the source and that you have the right to keep using them on the new site.

Compare phone and desktop layouts separately. A layout can look convincing at one width and still have clipped text, oversized images, or an unusable menu on a smaller screen.

  • Check logos and fonts against the original.
  • Inspect long headings, tables, and image captions on a phone.
  • Try hover, focus, expanded, and error states.
  • Check content below the first screen and in the footer.

Make review notes that lead to a useful fix.

Name the page, the screen size, and the expected behavior. “On the contact page at phone width, the submit button extends beyond the form” is more useful than “the mobile version looks wrong.”

Ask for adjustments in Site Design and compare the next preview. Keep a separate list for functionality that needs configuring, such as form delivery, payment credentials, or third-party embeds.

Give the familiar design somewhere to grow.

Once the rebuilt site works and its content is accounted for, you can change the design at your own pace. Start with an improvement that has a purpose: clearer navigation, a stronger service page, or a more useful article index.

Keep testing your existing URLs and core visitor journeys as the design evolves. Visual continuity is useful, but a faithful screenshot alone is not a complete migration.

Keep the details close.

A few good questions

Before you
press on.

Is the result guaranteed to be pixel-perfect?

No. The preview is there so you can compare the result. Dynamic content, inaccessible assets, responsive behavior, and custom interactions can need follow-up work.

Can I keep an Elementor or Divi design?

The publicly visible design can be the starting point for a reconstruction. Test the actual pages and interactions. Keeping the appearance does not mean the original builder or its modules run inside Payload.

Can I redesign after migrating?

Yes. Review the migration first, then request design changes in Site Design. Keeping those reviews separate helps you identify missing content and unintended behavior.

Will my forms and menus work because they look the same?

Appearance is not proof of functionality. Follow every important navigation path and submit test forms. Check delivery, validation, and any required service setup.

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