migrate-brizy-to-gutenberg

Audit Brizy pages and translate components into native Gutenberg blocks.

40|7|Updated Mar 7, 2026

Search Tags:#automation #migration #blocks #wordpress #gutenberg #brizy

Ready to run

npx skills add https://github.com/respira-press/agent-skills-wordpress --skill migrate-brizy-to-gutenberg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-brizy-to-gutenberg
Source: https://github.com/respira-press/agent-skills-wordpress/tree/main/skills/migrate-brizy-to-gutenberg
Command: npx skills add https://github.com/respira-press/agent-skills-wordpress --skill migrate-brizy-to-gutenberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Brizy-to-Gutenberg migrations by auditing Brizy-built pages and translating components into native Gutenberg blocks.

Core Features & Use Cases

Audits Brizy content across the site and inventories all components and layouts
Maps Brizy sections/rows/columns/text/image/button/video to Gutenberg blocks
Generates a migration plan and creates duplicate pages with Gutenberg markup for review before going live
Performs a safe, duplicate-first workflow to avoid touching live Brizy content
Supports switching Brizy sites to native WordPress blocks with minimal disruption

Quick Start

Trigger the migration by saying "migrate brizy to gutenberg" and let the skill perform a full Brizy audit, propose a migration plan, and create duplicate Gutenberg-ready pages for review.

Frequently Asked Questions about migrate-brizy-to-gutenberg

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate Brizy pages to Gutenberg blocks safely?▼

Migrate Brizy to Gutenberg safely by auditing Brizy-built pages, translating components into native blocks, and generating duplicate pages for review rather than modifying live content. This duplicate-first workflow prevents disruption to your active site.

Does the Brizy to Gutenberg migration modify my live content?▼

No, the Brizy to Gutenberg migration does not modify live content. It creates duplicate pages with Gutenberg markup so you can review the native blocks before publishing, ensuring a safe workflow and zero disruption to your live Brizy site.

What do I need to automate Brizy to Gutenberg migration?▼

To automate Brizy to Gutenberg migration, you need the Respira for WordPress plugin, an active MCP connection, Brizy Builder on the source site, and read/write access to create duplicate pages for translating Brizy components into native blocks.

Can all Brizy components be mapped to native WordPress blocks?▼

Brizy sections, rows, columns, text, image, button, and video components map to native WordPress blocks. The migration plan highlights unmappable elements, ensuring you know exactly which Brizy components cannot be automatically translated before finalizing the duplicate pages.

What is the best way to switch a Brizy site to native WordPress blocks?▼

The best way to switch a Brizy site to native WordPress blocks is using a duplicate-first migration workflow. It inventories Brizy content, proposes a migration plan, and creates duplicate Gutenberg-ready pages for review, minimizing disruption during the transition.

Are there limitations when translating Brizy sections to Gutenberg?▼

Limitations when translating Brizy sections to Gutenberg include unmappable elements that cannot be automatically converted. The migration workflow addresses this by producing a detailed migration plan that highlights these specific components for manual review.