**Version:** 2.0.0 **Updated:** 2026-06-30 **Freshly updated:** v2.0.0 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope source pages up front, a `respira_get_snapshot` checkpoint before any write, and surgical fixes
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-brizy-to-gutenberg
👁️ 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 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope source pages up front, a `respira_get_snapshot` checkpoint before any write, and surgical fixes
# Migrate Brizy to Gutenberg
**Version:** 2.0.0
**Updated:** 2026-06-30
**Freshly updated:** v2.0.0 weaves in the current Respira safety and precision flow — `respira_find_builder_targets` to inventory and scope source pages up front, a `respira_get_snapshot` checkpoint before any write, and surgical fixes via `respira_find_element` + `respira_update_element` (and `respira_batch_update` for multi-element or multi-page corrections) instead of rewriting whole pages. Rollback is now explicit (restore the snapshot, delete the draft duplicates). Reflects the current 16 supported builders.
Full-site migration from Brizy Builder to the WordPress block editor (Gutenberg). Audits every Brizy-built page, maps components 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 Brizy to Gutenberg, switching from Brizy to blocks, converting Brizy pages to the block editor, or moving away from Brizy to native WordPress.
## What This Skill Does
Brizy uses a proprietary content format with its own component system, storing data in `brizy_post_uid` and related custom meta fields. Gutenberg uses a flat block structure in `post_content` with HTML comment delimiters. The migration requires extracting Brizy's custom format, identifying each component type, and translating it to equivalent core Gutenberg blocks.
This skill reads every Brizy page, extracts the builder content, translates each component 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:**
- Section → Group block mapping
- Video → `<!-- wp:video -->` or `<!-- wp:embed -->` block
- Spacer → `<!-- wp:spacer -->` block
- Custom HTML → `<!-- wp:html -->` block
- Preserve text content, image URLs, link targets
- Flag unmappable components with `<!-- wp:paragraph --><p>[MIGRATION NOTE: ...]</p><!-- /wp:paragraph -->`
3. Assemble the complete Gutenberg block markup
4. Take a `respira_get_snapshot` checkpoint of the target before any write, so the page can be restored exactly if the conversion needs unwinding
5. Create a duplicate via `respira_create_page_duplicate` or `respira_create_post_duplicate`
6. Write the Gutenberg markup into the duplicate's `post_content` via `respira_update_page` or `respira_update_post`
7. Surgical fixes (not a rewrite): when a single block lands wrong — a heading, a button label, a spacing value — locate it with `respira_find_element` and correct it in place with `respira_update_element`. For repeated corrections across many blocks or several migrated pages, batch them with `respira_batch_update` rather than regenerating and re-writing whole pages.
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:
- Popups that need a separate popup plugin solution
- Forms that need a WordPress form plugin (Contact Form 7, WPForms, etc.)
- Dynamic content that needs reconnecting
- Brizy Pro features that have no Gutenberg equivalent
3. Provide review instructions:
- Where to find duplicates in WordPress admin
- How to preview pages in the block editor
- How to delete duplicates if not wanted
## Safety Model
- Read-only analysis first — full Brizy content audit before any changes
- Explicit user confirmation before creating any duplicates
- Snapshot before every write — `respira_get_snapshot` captures the target so it can be returned to its exact prior state
- Duplicate-first only — never modifies live/published Brizy content
- Never auto-publishes duplicates
- Explicit rollback path — restore the snapshot via `respira_restore_snapshot`, or delete the draft duplicates, to undo a migration cleanly
- Preserves all original Brizy content untouched
## Honest Disclaimer
This skill converts Brizy page structures to Gutenberg block markup and creates duplicates for review.
It cannot:
- Guarantee pixel-perfect visual parity between builders
- Migrate Brizy popups or forms automatically
- Convert Brizy Pro dynamic content features
- Replicate hover effects or animations
- Replace a thorough manual QA pass on every page
It can:
- Map 65-80% of standard Brizy components to core Gutenberg blocks
- Preserve content, images, links, and basic layout structure
- Move you off a third-party builder dependency to native WordPress
- 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_get_snapshot`
- `respira_restore_snapshot`
- `respira_find_element`
- `respira_update_element`
- `respira_batch_update`
- `respira_create_page_duplicate`
- `respira_create_post_duplicate`
- `respira_update_page`
- `respira_update_post`
- `respira_read_page`
- `respira_read_post`
## Telemetry
After run completion, send fire-and-forget usage tracking to:
