Move from Elementor to a Next.js storefront
Hello Elementor runs 8.6% of WooCommerce stores. Migrating one means rebuilding Theme Builder conditions and Loop Grid queries, not copying page layouts.

Most Elementor to Next.js migrations are quoted wrong because the quote is based on page count. Pages are the cheap part. The expensive part is that Elementor Pro's Theme Builder replaced your theme's template hierarchy with a conditions system (a product template that applies to one category, an archive template that applies to everything except that category, a header that swaps on checkout), and none of it is visible from the front end. You find it by opening Theme Builder and reading the condition list. Stores that have been on Elementor for four years routinely have templates whose conditions overlap in ways nobody intended, and the migration is the first time anyone notices.
Hello Elementor and Elementor Pro are two separate problems
Hello Elementor is deliberately almost nothing: a stylesheet stub whose entire job is to get out of Elementor's way. It is the second most common WooCommerce theme at 8.6% of stores, and it contributes close to zero of the weight anyone complains about. Everything you would want to migrate lives in Elementor Pro: the widgets, the Theme Builder templates, the global kit, the popups. So the sentence "we want to move off Hello Elementor" describes almost no work, and the sentence "we want to move off Elementor Pro" describes all of it. Getting this distinction wrong at quoting time is how a migration ends up half-priced and half-finished.
Theme Builder conditions are your real site map
Before touching code, export the condition list from Theme Builder. Every template declares where it applies (all products, products in a taxonomy, a specific page, everything but the cart), and the resolution order decides which one wins when two match. This is the routing logic of the store, written in a UI, and it is the single most common source of post-launch surprises. The pattern we hit most often: a store has a general product template plus one override for a category added during a campaign two years ago, nobody remembers it, and after migration those forty products render with the wrong layout because the override was never carried across.
- Export every Theme Builder template with its conditions before development starts
- Map overlapping conditions and resolve which one is actually rendering today
- Check singular, archive, product, cart, checkout and 404 separately, since each is its own template
- Any template whose condition nobody can explain gets tested on live before it is dropped
Read _elementor_data, do not scrape the rendered page
Elementor stores each page as a JSON tree in the _elementor_data post meta field. Extracting from that tree gives structured content: sections, columns, widget types, settings, the actual text and image IDs — which is what a component rebuild needs. Scraping the rendered HTML gives you Elementor's wrapper divs, its inline styles and its class names, which is what you are migrating away from. The JSON path costs more upfront and it is the only one that produces a clean storefront. There is one honest exception: under about fifteen builder-made pages, writing a parser is not worth it, and rebuilding by hand from screenshots is faster.
- Extract from _elementor_data post meta, not from the front end
- Map widget types to components once, then reuse across every page
- Resolve image IDs to the media library rather than copying rendered URLs
- Keep the text verbatim — rewriting copy during a migration makes ranking changes unattributable
Count widget types, not pages
The mapping table is where an Elementor rebuild gets priced honestly. Every element in the _elementor_data tree carries an elType (container, section, column or widget), and every widget a widgetType such as heading, image, text-editor or loop-grid. One query across post meta returns the distinct widget types the store actually uses, and that list, not the page total, is the build. Each type becomes one component, written once and reused on every page that carries it. As a scenario: a 300-page store using 25 widget types costs less to move than an 80-page store using 60. Add-on packs such as Essential Addons or JetElements register widget types of their own, and those are the expensive rows, because each pack stores its settings in its own shape and nothing outside the plugin documents it. Global colors and fonts come from the active kit, whose post ID sits in the elementor_active_kit option. Map them to design tokens before writing any component, or every component hard-codes a hex value the kit used to own.
- Inventory distinct widgetType values across all _elementor_data rows
- Flag every add-on widget type, since each needs its output reverse-engineered
- Turn the kit's global colors and typography into tokens first
- Retire widget types used on one page nobody visits instead of building them
Loop Grid carries queries you forgot you wrote
Loop Grid is where Elementor stopped being a layout tool and became a query builder, and it is the widget that most often surprises a migration. Each grid holds a query (post type, taxonomy filters, ordering, offset, related-to-current logic), and on a mature store those queries are scattered across dozens of pages with no inventory anywhere. They have to be enumerated and reimplemented against the WooCommerce API, and the ordering rules in particular need checking, because "manual order" in a Loop Grid is stored as menu_order, and sorting the rebuilt grid by date silently reshuffles every merchandised collection.
Measure Elementor at its best before quoting
Elementor ships its performance features switched off, and quoting a migration against a store that never enabled them overstates the case for leaving. Turn them on first with the Elementor speed optimization steps for WooCommerce, remeasure, and price the rebuild against the new numbers. That costs about a week, not a quarter.
Popups and forms need an owner named before launch
Two Elementor Pro features have no equivalent on the other side, and both get remembered in launch week. Popups carry triggers and display rules (exit intent, scroll depth, after N sessions), and stores run more of them than they remember, usually including one firing on mobile since a campaign that ended. Forms carry submission actions: email routing, webhooks, CRM handoffs. Decide on each before development, not during it.
- Inventory active popups with their triggers and audit which still convert
- List every form action, especially webhooks and CRM handoffs
- Decide per item: rebuild in Next.js, keep in WordPress behind the API, or retire
- Test form submissions end to end on staging, including the receiving system
Where the case for leaving Elementor is weakest
Three situations where we tell people not to do this. Where marketing publishes landing pages weekly without a developer, a build that drops the visual editing path costs real money every week it is in service. Scope that path in, or leave the store alone. If Core Web Vitals are already green in field data from CrUX, a rebuild is not going to be quoted honestly on performance grounds and you should ask what else it is for. And if the checkout is heavily customized through Elementor's WooCommerce widgets plus a subscriptions or bookings plugin, rebuilding that path in this project is premature. The safe move is a hybrid launch that leaves native checkout alone; attempting both at once is how migrations slip a quarter.
Elementor URLs that sit outside the page list
Most URLs on an Elementor store are ordinary pages, products and categories, and they keep their paths through the rebuild. Two kinds slip past a page export. Elementor's Landing Pages feature publishes under its own e-landing-page post type at a top-level slug, so those URLs never show up in the Pages screen, and they are often the ones paid campaigns still point at. Saved templates in the elementor_library post type can be reachable at a query-string URL on some setups and occasionally get indexed. Those should answer 404 or 410 after launch rather than redirect, because nothing a shopper wants lived there. For the rest, take twelve months of URLs with impressions from Search Console, run each through the new route map on staging with a crawler, and send anything retired to its closest live equivalent.
Sequencing that keeps the site sellable
Product template, top categories, homepage, marketing pages — in that order. Product and category pages hold both the traffic and the tangled Theme Builder conditions, so they go first; marketing pages are cheapest to redo, so they go last. Checkout stays on WooCommerce through launch.
Frequently asked questions
Do we need to move off Hello Elementor too?
There is almost nothing there to move. Hello Elementor is a stub theme contributing near-zero weight; the migration is entirely about Elementor Pro's widgets, Theme Builder templates and global kit.
How are Elementor pages actually converted?
By parsing the _elementor_data JSON tree in post meta into structured content, then mapping widget types to components. Under about fifteen builder pages, hand-rebuilding is cheaper than writing the parser.
What happens to Elementor popups and forms?
Neither transfers automatically. Each is inventoried with its triggers or submission actions and gets an explicit decision: rebuilt, kept in WordPress behind the API, or retired.
Can marketing keep building landing pages in Elementor after the migration?
Only if the project scopes it in before development. The simpler route keeps campaign pages on the WordPress side, still built in Elementor, while the catalog moves to Next.js. A build that drops visual editing turns every new landing page into a developer request.
Elementor WooCommerce slow
Elementor speed optimization for WooCommerce: the Features settings to switch on, how to measure the builder layer, where WP Rocket stops and when to rebuild.
Astra to Next.js
Astra to Next.js migration for WooCommerce: extracting Starter Template and Spectra pages, rebuilding Astra Pro layouts, redirects and what sets the price.
Headless WooCommerce migration
Headless WooCommerce migration from $1,999: a Next.js storefront in front of your store, with WordPress admin, hybrid checkout, SEO URLs and plugins kept.
See how many sales your store is losing
Start with a free speed audit. You'll get your store's real numbers and an honest recommendation — even if it's "you don't need us".