migrate-visual-composer-to-gutenberg

Migrate Visual Composer to Gutenberg

Full-site migration from Visual Composer (WPBakery) to the WordPress block editor (Gutenberg). Audits every Visual Composer page, maps elements 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 Visual Composer to Gutenberg, switching from WPBakery to blocks, converting Visual Composer pages to the block editor, or moving away from Visual Composer to native WordPress.

What This Skill Does

Visual Composer (now WPBakery Page Builder in its classic form, and Visual Composer Website Builder in its newer form) stores content in post_meta using VCV's custom JSON format. It has been one of the most widely-used WordPress page builders, bundled with thousands of themes. Gutenberg uses a flat block structure in post_content with HTML comment delimiters. The migration is moderate: Visual Composer's row/column grid and standard elements translate to Gutenberg, but the ecosystem of third-party VC add-ons and theme-bundled custom elements is vast and varied.

This skill reads every Visual Composer page, extracts the builder content, translates each element 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:

• vc_row → Group block mapping
• vc_column → Columns/Column block mapping
• vc_column_text → Paragraph/Heading blocks
• vc_single_image → Image block
• vc_btn / vc_button → Buttons/Button block
• vc_video → Video/Embed block
• vc_separator / vc_text_separator → Separator block
• vc_raw_html → Custom HTML block
• vc_empty_space → Spacer block
• vc_custom_heading → Heading block
• vc_row_inner / vc_column_inner → nested Columns blocks
• vc_toggle (FAQ-style) → basic heading + paragraph (flagged for Details block)
• vc_tabs / vc_accordion → basic content fallback (flagged for manual enhancement)

What This Skill Does NOT Do

• Migrate Visual Composer's Design Options (box shadows, borders, gradients) 1:1 — Gutenberg has different styling capabilities
• Convert third-party VC add-on elements (Ultimate Addons, Starter Sites, theme-specific elements) — flagged for manual handling
• Migrate Visual Composer's template library — must be rebuilt in Gutenberg
• Convert WPBakery's frontend editor custom CSS — must be moved to theme/Additional CSS
• Handle the newer Visual Composer Website Builder (vcwb) — this skill targets the classic VCV/WPBakery format
• Replicate VC's parallax backgrounds or scroll effects — Gutenberg has limited support
• Guarantee pixel-perfect visual parity — different rendering approaches

Requirements

• Respira for WordPress plugin installed and connected
• MCP connection active (desktop or WebMCP)
• Visual Composer / WPBakery active on the source site
• Read access to scan Visual Composer content
• Write access to create duplicates with Gutenberg content

Trigger Phrase

• "migrate visual composer to gutenberg"

Alternative Triggers

• "convert visual composer to blocks"
• "switch from wpbakery to gutenberg"
• "move visual composer to block editor"
• "replace wpbakery with gutenberg"
• "visual composer to wordpress blocks"
• "migrate wpbakery to native wordpress"
• "convert vc to gutenberg"

Builder Technical Context

Source: Visual Composer

• Content stored in post_meta using VCV's custom JSON format
• Shortcode-based structure in classic mode: [vc_row][vc_column][vc_column_text]...[/vc_column_text][/vc_column][/vc_row]
• Read via wordpress_extract_builder_content with builder=visual-composer
• Elements: vc_row, vc_column, vc_column_text, vc_single_image, vc_btn, vc_video, vc_separator, vc_raw_html, vc_empty_space, vc_custom_heading, vc_toggle, vc_tabs, vc_accordion, vc_row_inner, vc_column_inner, etc.

Target: Gutenberg (Block Editor)

• Content stored in post_content as HTML with block comment delimiters
• Format: <!-- wp:paragraph --><p>Text</p><!-- /wp:paragraph -->
• Write via standard WordPress content tools (wordpress_update_page / wordpress_update_post)
• Core blocks: paragraph, heading, image, buttons, columns, group, html, video, separator, spacer, embed, etc.

Execution Workflow

Phase 1: Pre-Migration Audit

1. Verify Respira + MCP connection via wordpress_get_site_context. If unavailable, stop and show setup guidance.
2. Detect Visual Composer presence via wordpress_get_builder_info or wordpress_list_plugins.
3. Inventory all Visual Composer content:
4. wordpress_list_pages and wordpress_list_posts — identify all content
5. wordpress_find_builder_targets with builder=visual-composer — find VC-managed pages
6. For each VC page, extract content:
7. wordpress_extract_builder_content with builder=visual-composer
8. Catalog: element types used, nesting depth, third-party elements, Design Options usage, custom CSS
9. Produce an Audit Report:
10. Total pages/posts using Visual Composer
11. Element type frequency (how many rows, columns, text blocks, images, etc.)
12. Third-party element inventory (elements not in core VC)
13. Complexity flags (nested rows, custom CSS, parallax, third-party add-ons)
14. Estimated migration difficulty per page (simple / moderate / complex)

Phase 2: Migration Plan

Present a structured migration plan:

## Visual Composer → Gutenberg Migration Plan

### Site Overview
- Total Visual Composer pages: X
- Simple pages (direct mapping): X
- Moderate pages (some manual review needed): X
- Complex pages (significant manual work): X

### Element Mapping
| VC Element | Gutenberg Block | Notes |
|---|---|---|
| vc_row | Group | Container mapping |
| vc_column | Columns / Column | Width ratios preserved where possible |
| vc_column_text | Paragraph / Heading | Rich text parsed into blocks |
| vc_single_image | Image | Direct mapping |
| vc_btn | Buttons > Button | Wrapped in container |
| vc_empty_space | Spacer | Height preserved |
| vc_raw_html | Custom HTML | Direct mapping |
| vc_tabs | [MANUAL] | Content migrated, tabs need plugin |
| ... | ... | ... |

### Migration Order
1. [Page Title] — Simple — estimated 2 min
2. [Page Title] — Moderate — estimated 5 min
...

### Items Requiring Manual Attention
- [Page X] — Ultimate Addons carousel (no core equivalent)
- [Page Y] — Theme-specific VC element
- [Page Z] — Custom CSS in Design Options
- VC template library — must be rebuilt in Gutenberg

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 Visual Composer content via wordpress_extract_builder_content with builder=visual-composer
2. Map each VC element to Gutenberg blocks:
3. vc_row → <!-- wp:group --> blocks
4. vc_column → <!-- wp:columns --> with <!-- wp:column --> children (map width attributes)
5. vc_column_text → Parse rich text into <!-- wp:paragraph --> and <!-- wp:heading --> blocks
6. vc_single_image → <!-- wp:image --> with src, alt, caption
7. vc_btn → <!-- wp:buttons --> wrapper with <!-- wp:button --> child
8. vc_video → <!-- wp:embed --> block with video URL
9. vc_separator → <!-- wp:separator --> block
10. vc_empty_space → <!-- wp:spacer --> block with height
11. vc_raw_html → <!-- wp:html --> block
12. vc_custom_heading → <!-- wp:heading --> block with level and alignment
13. vc_row_inner/vc_column_inner → nested <!-- wp:columns --> blocks
14. Preserve text content, image URLs, link targets
15. Flag unmappable