Kadence to Next.js: Moving Kadence Blocks, Shop Kit and Members

The renewal notice that starts this conversation

Kadence changed hands and shape in 2026. The old kadencewp.com addresses now redirect to Liquid Web, the theme's wordpress.org author reads Nexcess, and in May several sister brands were folded in: SolidWP became Kadence Security, Iconic became Shop Kit, and Restrict Content Pro became Kadence Memberships. The theme is still free and still good. The paperwork around it is new, and a migration plan has to account for it.

• Three plans, priced per site. As of October 2026: Essentials at $99, Pro at $299 and Elite at $499 a year. Shop Kit, memberships, security and backups start at Pro.
• Legacy plans hold while they are paid. Purchases made before May 2026 keep their pricing under unified licensing, but a lapse means buying one of the new plans to get access back.
• Lapsed products keep running, unpatched. The terms say they keep working without updates, premium support or premium templates.
• Patches matter on this stack. Patchstack published an SQL injection advisory for Shop Kit 3.0.6 and earlier, and legacy-license holders asking how to update were sent to Liquid Web support.

None of that is cause for panic, and plenty of owners renew happily; the Kadence review and Kadence pricing set out who should. If the real complaint is speed, Kadence speed tuning or a look at why the site slowed after an update may buy years for less. But if you are going to move, move while the license is active, so the live site keeps getting fixes during the build. The case for and against is in Kadence vs Next.js.

Kadence Blocks content is already half structured

Most Kadence sites are built in the block editor with the Kadence Blocks plugin, so the pages are not locked in a builder's private format. Each block is saved in the post as an HTML comment naming it (kadence/rowlayout, kadence/column, kadence/advancedheading, kadence/infobox, kadence/advancedbtn) followed by a JSON object of attributes: a uniqueID, padding per device, colors, column widths, icon choices. Then comes the rendered HTML. A script can read all of it without WordPress running.

The trap is assuming the HTML is the whole page. Kadence Blocks builds each block's CSS from those attributes when the page is served. Copy the HTML alone and you get the words without the layout. So the migration reads the attributes too, and uses them to pick the right component and variant: a three-column row becomes a three-column section, and an info box with an icon becomes a card with an icon.

Nine palette slots, two headers and one breakpoint

Kadence's global palette is a gift to whoever migrates the site. The theme defines nine colors in the Customizer and prints them as CSS variables, --global-palette1 through --global-palette9, and Kadence Blocks refers to those slots rather than to raw hex values. Read the nine values once and every block that said palette3 tells you what it meant. They become the design tokens of the new site, with the same names if your team is used to them.

Headers take more thought. Kadence builds two separate headers, Desktop and Tablet/Mobile, and the theme's CSS switches between them at 1024px with no Customizer setting to move the line. On phones a trigger opens an off-canvas drawer, which some owners have found opening with no menu items in it; see Kadence header and mobile issues. In Next.js the two headers become one responsive component, with the breakpoint chosen by the design. Fonts loaded locally through the Customizer's Performance settings move to next/font, which self-hosts them; if yours have been misbehaving, Kadence fonts not loading explains why.

Hooked Elements and other things that live outside your posts

Kadence Theme Kit Pro adds Hooked Elements, and on an older Kadence site they can be doing a surprising share of the work. A Content Section might insert a call to action after every blog post. A Fixed Section might pin a promo bar to the top of the screen. A Template element might replace the whole single-post layout, and an HTML element might carry the analytics tag, the chat widget and a script nobody remembers adding. Display conditions decide where each one appears.

• Content Sections become blocks in the page layout, or reusable sections an editor can switch on per page in Athena.
• Fixed Sections become a banner component. Seasonal ones can go to Demeter, the agent that drafts seasonal offers.
• Template elements become the Next.js layouts for posts, archives and products.
• HTML and code elements are reviewed line by line. Tags still in use move into the layout; dead ones are dropped.
• Conditional Headers become header variants chosen by page type in code.

Our inventory records every element with its hook, its conditions and what it actually outputs on the live pages. Conditions are easy to misread from the admin screen, and what renders is what visitors and Google have been seeing.

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

Where Shop Kit products and Kadence members end up

This is the part of a Kadence move that needs the most planning, because it carries money and logins. WooCommerce holds the catalog and the orders. Shop Kit, the former Iconic plugins, layers galleries, swatches, checkout and more on top. Kadence Memberships, the former Restrict Content Pro, holds membership levels, member records and the rules about who sees what.

Two plain notes. Members are asked to set a new password at launch, the usual practice when a site changes login systems, with one email written in your voice. And if your memberships bill through Stripe, the customers and subscriptions live in your Stripe account rather than in WordPress, so continuity is a mapping job, not a request for everyone to sign up again. Other gateways get a plan of their own. The store side is in WooCommerce to Next.js, the member side in membership sites on Athena, and the current setup in Kadence and WooCommerce.

A Kadence migration in eight steps

1. 1

   Copy everything, freeze nothing

   Database, uploads and a note of every active Kadence product and its license status. The live site keeps selling and serving members throughout the build.

2. 2

   Inventory blocks, elements and settings

   Count every kadence/ block type in use, list every Hooked Element with its conditions, and record the palette, both header layouts and the performance toggles.

3. 3

   Crawl URLs and pull search and sales data

   Every public URL is matched with Search Console clicks and, on stores, product sales, so effort goes where the revenue is.

4. 4

   Build the design system from the palette

   The nine palette slots, the type scale and the header become tokens and components, approved before content arrives.

5. 5

   Parse the content

   Kadence Blocks attributes and text are mapped into Athena fields, and link counts are compared post by post.

6. 6

   Move the store and the members

   Products, variants and images import into the new store; membership levels, members and restricted sections are rebuilt and tested with real logins.

7. 7

   Redirect and compare

   Every changed URL gets a permanent redirect, and each page is compared with its Kadence version on a staging address, checkout and member login included.

8. 8

   Switch and watch

   DNS changes, members get their password email, and Search Console, orders and logins are watched closely through the first weeks.

Store and member URLs you cannot afford to break

Kadence does not invent URLs; WordPress and WooCommerce do. That means a careful plan can keep nearly all of them, because Next.js routes can reproduce any permalink pattern. The addresses that need special care on a Kadence site are the ones tied to money and accounts.

• Shop, product and product-category paths are kept or mapped one to one, because product URLs carry rankings and ad campaigns.
• Cart, checkout and my-account pages redirect to the new store's equivalents, so old bookmarks and emailed links still land somewhere useful.
• Login, registration and account pages from Kadence Memberships redirect to the new member area, including links inside old welcome emails.
• Restricted posts keep their addresses, so members' bookmarks work and public teasers keep any rankings they earned.
• Product image URLs from WooThumbs galleries are kept or mapped, since stores often get real traffic from image search.

The redirect method is in WordPress to Next.js redirects, the naming rules in URL structure, and image handling in WordPress images to Next.js. Blogs on Kadence sites follow the blog migration playbook. Titles, descriptions and schema move field by field; keeping SEO through a migration has the checklist.

After Kadence: fewer vendors than the bundle promised

The calendar depends less on Kadence than on what was built with it: how many Hooked Elements carry logic, how large the catalog is, how many Shop Kit modules are in real use, and how many members need moving. A brochure site built on Kadence Blocks is a comparatively quick move; a store with memberships and a multi-step checkout is a proper project. What a migration costs and how long it takes explain the drivers, and we quote a fixed price after a free audit.

The Pro plan's pitch is one vendor for theme, blocks, shop, security and backups. After the move there is no vendor list for those jobs at all. Your team edits products, posts and member content in Athena CMS with plain fields, a real preview and every version kept. Aegis takes over the daily intrusion checks; Argus watches for broken links, failing forms and expiring certificates; Echo looks after reviews; Atlas flags thin and orphan pages. Most agents draft and wait for approval. New page types are developer work, tested before deploy. The handover is in switching from WordPress, the full process under WordPress to Next.js, and the work itself is our Next.js rebuild service. Stuck with a broken Kadence site in the meantime? Our Kadence repair team can steady it first.