/migrate-thrive-architect-to-gutenberg

name: migrate-thrive-architect-to-gutenberg
description: "Use when the user says 'migrate thrive architect to gutenberg', 'convert thrive to blocks', or 'replace thrive architect with native wordpress'. Parses Thrive Architect content, maps elements to core blocks, and creates draft duplicates for review."
license: MIT
metadata:
  author: Respira for WordPress
  author_url: https://respira.press
  version: 2.2.0
  mcp-server: respira-wordpress
  category: migration

Migrate Thrive Architect to Gutenberg

**Version:** 2.2.0 **Updated:** 2026-09-13 **Freshly updated:** v2.1.0 adds design-token awareness: conversion writes register the colors, font families and font sizes they carry as named presets in the block editor's own global styles (the palette, fontFamilies and fontSizes), and converted pages reference those presets instead of carrying value copies. A font token named for the body or heading also sets the site-wide body or heading font; font weights are not registered. Reuse registered tokens instead of re-inlining raw values, and report the registration in the migration summary.

Full-site migration from Thrive Architect to the WordPress block editor (Gutenberg). Audits every Thrive-built 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 Thrive Architect to Gutenberg, switching from Thrive to blocks, converting Thrive pages to the block editor, or moving away from Thrive Architect to native WordPress.

What This Skill Does

Thrive Architect is a conversion-focused page builder with a strong emphasis on marketing elements — lead generation forms, countdown timers, testimonials, and content reveal animations. It stores content in its own custom format. Gutenberg uses a flat block structure in `post_content` with HTML comment delimiters. The migration is moderate in complexity: standard content elements translate well, but Thrive's marketing-specific components have no direct Gutenberg equivalents and require alternative solutions.

This skill reads every Thrive Architect 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:**

• Content Box → Group block mapping
• Column layouts → Columns/Column block mapping
• Text elements → Paragraph/Heading blocks
• Image elements → Image block
• Button elements → Buttons/Button block
• Video elements → Video/Embed block
• Divider → Separator block
• Custom HTML/code content
• Background sections → Group block with background styles
• Styled lists → List block
• Blockquote/Testimonial → Quote block (basic mapping)

What This Skill Does NOT Do

• Migrate Thrive Leads opt-in forms — a separate email marketing/form solution is needed
• Convert Thrive Ultimatum countdown timers — no native Gutenberg equivalent
• Replicate Thrive's content reveal (click-to-expand) functionality
• Migrate Thrive Quiz Builder or Thrive Apprentice integrations
• Convert Thrive-specific A/B test variants — flagged for reference only
• Preserve Thrive's scroll-triggered animations — Gutenberg has limited animation support
• Migrate Thrive landing page templates — must be rebuilt from the Gutenberg block structure
• Guarantee pixel-perfect visual parity — different rendering approaches

Requirements

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

Trigger Phrase

• "migrate thrive architect to gutenberg"

Alternative Triggers

• "convert thrive to blocks"
• "switch from thrive architect to gutenberg"
• "move thrive pages to block editor"
• "replace thrive architect with gutenberg"
• "thrive architect to wordpress blocks"
• "migrate thrive to native wordpress"

Builder Technical Context

**Source: Thrive Architect**

• Content stored via Thrive's custom format in post_meta
• Conversion-focused component library with marketing elements
• Read via `respira_extract_builder_content` with `builder=thrive`
• Components: content boxes, columns, text, image, button, video, lead generation, countdown, testimonial, styled list, toggle, tabs, 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 (`respira_update_page` / `respira_update_post`)
• Core blocks: `paragraph`, `heading`, `image`, `buttons`, `columns`, `group`, `html`, `video`, `separator`, `quote`, `list`, `embed`, etc.

Execution Workflow

Phase 1: Pre-Migration Audit

1. Verify Respira + MCP connection via `respira_get_site_context`. If unavailable, stop and show setup guidance. 2. Detect Thrive Architect presence via `respira_get_builder_info` or `respira_list_plugins`. 3. Inventory all Thrive-built content:

• `respira_list_pages` and `respira_list_posts` — identify all content
• `respira_find_builder_targets` with `builder=thrive` — find Thrive-managed pages

4. For each Thrive page, extract content:

• `respira_extract_builder_content` with `builder=thrive`
• Catalog: element types used, marketing components (forms, countdowns, testimonials), A/B test variants, custom CSS

5. Produce an **Audit Report**:

• Total pages/posts using Thrive Architect
• Element type frequency (how many content boxes, text blocks, images, etc.)
• Marketing component inventory (lead gen forms, countdowns, quizzes)
• Complexity flags (Thrive Leads integration, A/B tests, landing pages, Thrive Suite dependencies)

-