Move from Astra to a Next.js storefront
Astra runs 11.6% of WooCommerce stores, and the theme is the easy part to replace. The work and the quote sit in what built the pages, and in the Astra Pro layouts that no export includes.

An Astra to Next.js migration is an extraction project more than a theme swap. Astra renders about 37KB of its own CSS and JavaScript, and everything a shopper actually looks at was built by something else, which is what separates this from a WoodMart or Avada migration. Those themes are the storefront: layouts, product features and page content live inside the theme, so removing the theme removes most of the work. On an Astra store the content sits in Elementor, Beaver Builder, Spectra or the block editor, frequently put there by a Starter Template, and Astra Pro adds placement rules that live in no page at all. Inventory that first. A migration priced on page count, without it, is priced on the number that matters least.
Price the builder layer, not the 37KB theme
Astra sits on roughly 480,000 WooCommerce sites by CartFlows' count, and its own assets are rarely what a migration buys its way out of: if Astra is 37KB of a 2.4MB page, the project exists to replace the other 2.3MB. Whether that layer can be tuned in place instead is a separate question, and the Astra speed optimization order of checks should answer it before anyone writes a quote.
Find out what actually built your pages
This is the first hour of every Astra project, and it decides the price. Astra ships no builder of its own, so page content lives in one of four places, and stores that have been running for three years often contain all four at once. Each Starter Template import comes in one builder's version (Spectra, Elementor or Beaver Builder), never two, so the import tells you which builder the store inherited. Pages added later by hand sit in whatever format the editor of the day preferred. Each format needs a different extraction path, and the mixed case is the expensive one. Past three formats on one site, automated extraction stops being worth writing, because hand-rebuilding the twenty pages that matter is cheaper than a parser for the long tail nobody visits.
- Elementor: content is JSON in post meta, extractable but nested
- Beaver Builder: serialized module data, needs its own parser
- Spectra and core blocks: block markup, the cheapest case by a wide margin
- Classic editor pages: plain HTML, trivial
- Astra Pro custom layouts: PHP-hooked fragments that no export includes
Spectra pages keep their styling outside the markup
Spectra is the cheapest builder to leave and still hides one trap. Its blocks save into post_content alongside core blocks, under the uagb namespace (uagb/container, uagb/advanced-heading, uagb/info-box), and every design setting is held as JSON attributes inside the block comment. Spectra generates the CSS from those attributes at render time, inline in the page head or, with its File Generation option on, as separate files. An extractor that reads the rendered HTML therefore gets the structure and loses the spacing, colors and responsive breakpoints. Read the attributes instead, through WordPress's own parse_blocks() or the REST API with the edit context, and map each uagb block type to a component once. Synced patterns need a separate pass. A page that uses one stores only a wp:block reference with a numeric ID pointing at a wp_block post, so an extractor that skips references ships a page with a hole where the trust row or size chart used to be.
Astra Pro's hooks are the part with no direct equivalent
The astra-addon plugin lets you inject content at WordPress hook points: a shipping notice above the add-to-cart button, a trust row before the footer, a banner on category archives only. These fragments are invisible to page exports because they are not part of any page. They are rules. Nobody remembers all of them, and the store owner is usually surprised by two or three during the audit. We enumerate them from the Astra Pro custom layouts screen, decide which ones still earn their place, and rebuild the survivors as components with explicit placement rather than implicit hook order. Roughly a third get dropped, because nobody could say what they were for.
What the WooCommerce module was quietly doing
Astra Pro's WooCommerce module supplies quick view, off-canvas cart, sticky add-to-cart, infinite scroll on archives, and a set of gallery behaviors. Each is a small conversion feature the store has leaned on for years without anyone writing it down, and each needs a decision in the rebuild. Sticky add-to-cart and off-canvas cart usually come across: cheap, and they earn their place on mobile. Infinite scroll usually should not. It breaks the back button, it makes a category page impossible to link into, and past about 300 products it becomes a scroll trap that costs you crawlability for nothing.
- Keep: sticky add-to-cart, off-canvas cart, gallery zoom
- Rebuild deliberately: quick view, only if analytics show it is used
- Drop: infinite scroll on archives past ~300 products
Redirects when a Starter Template built your URLs
Starter Template imports create pages the store never asked for (sample services, an about template, a blog stub), and they have been indexed for years. Pull twelve months of URLs from Search Console rather than the sitemap. The sitemap tells you what exists; Search Console tells you what earned something.
- Export twelve months of Search Console URLs, not the sitemap
- Classify each: keep, improve, 301 to a relevant page, or noindex
- Point removed template pages at the nearest real page, never the homepage
- Verify redirects on staging with a crawler before launch, not after
Three Astra stores that should not migrate
A migration off Astra stops paying for itself in three cases we see often enough to name. A store under roughly 200 products with pages built in the block editor is already close to the ceiling a headless rebuild would reach, and the gap is not worth the project. A store whose slowness traces to database queries, an unindexed wp_postmeta table or an oversubscribed shared host will carry that problem into Next.js unchanged, because the REST and GraphQL endpoints hit the same database. And a team of one person who edits pages weekly in Elementor will lose more in workflow than they gain in milliseconds, unless the rebuild keeps WordPress as the editing surface. Fix hosting and queries first; if the store is still slow, the frontend is genuinely the bottleneck and the case is real.
Why page count barely moves an Astra quote
Four numbers from the first-week inventory set the price, and the page total is not one of them. The biggest is the count of content formats: one builder plus classic pages is a normal project, while Elementor, Beaver Builder and Spectra on the same site means three extraction paths or a hand rebuild of the pages that earn traffic. Second is the number of Astra Pro custom layouts that survive the audit, because each one becomes a component with an explicit placement rule. Third, the WooCommerce module features the store keeps. Fourth, the indexed URLs that need a one-to-one redirect rather than a pattern rule. The four-week plan below is a Growth Customization project, from $4,500. A store whose pages are mostly block-editor content on stock WooCommerce templates can come in as a Launch Setup from $1,999, and three formats with dozens of hooked layouts get quoted after the audit as a Premium Migration. Treat any fixed quote issued before that inventory as a guess.
How the first four weeks run
Week one is measurement and inventory: three-layer performance breakdown, builder format audit, Astra Pro hook enumeration, Search Console URL export. Week two rebuilds the product template and the top three categories. That is where money and traffic concentrate, and if the schedule slips it slips here, not at the end. Week three connects product data, implements the redirect map and wires the checkout handoff so WooCommerce keeps owning payment, tax and orders. Week four is staging validation and a rehearsed rollback. Launch early in the week, while the people who can fix things are at their desks; a Friday launch buys you a weekend of nobody watching. Then hold still for fourteen days and read Search Console. Crawl rate, indexation and rankings all move on a lag, and shipping through that window is how teams lose the ability to attribute what happened.
Frequently asked questions
How much does it cost to migrate an Astra store to Next.js?
The four-week build described here is a Growth Customization project, from $4,500. A store built mostly in the block editor on stock WooCommerce templates can fit a Launch Setup from $1,999, and a site mixing three builders with many Astra Pro layouts is quoted after the audit. Page count matters less than the number of content formats.
How are Spectra blocks migrated to Next.js?
From the block attributes stored in post_content, not from the rendered HTML, because Spectra generates its CSS from those attributes separately. Each uagb block type is mapped to a component once, and synced patterns are resolved from their wp_block reference.
What happens to pages built with Starter Templates?
They are extracted from whichever builder the template installed and rebuilt as components. Template pages nobody uses get redirected rather than recreated, but only after checking twelve months of Search Console impressions.
Will Astra Pro custom layouts survive a migration?
Not automatically. The hook-injected fragments are enumerated by hand and rebuilt as components. In our experience about a third get dropped because no one can say what they were for.
Can the team keep editing pages after the migration?
Yes, if the build keeps WordPress as the editing surface and pulls content through the API. For a one-person team editing weekly, this is not optional, since without it the workflow cost outweighs the speed gain.
Astra speed
Astra speed optimization: the theme ships under 50KB, so tuning it rarely fixes a slow store. Check the builder, plugins and images in this order, then stop.
Elementor to Next.js
Migrate an Elementor WooCommerce store to Next.js: reading _elementor_data, rebuilding Theme Builder conditions, and what happens to popups and forms.
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.
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".