migrate-divi-to-bricks

To migrate Divi pages to Bricks, the system parses Divi shortcode hierarchies from post_content, maps modules to Bricks equivalents, and writes the resulting Bricks JSON directly to page meta fields for review.

Shortcode parsing for Divi to Bricks conversion extracts nested module structures from post_content, resolves the hierarchy, and auto-maps each Divi module to its corresponding Bricks element while preserving content and settings.

Yes, converting Divi content requires Bricks installed, an active Respira MCP connection, access to Divi content, and read/write access to post meta fields like post_content and _bricks_page_content_2.

Auto-mapping Divi modules to Bricks elements is best handled by generating a page-by-page migration plan with conversion notes and safety checks before writing Bricks JSON drafts.

Original Divi pages remain untouched during migration; the tool writes converted Bricks JSON to the _bricks_page_content_2 field, generating drafts ready for review in the Bricks editor.

Supported Divi modules for Bricks conversion include standard layout structures and elements like text, image, button, tabs, and accordion, with content, media, and settings preserved during the mapping process.