← All migration paths

Migrate away from Oxygen

Oxygen stores its pages as JSON component tree. That single fact decides what a migration can carry across and what it cannot, so it is where this page starts.

What Oxygen stores

Oxygen stores a JSON component tree and, unlike most builders, replaces the theme entirely rather than sitting inside it. Oxygen 6 (Jenga) changed the namespace, so a site on 6 and a site on 4 are meaningfully different sources.

The part that actually costs time

Because Oxygen replaces the theme, there is no theme to fall back on when it is removed. A migration has to supply the header, footer and template layer as well as the page content, which is work that a builder-to-builder move normally does not include.

Carries across

  • Component hierarchy
  • Text and media
  • Class-based styling, which maps unusually well to Bricks
  • Reusable parts, as components

Needs a decision, or a rebuild

  • Header, footer and templates, since no theme remains underneath
  • Oxygen-specific dynamic data bindings
  • Code blocks holding raw PHP

Where you can go from Oxygen

Migrate Oxygen to Bricks
Converts Oxygen Builder pages to Bricks by mapping component trees to Bricks JSON elements and creating draft duplicates for review.
Migrate Oxygen to Breakdance
Converts Oxygen Builder pages to Breakdance by mapping component trees to Breakdance elements and creating draft duplicates for review.

Coming the other way, into Oxygen

Migrate Elementor to Oxygen

How the migration actually runs

The agent works on a duplicate of the page, not the live one. The original keeps serving while the converted copy waits for review, and every write captures a before-state so a bad conversion is one call to undo. Nothing publishes without a human approving it.

All 16 migration paths → Pricing →
Summarize with Google AI Mode