Skip to content

Divi to Gutenberg or Kadence

Get your content out of Divi.

Divi makes pages easy to build and hard to leave. The layout lives in Divi’s own format, so switching the theme off does not give you clean pages. On older Divi sites, it leaves every page full of [et_pb_section] shortcodes.

We rebuild Divi sites on the WordPress block editor, either with native Gutenberg blocks or with Kadence, and clean the leftovers out of your content.

Thinking about leaving Divi?

Replies within one business day.

Gutenberg or Kadence?

  • •Native Gutenberg with a block theme. The fewest dependencies. Best when the design system is simple and you want the longest possible shelf life.
  • •Kadence (Kadence theme and Kadence Blocks). More layout controls and ready-made blocks for editors, still built on the block editor. Best when your team wants Divi-like flexibility without the lock-in.

Both store content as standard blocks. If you leave Kadence one day, your text and images are still readable.

Why teams make this move

Speed.

Heavy CSS and JavaScript on every page, whether it is needed or not.

Lock-in.

The content only makes sense while Divi is active.

Editor friction.

Small copy changes take too many clicks in the visual builder.

What moves, what gets rebuilt, what stays behind

Moves across

Comes across as it is

  • Every page and post, same URL
  • Text, headings, images, links
  • SEO plugin settings (Yoast, Rank Math)
  • Menus, categories, media library
Gets rebuilt

Built again on the new platform

  • Layouts, as blocks and patterns
  • Global headers and footers
  • Sliders, tabs, toggles, contact forms
  • Reusable Divi layouts as synced patterns
Stays behind

Left on the old platform

  • Divi theme and Divi Builder
  • Divi shortcodes in the database
  • Divi Theme Builder templates
  • Unused Divi CSS and scripts

How we run it

  1. 01Crawl and list every page,with the Divi modules each one uses. That list sets the scope.
  2. 02Build a small block library.One pattern per repeating section, so pages are consistent and editors cannot break the layout.
  3. 03Rebuild templates first:header, footer, blog, single post, archives.
  4. 04Convert pages,high-traffic ones first, and compare each one side by side with the Divi version.
  5. 05Clean the databaseof leftover shortcodes, including old posts that still use Divi modules.
  6. 06Measure speed before and afteron the same templates.
  7. 07Launch the new theme,check every URL, and watch Search Console.

Where this usually goes wrong

Shortcodes left in old posts.

The homepage looks fine and a 2019 blog post shows raw code.

Divi-only features forgotten.

Popups, contact form notifications, A/B tests set up in Divi.

Automatic converters.

They carry the markup across, not the design. We use them only as a starting point, never as the finished result.

What we won’t promise

A one-click conversion. There isn’t one that produces a site you would want to keep. The rebuild is page by page, with a block library to speed it up.

Frequently asked questions

Will our URLs change?+

No. Pages and posts keep their URLs. Only the theme and the page markup change.

Can we keep the current design?+

Yes. We can match it closely, or use the move to fix what is not working.

How long does it take?+

It depends on the number of unique layouts, not the number of pages. A site with 200 posts and 6 page layouts is faster than one with 30 pages and 30 layouts.

Will editing be harder than Divi?+

Usually easier for day-to-day changes. We give editors patterns for every section, and a short recorded walkthrough.

Ready to leave Divi?

Send your site URL. We will look at your layouts and tell you what the rebuild involves before you commit.

Replies within one business day.