Migrate Oxygen To Breakdance

Migrate Oxygen to Breakdance

Version: 2.1.0 Updated: 2026-08-04 Freshly updated: v2.1.0 adds design-token awareness: conversion writes now register the colors and typography they carry as named design tokens in Breakdance's own global styles, and converted pages reference those tokens instead of carrying value copies. Reuse registered tokens instead of re-inlining raw values, and report the registration in the migration summary.

Full-site migration from Oxygen Builder to Breakdance. Audits every Oxygen-built page, maps components to their Breakdance equivalents, builds a migration plan for approval, and executes page-by-page conversion — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Oxygen to Breakdance, switching from Oxygen to Breakdance, converting Oxygen pages to Breakdance, or replacing Oxygen with Breakdance.

What This Skill Does

Oxygen and Breakdance share the same developer lineage (Soflyy), which makes this one of the smoothest builder migrations available. Many component concepts, naming conventions, and architectural decisions carry over directly. However, the underlying storage formats are completely different — Oxygen uses JSON shortcodes in ct_builder_shortcodes while Breakdance uses its own post_meta format — so content must still be extracted, mapped, and re-encoded.

This skill reads every Oxygen page, extracts the builder content, translates each component to its Breakdance equivalent, and writes the result to duplicate pages in Breakdance format — giving you a complete parallel version of your site to review before going live.

Handles:

• Section → Breakdance Section mapping
• Container/Div → Breakdance Div mapping
• Heading, Text, Image, Button, Video, Icon components
• Flexbox layout settings (direction, alignment, gap, wrap)
• Column/grid structures
• Custom CSS classes and inline styles
• Link elements and CTAs
• Code blocks and custom HTML

What This Skill Does NOT Do

• Migrate Oxygen's Global Styles or Style Sheets — Breakdance uses its own global styling system
• Convert Oxygen conditions (visibility rules) — Breakdance has its own conditions system that must be configured separately
• Migrate Oxygen's custom PHP/code block logic — flagged for manual porting
• Recreate Oxygen templates (headers, footers, archives) — Breakdance templates must be rebuilt using its template system
• Transfer WooCommerce builder templates — product/shop templates need separate handling
• Guarantee pixel-perfect visual parity — some spacing/sizing will need fine-tuning

Requirements

• Respira for WordPress plugin installed and connected
• MCP connection active (desktop or WebMCP)
• Oxygen Builder active on the source site
• Breakdance installed on the target site (can be the same site)
• Read access to scan Oxygen content
• Write access to create duplicates with Breakdance content

Trigger Phrase

• "migrate oxygen to breakdance"

Alternative Triggers

• "convert oxygen to breakdance"
• "switch from oxygen to breakdance"
• "move oxygen pages to breakdance"
• "replace oxygen with breakdance"
• "oxygen to breakdance migration"
• "upgrade oxygen to breakdance"

Builder Technical Context

Source: Oxygen Builder

• Content stored in post_meta key ct_builder_shortcodes
• JSON-based structure encoding nested components
• Read via respira_extract_builder_content with builder=oxygen
• Components: ct_section, ct_div, ct_headline, ct_text_block, ct_image, ct_link_button, etc.

Target: Breakdance

• Content stored in post_meta
• Write via respira_inject_builder_content with builder=breakdance
• Elements: EssentialElements\Section, EssentialElements\Div, EssentialElements\Heading, EssentialElements\Text, EssentialElements\Image, EssentialElements\Button, 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 Oxygen presence via respira_get_builder_info or respira_list_plugins.
3. Inventory all Oxygen-built content:
   • respira_list_pages and respira_list_posts — identify all content
   • respira_find_builder_targets with builder=oxygen — find Oxygen-managed pages
4. For each Oxygen page, extract content:
   • respira_extract_builder_content with builder=oxygen
   • Catalog: component types used, nesting depth, custom CSS, dynamic data usage, code blocks
5. Produce an Audit Report:
   • Total pages/posts using Oxygen
   • Component type frequency (how many sections, headings, images, etc.)
   • Complexity flags (custom PHP, conditions, dynamic data, WooCommerce templates)
   • Estimated migration difficulty per page (simple / moderate / complex)

Phase 2: Migration Plan

Present a structured migration plan:

## Oxygen → Breakdance Migration Plan

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

### Component Mapping
| Oxygen Component | Breakdance Equivalent | Notes |
|---|---|---|
| ct_section | Section | Direct mapping — same developer lineage |
| ct_div | Div | Direct mapping |
| ct_headline | Heading | Direct mapping |
| ... | ... | ... |

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

### Items Requiring Manual Attention
- [Page X] — Custom PHP code block
- [Page Y] — Oxygen condition logic
- Global Styles — must be recreated in Breakdance Global Settings

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 Oxygen content via respira_extract_builder_content with builder=oxygen
2. Map each Oxygen component to its Breakdance equivalent:
   • Translate component types (ct_section → Section, ct_div → Div, etc.)
   • Convert layout properties (flexbox settings, spacing, sizing)
   • Map CSS classes and inline styles
   • Preserve text content, image URLs, link targets
   • Flag any unmappable components (custom PHP, conditions) with inline comments
3. Build the Breakdance content structure
4. Take a respira_get_snapshot checkpoint of the target before any write, so the page can be restored exactly if the conversion needs unwinding
5. Create a duplicate via respira_create_page_duplicate or respira_create_post_duplicate
6. Inject Breakdance content into the duplicate via respira_inject_builder_content with builder=breakdance
7. Surgical fixes (not a re-inject): when a single element lands wrong — a heading, a button label, a spacing value — locate it with respira_find_element and correct it in place with respira_update_element. For repeated corrections across many elements or several migrated pages, batch them with respira_batch_update rather than re-injecting whole pages.
8. Log the migration result (success, warnings, manual review items)

Phase 4: Post-Migration Verification

1. Summarize all migrated pages with status:
   • Design tokens registered in Breakdance's global styles (token names and counts)
   • Clean migrations (no issues)
   • Migrations with warnings (flagged items needing review)
   • Failed migrations (if any)
2. List all manual review items:
   • Custom PHP code blocks that need porting
   • Dynamic data references that need reconnecting
   • Oxygen conditions that need rebuilding in Breakdance
3. Provide review instructions:
   • Where to find duplicates in WordPress admin
   • How to preview Breakdance pages
   • How to delete duplicates if not wanted

Design Tokens

Conversion writes now register the colors and typography they carry as named design tokens in Breakdance's own global styles, and the converted pages reference those tokens instead of carrying value copies. When fixing or extending a migrated page, reuse the registered tokens (respira_list_design_tokens shows them) rather than re-inlining raw hex values or font stacks. And say so when you finish: the migration summary should name the tokens that were registered and note that migrated pages reference them.

Safety Model

• Read-only analysis first — full Oxygen content audit before any changes
• Explicit user confirmation before creating any duplicates
• Snapshot before every write — respira_get_snapshot captures the target so it can be returned to its exact prior state
• Duplicate-first only — never modifies live/published Oxygen content
• Never auto-publishes duplicates
• Explicit rollback path — restore the snapshot via respira_restore_snapshot, or delete the draft duplicates, to undo a migration cleanly
• Preserves all original Oxygen content untouched

Honest Disclaimer

This skill converts Oxygen page structures to Breakdance format and creates duplicates for review.

It cannot:

• Guarantee pixel-perfect visual parity between builders
• Migrate Oxygen Global Styles or conditions automatically
• Convert custom PHP code blocks to Breakdance equivalents
• Handle WooCommerce template migrations
• Replace a thorough manual QA pass on every page

It can:

• Leverage the shared developer lineage for high-fidelity component mapping
• Map 85-95% of standard Oxygen components to Breakdance equivalents
• Preserve content, images, links, and layout structure
• Save days of manual rebuild work
• Identify exactly what needs manual attention

Tooling

Core WordPress tools

• respira_get_site_context
• respira_get_builder_info
• respira_list_pages
• respira_list_posts
• respira_list_plugins
• respira_find_builder_targets
• respira_extract_builder_content
• respira_inject_builder_content
• respira_get_snapshot
• respira_restore_snapshot
• respira_find_element
• respira_update_element
• respira_batch_update
• respira_create_page_duplicate
• respira_create_post_duplicate
• respira_read_page
• respira_read_post

Telemetry

After run completion, send fire-and-forget usage tracking to:

• POST https://www.respira.press/api/skills/track-usage

Include:

• skill_slug = migrate-oxygen-to-breakdance
• site/version context
• duration and success
• pages audited, pages migrated, warnings count
• tools used

Never block user flow on telemetry failure.

Related Skills

• WordPress Site DNA (understand site structure before migrating)
• Technical Debt Audit (clean up before or after migration)
• SEO & AEO Amplifier (verify SEO preservation post-migration)

Built by Respira Team https://respira.press/skills/migrate-oxygen-to-breakdance