Migrating from Beaver Builder to native Gutenberg & ACF blocks

Beaver Builder is lighter than Elementor or Divi, but it is still a page builder — layouts live in serialised post meta (_fl_builder_data), not in native Gutenberg blocks. Agencies that standardise on ACF blocks for client rebuilds need a deliberate migration path, not a plugin swap.

The failure mode with Beaver is particularly cruel: unlike WPBakery's visible shortcodes, deactivating Beaver often leaves completely blank pages — not a wall of [fl_builder] tags you can search for. That makes staging spot-checks deceptive if you only open Gutenberg-built pages. This guide covers what breaks, how modules map to blocks, and the workflow we use.

What breaks if you just remove Beaver Builder

Deactivate Beaver Builder and pages built with it typically show nothing useful — the content is not in post_content as readable HTML, it is in builder data that only Beaver's renderer understands. Unlike WPBakery's visible shortcodes, the failure mode here is often a completely blank page, which makes the problem easy to miss on a staging spot-check if you only open Gutenberg-built pages.

Why teams leave Beaver Builder for ACF blocks

• arrow_rightConsistent editor: one Gutenberg experience across every page, no front-end builder overlay.
• arrow_rightTighter output: your PHP templates control markup instead of Beaver's row/column wrappers.
• arrow_rightPortfolio economics: ACF block libraries reuse across clients; per-site builder licences do not.
• arrow_rightMigration-ready structure: field-driven blocks are what automated classifiers map into — builder meta is not.
• arrow_rightPerformance: remove Beaver's CSS/JS payload from every page load.

How Beaver Builder stores content

Beaver Builder modules to ACF blocks mapping

Saved rows, templates and global headers

Beaver Builder's Saved Rows and Templates are reusable layout fragments. They render on any page that imports them, but the source of truth is in Beaver's admin — not obvious when you are looking at a single page in the WordPress editor. When you crawl, the rendered page includes them. When you audit, list which saved rows appear on more than one URL so you do not pay to review the same footer CTA twelve times.

Beaver Themer (if installed) adds header, footer and part layouts similar to Elementor Theme Builder. Audit these separately from page content — your new theme's template parts must replace them before you remove Beaver.

Step-by-step migration workflow

1. 1Export a full URL list; identify Beaver-built pages (_fl_builder_enabled meta or front-end inspect).
2. 2Register ACF blocks; export field groups as JSON.
3. 3Crawl every Beaver page on the live site — not the builder's back-end preview URL.
4. 4Classify modules into blocks; queue HTML/Shortcode modules for manual handling.
5. 5Import as drafts; verify images in Media Library and internal links.
6. 6Rebuild Themer templates (header, footer) in new theme.
7. 7Run migration QA on staging.
8. 8Deactivate Beaver Builder and Themer after sign-off.

Beaver vs Elementor: migration differences

Both store layout in post meta and require front-end crawling. Beaver's output is typically leaner — fewer wrapper divs — which can mean higher classifier confidence. Elementor has more module types and denser nesting. The workflow is identical: crawl, classify, review, import. See Elementor migration for parallel patterns.

Beaver Builder Lite vs Pro

Beaver Builder Lite (bundled with some themes) has fewer modules than Pro. Audit which modules the site actually uses before building your ACF block library — you may not need a pricing table block if no page uses one. Pro-only modules (login form, posts carousel, WooCommerce modules) need explicit mapping decisions. WooCommerce modules are dynamic — wire to live queries on the new site.

Multisite and agency reseller accounts

Agencies running Beaver on multisite or reseller licences often rebuild to escape per-site licence management. ACF block libraries shared across a portfolio replace per-client Beaver customisations. Document which Beaver templates were global across subsites — each may need the same theme template part on the new network.

Common Beaver Builder migration mistakes

• arrow_rightSpot-checking only blog posts — Beaver pages are blank, posts may look fine.
• arrow_rightMigrating Saved Row content repeatedly instead of once as a shared block.
• arrow_rightForgetting Beaver Themer headers and footers.
• arrow_rightLeaving HTML modules with tracking scripts unreviewed.
• arrow_rightDeactivating Beaver before Themer replacements exist.
• arrow_rightNot running broken images check after sideload.

Pricing and scoping Beaver migrations

Beaver sites are often 20–50 pages with moderate complexity. Quote migration separately from design and theme build. Show the maths: 40 pages at 2 hours manual = 80 hours versus 40 pages at 15 minutes review = 10 hours. Beaver Themer adds template rebuild time — header, footer, and archive templates are development line items, not migration line items. See how to scope and price a rebuild.

Post-migration: editor training

Beaver clients are used to front-end drag-and-drop. Gutenberg with ACF sidebar fields feels different. Run a 30-minute staging walkthrough: insert a hero block, edit a repeater row, preview, publish. Provide a one-page block guide. The first week post-launch expect support tickets — budget two hours of handover support in the project scope.

Identifying Beaver-built pages in the database

Query wp_postmeta for _fl_builder_enabled = 1 to list Beaver pages. Cross-reference with your sitemap and analytics — some pages may have been built in Beaver then partially edited in Gutenberg. Hybrid pages need manual inspection: the crawl captures rendered output regardless of which editor last saved. Beaver Themer layouts do not set _fl_builder_enabled on every page they affect — audit Themer separately.

SEO preservation on Beaver migrations

Beaver sites use Yoast or Rank Math like any WordPress build. Migrate titles and descriptions with the content bundle — see preserve Yoast SEO. Beaver does not store SEO data in builder meta; it is in the same post meta keys as a standard WordPress site. If URLs change when you restructure services pages, load a redirect map before deactivating Beaver.

Performance gains after leaving Beaver

Beaver is lighter than Elementor but still ships builder CSS and JS on every page. Removing Beaver and rendering through ACF block templates typically improves LCP and reduces DOM size. Run Lighthouse on the homepage before and after on the same hosting — the screenshot is your client pitch for the rebuild. See page builder performance problems for metric framing.

Staging and launch sequence

1. 1Import all Beaver pages as drafts on staging.
2. 2Rebuild Themer templates in new theme.
3. 3Editor review and publish on staging.
4. 4Load redirects; verify SEO meta.
5. 5Run full migration QA.
6. 6Deactivate Beaver on staging; confirm no blank pages.
7. 7Cutover production; monitor post-launch.

Beaver migrations benefit from the same staging workflow as every builder exit. Never deactivate Beaver on production until staging proves every page renders from ACF blocks alone. The blank-page failure mode is silent — your QA checklist must include every URL from the sitemap, not just the pages the client remembers.

Module edge cases

• arrow_rightContact form module — rebuild in Gravity Forms; map fields to match old submissions.
• arrow_rightPosts module / Posts carousel — dynamic WP_Query block on new theme.
• arrow_rightMap module — Google Maps embed or ACF map field with API key on new site.
• arrow_rightMenu module — rebuild as WordPress nav menu, not ACF block content.
• arrow_rightSidebar module — widget area or block template part in new theme.
• arrow_rightSubscribe form — Mailchimp/ConvertKit embed or form plugin integration.

Slideshow and Photo modules are where broken images cluster — every slide needs sideloading into the Media Library, not a hotlinked URL from the old uploads folder. Verify repeater row image fields in the editor after import, not just the front-end preview.

Preserve Yoast SEO metadata during Beaver migrations — builder removal does not affect post meta, but a fresh install without explicit mapping does. Include SEO fields in your bundle alongside block content.

Load a redirect map before deactivating Beaver if any marketing URLs change during the rebuild. Beaver pages often have clean slugs — preserve them unless the information architecture deliberately shifts during the project.

AIRA handles the crawl-and-classify stages against your ACF export — the same pipeline used for Elementor and WPBakery migrations. Pair with the WordPress migration checklist and post-launch monitoring plan.

What to read next on this rebuild

Beaver Builder stores layout in postmeta like Elementor — the rendered-page crawl approach in this guide still applies. For WooCommerce sites on Beaver, product templates are separate from page migration; see WooCommerce ACF rebuild. Do not skip media library migration — Beaver image modules often embed attachment IDs that break after import.