**Version:** 2.0.0 **Updated:** 2026-06-30 **Freshly updated:** v2.0.0 wires in current Respira safety and precision. Pre-migration now inventories source pages with `respira_find_builder_targets`. Every write is preceded by a `respira_get_snapshot`, and the existing
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/migrate-beaver-builder-to-bricks
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
**Version:** 2.0.0 **Updated:** 2026-06-30 **Freshly updated:** v2.0.0 wires in current Respira safety and precision. Pre-migration now inventories source pages with `respira_find_builder_targets`. Every write is preceded by a `respira_get_snapshot`, and the existing
# Migrate Beaver Builder to Bricks
**Version:** 2.0.0
**Updated:** 2026-06-30
**Freshly updated:** v2.0.0 wires in current Respira safety and precision. Pre-migration now inventories source pages with `respira_find_builder_targets`. Every write is preceded by a `respira_get_snapshot`, and the existing draft-duplicate path is kept. After the first `respira_inject_builder_content`, validation issues (collapsed column widths from the row/column-to-container translation, broken parent refs, a misconverted module) are corrected surgically with `respira_find_element` + `respira_update_element` (and `respira_batch_update` for multi-element or multi-page fixes) instead of re-injecting whole pages. Snapshot restore and draft deletion are now explicit rollback paths. Reflects the current 16 supported builders.
Full-site migration from Beaver Builder to Bricks Builder. Audits every Beaver Builder page, maps modules to their Bricks equivalents, builds a migration plan for approval, and executes page-by-page conversion into Bricks' JSON format — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builder to Bricks, switching from BB to Bricks, converting Beaver Builder pages to Bricks, or replacing Beaver Builder with Bricks.
## What This Skill Does
Beaver Builder and Bricks are both visual page builders, but they differ significantly in architecture. Beaver Builder uses a module-based system with rows, columns, and modules stored in `_fl_builder_data`. Bricks uses a more modern, flexbox-first approach with sections, containers, and elements stored as a JSON array in `_bricks_page_content_2`. The migration requires translating BB's row/column grid into Bricks' container model and mapping each module to its Bricks element equivalent.
This skill reads every Beaver Builder page, extracts the module structure, translates each row/column/module to its Bricks equivalent, and writes the result to duplicate pages in Bricks format — giving you a complete parallel version of your site to review before going live.
- Beaver Themer layouts — must be rebuilt as Bricks templates
```
Then ask:
> Here's the migration plan. Would you like me to:
> 1. Migrate all pages (creates duplicates for review)
> 2. Migrate only simple pages first
> 3. Migrate specific pages you choose
> 4. Just keep this as a reference — no changes
Wait for explicit confirmation before proceeding.
### Phase 3: Page-by-Page Migration
For each approved page:
1. Extract Beaver Builder content via `respira_extract_builder_content` with `builder=beaver`
2. Map the row/column/module hierarchy to Bricks elements:
- Rows → Bricks `section` elements
- Columns → Bricks `container` elements with flex layout settings
- Text Editor → Parse into `text` and `heading` elements
- Photo → `image` element with src, alt, caption
- Button → `button` element with text, link, style
- HTML → `code` element
- Map CSS classes and inline styles to Bricks settings
- Preserve text content, image URLs, link targets
- Flag any unmappable modules with comment annotations
3. Build the Bricks JSON array structure
4. Create a duplicate via `respira_create_page_duplicate` or `respira_create_post_duplicate`
5. Before writing, take a snapshot with `respira_get_snapshot` so the duplicate's pre-write state can be restored if anything goes wrong
6. Inject Bricks content via `respira_inject_builder_content` with `builder=bricks`
7. Surgical fix pass — if the injected page has validation issues (column widths that collapsed during the row/column-to-container translation, broken parent refs, a misconverted module), do not re-inject the whole page. Locate the specific element with `respira_find_element` and correct it with `respira_update_element`. For repeated fixes across many elements or several pages, batch them with `respira_batch_update`
8. Log the migration result (success, warnings, manual review items)
### Phase 4: Post-Migration Verification
1. Summarize all migrated pages with status:
- Clean migrations (no issues)
- Migrations with warnings (flagged items needing review)
- Failed migrations (if any)
2. List all manual review items:
- Third-party modules that need manual replacement
- Content sliders or advanced layouts needing Bricks-native rebuilds
- Custom CSS that needs to be added to Bricks element styles
- Beaver Themer layouts that need separate rebuilding in Bricks
3. Provide review instructions:
- Where to find duplicates in WordPress admin
- How to preview Bricks pages
- How to delete duplicates if not wanted
## Safety Model
- Read-only analysis first — full Beaver Builder content audit before any changes
- Explicit user confirmation before creating any duplicates
- Duplicate-first only — never modifies live/published Beaver Builder content
- Never auto-publishes duplicates
- Snapshot before every write — `respira_get_snapshot` captures the duplicate's pre-write state, and `respira_restore_snapshot` rolls it back if an injection goes wrong
- Two explicit rollback paths: restore the snapshot to revert a bad write, or delete the draft duplicates entirely to undo the migration
- Preserves all original Beaver Builder content untouched
## Honest Disclaimer
This skill converts Beaver Builder page structures to Bricks format and creates duplicates for review.
It cannot:
- Guarantee pixel-perfect visual parity between builders
- Migrate Beaver Themer layouts automatically
- Convert third-party BB add-on modules to Bricks equivalents
- Replicate BB animations in Bricks interactions
- Replace a thorough manual QA pass on every page
It can:
- Map 75-85% of standard Beaver Builder modules to Bricks elements
- Translate row/column grids to Bricks' modern flexbox containers
- Preserve content, images, links, and layout structure
- Move you to a more modern builder architecture
- Save days of manual rebuild work
- Identify exactly what needs manual attention
## Tooling
**Core WordPress tools**
- `respira_get_site_context`
- `respira_get_builder_info`
- `respira_list_pages`
- `respira_list_posts`
- `respira_list_plugins`
- `respira_find_builder_targets`
- `respira_extract_builder_content`
- `respira_inject_builder_content`
- `respira_create_page_duplicate`
- `respira_create_post_duplicate`
- `respira_read_page`
- `respira_read_post`
**Safety and surgical-fix tools**
- `respira_get_snapshot`
- `respira_restore_snapshot`
- `respira_find_element`
- `respira_update_element`
- `respira_batch_update`
## Telemetry
After run completion, send fire-and-forget usage tracking to:
