Neve to Next.js: Moving the Customizer, Neve Pro and Your Starter Site

Three layers in a Neve install, and the one that fights back

A Neve site is not one thing. It is a free classic theme that keeps its look in the WordPress Customizer, a paid Neve Pro plugin that adds modules on top, and page content made with whatever editor the starter site was built for. Each layer leaves a different kind of residue in the database, and each one migrates at a different speed.

Neve itself is the easy part. It never asked you to build pages inside a proprietary theme builder, so there is no theme shortcode soup to translate. That is a real point in its favor, and part of why the Neve vs Next.js comparison calls it one of the lighter exits.

Reading theme_mods_neve before you switch anything off

Almost every visual choice you made in Neve, from container widths to blog layout to the header rows, sits in a single serialized option called theme_mods_neve. When the theme is deactivated, that row stays in the database but nothing reads it, and the design it described vanishes from the front end. Capture it while it still renders.

• Export the row and screenshot the result. We save the raw option for reference and screenshot the header, footer, blog index and a single post at phone, tablet and desktop widths, because Neve's header builder keeps a separate mobile layout.
• Write down the palette and type scale. Global colors, font families and sizes become design tokens in the new build. If you used the free Local Fonts Hosting setting, the font files are already on your server and easy to carry over.
• Note conditional header behavior. Transparent headers on some pages, sticky rows, a cart icon added by Pro components: each becomes a rule in code, so list where it appears.
• Check the row is healthy first. In a WordPress.org support thread, Themeisle staff traced an expected_array save error to a malformed theme_mods_neve option. If your Customizer has been refusing to save, treat the screenshots as the source of truth, not the database. The Neve repair hub covers that fault.

If the header has been misbehaving on phones, read our notes on the Neve mobile menu and header builder problems before deciding which version of it to copy.

Neve Pro, module by module

Neve Pro is a plugin with switchable modules, and the plan you bought decides which ones you have. As of October 2026, Personal is $69 for the first year, Business $149 and Agency $259, and the pricing page says renewals are at full price ($139, $299 and $519). List the modules that are switched on, then decide what each one becomes.

Which builder did your starter site bring with it?

The Business plan advertises 110+ starter sites, imported with the Starter Sites & Templates by Neve plugin. Themeisle's docs say each design is published for specific builders, some for both Gutenberg and Elementor, some for only one. That choice, made in a hurry on day one, sets most of your migration effort today.

Look at the plugin list: Otter Blocks active means Gutenberg, Elementor active means the other road, and both active usually means someone tried two starter sites. Demo leftovers deserve a sweep too. Sample team bios, placeholder testimonials and stock images from the import are common, and if the starter site import half failed, orphaned demo pages may still be published.

The Neve exit, in eight moves

1. 1

   Crawl and count

   Crawl the live site and export every URL, title, description and status code. Add Search Console's top pages so nothing with traffic is missed.

2. 2

   Freeze the design record

   Save theme_mods_neve, screenshot every template at three widths and list each Custom Layout with its conditions and hook.

3. 3

   Inventory Neve Pro and plugins

   Write one line per active module and plugin: keep, rebuild, replace or drop. This list drives the quote more than page count does.

4. 4

   Identify the builder and parse content

   Pull posts, pages and products through the REST API or a database copy. Map Otter or Elementor sections into structured content types.

5. 5

   Rebuild the layout in code

   Header, footer, post template and archive become Next.js components, with fonts through next/font and images through next/image.

6. 6

   Carry SEO data across

   Import titles, descriptions, canonical tags and schema from the SEO plugin so every page keeps its search snippet.

7. 7

   Write the redirect map

   Match each old URL to its new one, redirect anything that changes with a single 301 hop, and test the full list against staging.

8. 8

   Launch, then watch

   Switch DNS, submit the new sitemap, and check crawl errors and rankings daily for the first weeks. Keep Neve Pro active on the old copy until you are sure.

The third option

Athena CMS, with AI agents on staff.

Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.

• PPicassoImages
• AApolloSite analysis
• AAresCompetitor watch
• PPrometheusContent holes
• AAtlasPage depth and structure
• DDelphiAI search visibility

ZDAOAand 12 more agents. Two come with Athena; the rest are monthly add-ons.

Meet the agentsTake the Athena tour

PPicassoWeekly · ImagesAApolloWeekly · Site analysis

Permalinks Neve never touched

Good news for your rankings: Neve does not invent URL patterns. Your post and page addresses come from WordPress's Permalinks setting, so the new site can match them one for one, and most Neve migrations need far fewer redirects than a builder-heavy theme. Our URL structure guide covers how routes mirror permalinks.

• Archives: category, tag, author and date pages, plus their /page/2/ pagination. Keep the ones with traffic, redirect or retire the rest deliberately.
• WooCommerce paths: /product/ and /product-category/ bases, if the store uses them, plus cart, checkout and account pages.
• Attachment pages: WordPress can publish a page per image. Send any indexed ones to their parent post.
• AMP URLs: the vendor advertises AMP compatibility. If an AMP plugin ever ran, check Search Console for /amp/ addresses and redirect them to the canonical page.
• Feeds: /feed/ has subscribers you cannot see. Publish an RSS feed at the same address.

The mechanics of 301s, chains and testing live in our redirects guide, and the whole checklist for rankings is in migrating without losing SEO.

Images, fonts and a lighter page by default

Neve sells itself on weight: the vendor says 28KB and a one-second load on a default install. A finished site is rarely the default install, which is why our Neve speed page spends its time on the plugins around the theme. In the new build, the theme's weight stops being the question.

Images move as originals, and next/image produces the sizes each layout needs, so the half-dozen resized copies WordPress made of every upload stay behind. Demo images from the starter site are a good moment for a cull. Fonts that Neve hosted locally become next/font files, which removes the font loading problems some owners fight. The full method is in moving WordPress images to Next.js.

Neve kept your design in one database row. The new site keeps it in code you can read.

What sets the timeline on a Neve migration

Page count matters less than people expect. A forty-page Gutenberg site with three Custom Layouts moves faster than a twelve-page Elementor site with a WooCommerce Booster store and members-only content. These are the drivers we price against after a free site audit:

• Which builder the starter site used, and how far the pages drifted from it.
• How many Custom Layouts exist, and how tangled their conditions are.
• Whether WooCommerce is involved, and which Booster features customers rely on (the WooCommerce migration guide covers the store side).
• Content restriction, LMS courses or member data that must keep working on launch day.
• Blog volume and how much clean-up the posts need, covered in moving a WordPress blog.

For ranges and phases, see what a migration costs and how long it takes. We quote a fixed price, and financing for WordPress projects is available.

Editing after Neve, without a Customizer or a renewal

Neve owners tend to like the Customizer's live preview, and they should not lose it. Athena CMS, included with every site we build, gives editors plain fields, a real preview and every version kept. Changing a headline does not risk the header, because the header is code and the headline is content.

The chores Neve Pro nagged you about go to agents with one job each. Argus watches for broken links, failing forms and slow pages. Iris drafts search titles and social cards. Ariadne suggests internal links. Picasso makes sure no image goes up undescribed or oversized. Most draft for your approval rather than publishing on their own.

When it is time, our WordPress to Next.js development team handles the whole move, and the migration hub collects every guide in this series.