migrate-visual-composer-to-gutenberg

Migrate Visual Composer pages to native WordPress Gutenberg blocks via duplicates.

40|7|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/respira-press/agent-skills-wordpress --skill migrate-visual-composer-to-gutenberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-visual-composer-to-gutenberg
Source: https://github.com/respira-press/agent-skills-wordpress/tree/main/skills/migrate-visual-composer-to-gutenberg
Command: npx skills add https://github.com/respira-press/agent-skills-wordpress --skill migrate-visual-composer-to-gutenberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual Composer to Gutenberg migration is complex and risky if done in-place. This skill reads VC content, maps elements to Gutenberg blocks, builds a safe migration plan, and executes page-by-page conversion into native block markup via duplicates so the live site stays untouched.

Core Features & Use Cases

  • Audit existing VC content across pages to identify element types, nesting, and deprecated elements.
  • Map VC elements to Gutenberg blocks, preserving structure and content while creating duplicate drafts for review.
  • Execute page-by-page conversions into native WordPress blocks, enabling safe review before going live.

Quick Start

Convert your first Visual Composer page to Gutenberg by running a migration plan and reviewing the duplicate, leaving live VC content untouched.

Frequently Asked Questions about migrate-visual-composer-to-gutenberg

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

FAQPage Schema
How do I migrate Visual Composer pages to Gutenberg safely?

Migrate Visual Composer pages to Gutenberg safely by auditing VC content, mapping elements to native blocks, and converting page duplicates for review, keeping live pages untouched.

What is the best way to convert WPBakery content to native WordPress blocks?

Converting WPBakery content to native WordPress blocks requires auditing existing VC elements, mapping them to Gutenberg blocks, and executing page-by-page conversions into duplicates for safe review before going live.

Can I migrate Visual Composer pages without disrupting my live WordPress site?

Yes, you can migrate Visual Composer pages without live site disruption by creating page duplicates and converting the duplicated drafts into Gutenberg blocks, leaving the original VC content untouched during the transition.

Does the Visual Composer to Gutenberg migration preserve images and links?

Yes, the Visual Composer to Gutenberg migration preserves content, images, and links by mapping VC elements to native WordPress blocks while building a safe conversion plan for page duplicates.

What do I need to convert Visual Composer pages to Gutenberg block markup?

Converting Visual Composer pages to Gutenberg block markup requires the Respira for WordPress plugin connected via MCP, access to existing VC content, and permission to create page duplicates for review.

How does the Visual Composer to Gutenberg migration handle deprecated VC elements?

The Visual Composer to Gutenberg migration handles deprecated elements by auditing existing VC content across pages to identify element types, nesting, and deprecated elements before mapping them to Gutenberg blocks.