JHMG Converter For Beaver Builder to Divi 5

Convert pages built with Beaver Builder into native Divi 5 block layouts — rows become sections, column groups become rows, columns become columns, and every Beaver Builder Lite module maps to its Divi 5 counterpart with its content, links, images, colours, typography, spacing and backgrounds carried across.

If Beaver Builder is installed on this site, pick the page from a list — no export needed. Converting from another site? Export it from Tools → Export there (Beaver Builder stores its layouts inside the export) and upload the file here.

Before you convert, click Check this page to see a conversion report: the structure the conversion will produce, laid out as an outline, and everything that could not be carried over, by name. Nothing is written until you click Convert. Converting always creates a new Divi draft — your Beaver Builder page is never modified — and every run can be undone with one click.

What converts

Layout: rows (full and fixed width, backgrounds, overlays, gradients, padding, minimum height), column groups, columns (widths, backgrounds, borders), nested column groups, and the Box container.

Beaver Builder Lite modules — every one of them, from the plugin’s own source: Heading, Text Editor, Photo, Button, Button Group, HTML, Video, Audio, Sidebar, Icon, Callout, Call to Action, Number Counter, Star Rating, Menu, Box. Widget, Reusable Block and ACF Block modules leave a labelled placeholder holding their text.

Beaver Builder Pro modules — Separator, Accordion, Tabs, Testimonials, Pricing Table, Contact Form, Subscribe Form, Map, Gallery, Slideshow, Content Slider, Posts (grid, slider, carousel), Countdown, Icon Group, Social Buttons, Login Form, Search, List, Progress Bar, WooCommerce (product grids become Divi’s Shop module, every other layout keeps its WooCommerce shortcode), BigCommerce Products, the Beaver Themer Loop (Divi 5’s own loop, with field connections turned into dynamic content) and Popup (kept as a hidden group for a popup plugin) convert with their content. These mappings come from Beaver Builder’s documentation and exported layouts rather than its source, so the report marks them as approximate and lists them for you to check. Every module in Beaver Builder’s own module reference has a handler; WordPress Patterns and Widgets are rendered into static HTML, and only ACF Blocks and North Commerce leave a labelled placeholder.

Field connections — Beaver Themer’s [wpbb post:title], [wpbb site:year], [wpbb post:featured_image] and similar connections become Divi dynamic content wherever Divi has the matching option; the rest are listed in the report.

PowerPack for Beaver Builder — Advanced Heading, Icon List and Fluent Forms modules convert too (the form is embedded through its Fluent Forms shortcode with PowerPack’s styling carried as CSS). Sites running Ultimate Addons or PowerPack save around a hundred add-on settings on every row and column; the converter recognises those families, ignores the ones left at their defaults and reports the ones you switched on, so the report only lists what the page really loses.

Design settings: margins and padding (with units and tablet/phone values), background colours, photos, gradients and overlays, borders, radius and shadows, typography (family, weight, size, line height, letter spacing, alignment, transform, decoration, shadow), text colours, minimum heights, widths, alignment, custom IDs and classes, and responsive visibility. Font Awesome icons become the identical Divi icon.

Reported, not silently lost: animations, logged-in/logged-out visibility, row shape layers, video and slideshow backgrounds, lightbox links, hover colours, click actions, third-party connections, global colours that could not be resolved, and any setting the converter did not map.

Free vs Pro

Free:

• Convert a page straight from your Beaver Builder site — pick it from a list
• Check any page before converting: see the structure and exactly what will not carry over
• Upload a WordPress export or a Beaver Builder template file to convert a page from another site
• Every Beaver Builder Lite module and the popular Pro modules
• A detailed per-page report, one-click undo for every run
• Unlimited conversions — one page at a time

Pro add-on:

• Convert as many pages as you like in one run — from this site or from one export file
• Send Beaver Themer headers and footers straight into the Divi Theme Builder
• Priority support and regular updates

Step by step

1. Install and activate this plugin on your Divi 5 site.
2. Go to Tools → Beaver Builder → Divi 5.
3. Pick the page you want to convert and click Check this page.
4. Read the report, then click Convert to Divi 5 — a new Divi draft is created.
5. Review it in the Divi Builder, then publish when ready.

External services

This plugin can optionally send a short report to divi5lab.com so that the most
commonly missing Beaver Builder modules get built first.

• Service: divi5lab.com coverage endpoint — https://divi5lab.com/api/plugin/coverage
• What is sent: two fields — widget_types (the names of Beaver Builder module
  types your conversions could not convert, for example acf-block) and product (a
  fixed identifier for this plugin). Nothing else — no site address, no page content,
  no personal data, no licence or account information.
• When: at most once a week, and only after you explicitly turn sharing on from
  the Conversion coverage panel. Sharing is opt-in, off by default, and nothing is sent until you enable it.
• Turning it off: use “Stop sharing” on the same panel at any time.
• Terms: https://divi5lab.com/license — Privacy policy: https://divi5lab.com/license#privacy

Google Maps (converted Map modules only). Beaver Builder’s Map module stores an
address, not the coordinates and API key Divi’s Map module needs, so the converter
turns it into a Divi Code module holding a Google Maps embed of the same address
(an iframe loaded from https://maps.google.com). Nothing is sent during the
conversion itself. When a visitor views the converted page, their browser loads
the map from Google, which receives the address shown and the usual request data
(the visitor’s IP address, browser details and any Google cookies). Pages without
a Map module make no request to Google. You can delete or replace the embed in the
Divi Builder at any time.

• Service: Google Maps embed — https://maps.google.com
• Terms: https://policies.google.com/terms and https://www.google.com/help/terms_maps/
• Privacy policy: https://policies.google.com/privacy