Move from The7 to a Next.js storefront

Export the content of a The7 store and you get text and images with almost none of the appearance attached. Header layout, product page structure, typography, spacing, mobile behaviour, the mega menu configuration — all of it sits in theme options, and some of it is overridden per page, per category and per post type. A migration reads those panels and transcribes them, screen by screen, and there is no shortcut. Budget it as its own line item, because a quote priced from page count will miss it entirely and the gap shows up as a change request in week three.

• Screenshot every options screen before development begins
• Record per-page and per-category overrides separately from global settings
• Check the mobile-specific settings — they are often a different configuration entirely
• Treat options transcription as a distinct deliverable, not part of page rebuilding

The7 supports both WPBakery and Elementor, and stores that have been live for several years usually contain pages built in each — an older set from whichever builder the demo installed, and a newer set from whatever the last developer preferred. That doubles the extraction work, because the two formats have nothing in common: WPBakery content is shortcodes in post_content, Elementor content is a JSON tree in post meta. Audit this before quoting. If both are present and the split is roughly even, expect the extraction estimate to be close to the sum of two migrations rather than a blend of them.

Much of what looks like theme functionality comes from The7 Elements, the companion plugin: photo scrollers, carousels, testimonial widgets, portfolio grids, several product-page components. That matters twice. Disabling the theme without the plugin gives a misleading audit, and every Elements component on a template needs its own rebuild decision.

A theme that exposes every visual decision as a setting has to ship the CSS and JavaScript for all of them on every template, because it cannot know in advance which page uses what. Add a builder doing the same, plus The7 Elements, and the baseline weight arrives before your content does. That is where 71/100 and 4.3 seconds come from. It is also why tuning inside the theme has a low ceiling — worth finding before paying for anything larger.

The7 ships its own optimization tooling and integrates with minification plugins such as Fast Velocity Minify, and a store that has never enabled any of it is not a fair test of what the theme can do. Spend a week: turn on the theme's asset optimization, disable the Elements components you cannot point at in the storefront, fix images, and re-measure with field data rather than a lab score. Green mobile vitals at the end of that week end the discussion, and we would rather say so at audit than after an invoice. A gap that survives the week is structural, and then the conversation is a real one.

The7 is a general-purpose theme, so its stores usually carry more than a catalog: portfolio post types, team pages, service pages, a blog with custom layouts. These are cheap to forget and expensive to discover late, particularly because they often use their own The7 templates and their own URL patterns. Inventory every registered post type at the start, not just products and pages. Two decisions follow for each: does it still earn its place, and if so does it need a bespoke template or can it collapse into a simpler one.

A few hundred products, steady sales, green field data once the optimization pass is done — that store should keep its theme. If your team edits pages weekly through the options panel and nobody wants to involve a developer for a copy change, moving to Next.js removes that unless the build deliberately keeps an editing path — and that has to be scoped up front, not discovered afterwards. And if only one of the two builders is actually in active use and the rest is dormant content nobody visits, consolidating inside WordPress is a much cheaper project than replatforming the frontend.

Options transcription and the builder audit come first, because together they set the price and either can change the decision. Rebuild the product template next, since on The7 stores it is where options overrides cluster most densely. Categories and filters follow, then the marketing and portfolio content in whatever order traffic justifies. Keep checkout on WooCommerce for the first launch. One The7-specific caution: keep the theme and The7 Elements installed but inactive until the redirect map has run in production for a fortnight, because dormant post types have a way of surfacing URLs nobody mapped.