migrate-brizy-to-gutenberg

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.

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.

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.

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.

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.

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.