Convert your Oxygen Classic layouts, styles, and classes to Breakdance format — and write directly to your target site.

Moving from Oxygen Classic (v4.x) to Breakdance? Rebuilding every element manually isn't your only option. TransferForge converts your Oxygen Classic data through the TFIS pipeline and writes native Breakdance output to your target WordPress site — preserving structure, styles, and class information.

How It Works

1. Install the bridge and connect your sites
Install the TransferForge Bridge plugin on both your Oxygen Classic source site and your Breakdance target site. Connect both in the TransferForge dashboard. Setup guide →

2. Pull templates from your source site
The dashboard fetches pages, templates, and components directly from your Oxygen Classic site.

3. Convert through TFIS
TransferForge reads Oxygen Classic data, normalizes it into the TFIS intermediate format, and renders it into Breakdance's native storage structure — including the correct tree_json_string format, EssentialElements\Section type naming, and numeric element IDs that Breakdance requires.

4. Push to your Breakdance site
The bridge plugin writes converted data to the _breakdance_data post meta on your target site. Templates appear in Breakdance's editor ready for review.

5. Review and refine
Open the page in Breakdance and verify. Standard layouts transfer cleanly. Adjust any elements that need builder-specific fine-tuning.

What Converts

Feature	Manual Rebuild	TransferForge
Layout structure	Start from scratch	Automatic
Style properties	Copy values manually	Converted to Breakdance design format
AutomaticCSS classes	Re-apply or rebuild	Preserved + converted to native design values
Responsive breakpoints	Set up per breakpoint	Mapped (Oxygen → Breakdance breakpoints)
Breakdance-native output	N/A	Correct JSON structure, escaping, and storage
Time per page	30–60+ minutes	Seconds

What's Supported

Elements: Sections, divs, headings, text blocks, buttons, and containers convert to their Breakdance equivalents (EssentialElements\Section, EssentialElements\Heading, etc.). Unsupported elements fall back to EssentialElements\Div to preserve the page structure.

Styles: Spacing (margin/padding), backgrounds, colors, typography, and layout properties are converted into Breakdance's properties.design format with proper breakpoint keys.

AutomaticCSS: Utility classes like grid--3, gap--m, grid--l-2, and pad--s are both preserved on the element (under settings.advanced.classes) and converted to native Breakdance design values (e.g., layout_v2.grid_template_columns).

Not yet supported: Interactive elements (accordions, tabs, sliders), WooCommerce elements, OxyExtras/OxyNinja components, and dynamic data beyond basic post fields. These are on the roadmap.

FAQ

Will the output work natively in Breakdance?
Yes. TransferForge writes to Breakdance's exact storage format — the same tree_json_string structure that Breakdance itself creates. Templates appear in the Breakdance editor as native elements.

What about complex layouts?
Grids and flexbox layouts convert when expressed through standard CSS properties or AutomaticCSS utility classes. Highly custom CSS or builder-specific layout features may need manual adjustment after conversion.

Can I batch convert multiple pages?
Yes. The dashboard lets you select multiple pages and templates to convert and push in a single workflow.

Ready to migrate? Sign up or read the full docs.