TransferForge is a migration platform that converts WordPress page builder data from one format to another through a neutral intermediate schema called TFIS. It currently supports Oxygen Classic (v4.x) as a source, with Oxygen 6 and Breakdance as targets.

The platform has two parts: a web app at app.transferforge.com where you manage migrations, and a lightweight bridge plugin installed on your WordPress source and target sites to expose builder data that the REST API doesn't cover.

Get Started

New to TransferForge? Follow our step-by-step guides:

How It Works

Install the bridge plugin on your source (Oxygen Classic) and target (Oxygen 6 or Breakdance) WordPress sites. The bridge exposes builder-specific storage that the standard REST API doesn't cover.
Connect your sites in the TransferForge dashboard using your site URL and a WordPress application password. The app authenticates through standard WordPress REST API auth — no FTP, no direct database access.
Pull templates from the source site. The dashboard lists pages, templates, and components so you can see what you're working with before converting anything.
Convert through TFIS. The conversion engine reads your Oxygen Classic data, normalizes it into the TransferForge Intermediate Schema (TFIS), and then renders it into the target builder's format — whether that's Oxygen 6 or Breakdance.
Push to your target site. Write the converted layouts, styles, and classes to the target WordPress site. The bridge plugin writes to the correct post meta and storage locations for each builder.
Review and refine. Open the target builder and verify the output. Most layouts transfer cleanly; complex or builder-specific features may need manual touch-up.

What's Supported

Source builders:

Oxygen Classic (v4.x) — full support

Target builders:

Oxygen 6 — full support
Breakdance — full support (via TFIS pipeline)

Supported elements: Sections, divs, headings, text blocks, buttons, images, and basic containers convert accurately. Unsupported elements (interactive components, WooCommerce elements, navigation menus) fall back to a generic div to preserve structure.

Style handling: Classes, spacing (margin/padding), backgrounds, colors, typography, and layout properties are converted. AutomaticCSS utility classes (e.g., grid--3, gap--m, pad--s) are preserved on the element and also converted into native design values for the target builder.

Not yet supported:

Third-party Oxygen extensions (OxyExtras, OxyNinja) — partial support may work but is not guaranteed
Interactive elements (accordions, tabs, sliders)
Dynamic data beyond basic post fields
WooCommerce-specific elements
Advanced CSS (transforms, animations, custom CSS blocks)

These are on the roadmap and being actively developed.

Updates & Compatibility

TransferForge is under active development. The conversion engine runs on a SvelteKit API deployed to Vercel, so improvements ship instantly — no plugin update needed for conversion logic changes.

The bridge plugin receives periodic updates through the WordPress admin. Keep it updated for the latest endpoint support.

Future Builder Support

Our long-term goal is cross-builder migration. The TFIS intermediate format is designed so that adding a new source or target builder doesn't require rewriting existing conversion logic.

On the roadmap:

Bricks Builder (as a target)
Additional source builders
Elementor (planned, no timeline yet)

Got Ideas or Found a Bug?

We build TransferForge with the community. If you've found a bug, have a feature request, or want to share feedback:

Email hello@transferforge.com
See the roadmap for what's planned
Use the support form for product issues

Support Scope

We support TransferForge migration workflows end-to-end — from bridge installation through conversion and push to target. For general Oxygen or Breakdance builder questions unrelated to migration, the respective builder's documentation is the best resource.