From Respira WordPress Skills Library
Audits and converts all Beaver Builder pages to native WordPress block editor (Gutenberg) markup via duplicates so the live site stays untouched. Maps rows, columns, and modules to core block equivalents and generates a migration plan for approval.
How this skill is triggered — by the user, by Claude, or both
Slash command
/respira-wordpress-skills:migrate-beaver-builder-to-gutenbergThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full-site migration from Beaver Builder to the WordPress block editor (Gutenberg). Audits every Beaver Builder page, maps modules to their Gutenberg block equivalents, builds a migration plan for approval, and executes page-by-page conversion into native block markup — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builde...
Full-site migration from Beaver Builder to the WordPress block editor (Gutenberg). Audits every Beaver Builder page, maps modules to their Gutenberg block equivalents, builds a migration plan for approval, and executes page-by-page conversion into native block markup — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builder to Gutenberg, switching from Beaver Builder to blocks, converting Beaver Builder pages to the block editor, or moving away from Beaver Builder to native WordPress.
Beaver Builder uses a module-based architecture with rows, columns, and modules stored in _fl_builder_data and _fl_builder_data_settings. Gutenberg uses a flat block structure in post_content with HTML comments as block delimiters. The architectural gap is moderate — Beaver Builder's row/column grid must be translated to Gutenberg's Group, Columns, and Column blocks, while individual modules map to core blocks.
This skill reads every Beaver Builder page, extracts the module structure, translates each row/column/module to its Gutenberg block equivalent, and writes the result to duplicate pages in native block markup — giving you a complete parallel version of your site to review before going live.
Handles:
Source: Beaver Builder
_fl_builder_data and _fl_builder_data_settingswordpress_extract_builder_content with builder=beaver or builder=beaver-builderrich-text, photo, button, heading, html, video, icon, separator, callout, cta, numbers, content-slider, etc.Target: Gutenberg (Block Editor)
post_content as HTML with block comment delimiters<!-- wp:paragraph --><p>Text</p><!-- /wp:paragraph -->wordpress_update_page / wordpress_update_post)paragraph, heading, image, buttons, columns, group, html, video, separator, embed, etc.wordpress_get_site_context. If unavailable, stop and show setup guidance.wordpress_get_builder_info or wordpress_list_plugins.wordpress_list_pages and wordpress_list_posts — identify all contentwordpress_find_builder_targets with builder=beaver — find BB-managed pageswordpress_extract_builder_content with builder=beaverPresent a structured migration plan:
## Beaver Builder → Gutenberg Migration Plan
### Site Overview
- Total Beaver Builder pages: X
- Simple pages (direct mapping): X
- Moderate pages (some manual review needed): X
- Complex pages (significant manual work): X
### Module Mapping
| BB Module | Gutenberg Block | Notes |
|---|---|---|
| Text Editor | Paragraph / Heading | Content parsed into appropriate blocks |
| Photo | Image | Direct mapping |
| Button | Buttons > Button | Wrapped in Buttons container |
| Row (2 col) | Columns (2 col) | Width ratios preserved where possible |
| ... | ... | ... |
### Migration Order
1. [Page Title] — Simple — estimated 2 min
2. [Page Title] — Moderate — estimated 5 min
...
### Items Requiring Manual Attention
- [Page X] — PowerPack module (no core block equivalent)
- [Page Y] — Content slider (basic fallback only)
- Beaver Themer layouts — must be rebuilt as block templates
Then ask:
Here's the migration plan. Would you like me to:
- Migrate all pages (creates duplicates for review)
- Migrate only simple pages first
- Migrate specific pages you choose
- Just keep this as a reference — no changes
Wait for explicit confirmation before proceeding.
For each approved page:
wordpress_extract_builder_content with builder=beaver<!-- wp:group --> blocks<!-- wp:columns --> with <!-- wp:column --> children<!-- wp:paragraph --> and <!-- wp:heading --> blocks<!-- wp:image --> with src, alt, caption<!-- wp:buttons --> wrapper with <!-- wp:button --> child<!-- wp:html --> block<!-- wp:paragraph --><p>[MIGRATION NOTE: ...]</p><!-- /wp:paragraph -->wordpress_create_page_duplicate or wordpress_create_post_duplicatepost_content with the Gutenberg markup via wordpress_update_page or wordpress_update_postThis skill converts Beaver Builder page structures to Gutenberg block markup and creates duplicates for review.
It cannot:
It can:
Core WordPress tools
wordpress_get_site_contextwordpress_get_builder_infowordpress_list_pageswordpress_list_postswordpress_list_pluginswordpress_find_builder_targetswordpress_extract_builder_contentwordpress_create_page_duplicatewordpress_create_post_duplicatewordpress_update_pagewordpress_update_postwordpress_read_pagewordpress_read_postAfter run completion, send fire-and-forget usage tracking to:
POST https://www.respira.press/api/skills/track-usageInclude:
skill_slug = migrate-beaver-builder-to-gutenbergNever block user flow on telemetry failure.
Built by Respira Team https://respira.press/skills/migrate-beaver-builder-to-gutenberg
npx claudepluginhub respira-press/agent-skills-wordpressAudits every Beaver Builder page, maps modules to Bricks equivalents, builds an approval migration plan, and converts pages to Bricks JSON via duplicates without touching the live site.
Generates or edits WordPress Gutenberg blocks for the Greenshift/GreenLight plugin and converts data or vanilla HTML+CSS+JS to WordPress blocks.
Converts React/HTML/Next.js codebases into pixel-perfect WordPress themes with preserved SEO, dynamic CMS features, and strict UI audits. Use for high-fidelity frontend-to-WP migrations.