TransferForge follows a three-step workflow: pull templates from your source site, convert through the TFIS pipeline, and push to your target builder. This guide walks through each step.

Before You Start

Make sure you've completed the setup:

TransferForge account created at app.transferforge.com
Bridge plugin installed and activated on both source and target WordPress sites
Both sites connected in the dashboard with application passwords

If you haven't done this yet, follow the installation guide first.

Step 1 — Pull Templates From Your Source Site

In the TransferForge dashboard, select your source site from the site list.
Click Pull to fetch templates, pages, and builder data from the source.
The dashboard will display a list of available content — pages, templates, components, and their builder structure.

You can review what was pulled before converting anything. The dashboard shows per-page status so you know exactly what you're working with.

Step 2 — Convert Through TFIS

Select the pages or templates you want to convert.
Choose your target builder (Oxygen 6 or Breakdance).
Click Convert.

TransferForge reads the Oxygen Classic data, normalizes it into the TFIS intermediate format, and renders it into the target builder's expected structure — including element types, style properties, class mappings, and layout values.

Conversion options:

Preserve dynamic data — maintains content bindings and shortcodes where supported
Include styles — converts CSS properties, spacing, backgrounds, and typography
Flatten utility classes — converts AutomaticCSS utility classes into native design values (when off, classes are preserved on elements and also converted)

The conversion runs on our API — results are typically ready in a few seconds.

Step 3 — Push to Your Target Site

Review the conversion output in the dashboard. You'll see the converted structure and can compare it against the source.
When you're satisfied, click Push to write the converted data to your target WordPress site.
The bridge plugin writes to the correct post meta and storage locations for your target builder (Oxygen 6 or Breakdance).

Verified writes: After pushing, TransferForge reads back the data from the target site to confirm the write succeeded. Per-page status updates in the dashboard so you can track what's been converted, what's queued, and what needs attention.

Step 4 — Review in the Target Builder

Open the target page or template in your builder (Oxygen 6 or Breakdance).
Verify the layout, styles, and content transferred correctly.
Make any manual adjustments needed for builder-specific features or complex elements.

Most standard layouts (sections, divs, headings, text, buttons, images) transfer cleanly. Elements that don't have a direct equivalent in the target builder are converted to generic containers to preserve structure.

Tips for Best Results

Start with a staging or development site as your target. Don't push to production until you've verified the output.

Convert in batches if you have a large site. The dashboard's per-page status tracking makes it easy to work through a site methodically.

Check AutomaticCSS results. If your source site uses ACSS, review the converted values — TransferForge resolves utility classes to concrete CSS values using your site's configuration, but complex or custom ACSS setups may need manual review.

Report issues. If a conversion produces unexpected results, email hello@transferforge.com with the source and target details. Bug reports help us improve the conversion engine for everyone.

Important Notes

Element support: TransferForge currently converts 8 core Oxygen element types (section, div, heading, text, button, image, and basic containers). Interactive elements (accordions, tabs, sliders), WooCommerce elements, and third-party extension components (OxyExtras, OxyNinja) are not yet supported — unsupported elements fall back to a generic div.

Third-party plugins: OxyExtras and OxyNinja support depends on their compatibility with the conversion pipeline. We're actively working on broader third-party support.

Not affiliated with Oxygen/Soflyy or Breakdance/Soflyy. TransferForge is an independent tool. Support for newly released builder features may lag behind official releases until stable documentation is available.