Routes
Supported conversion routes
Universal By Foundation labels route confidence clearly so you can see what is stable, what is beta, and what is still experimental before you commit work.
Elementor → Divi
Agency standardisation
Stable
Move Elementor layouts into Divi output
Builder-to-builder portability for teams standardising on Divi without rebuilding inherited Elementor sites from zero.
Strong on layout, core widgets, loops, menus, pricing, sliders, tabs, and accordions.
- Migration
- Agency
- Inherited sites
- Plugin-specific widgets may fall back to preserved structures
- Custom JavaScript is preserved, not recreated as native motion
View route
Elementor → Divi 4 Legacy
Stable route
Stable
Use Elementor to Divi 4 Legacy conversion
Convert Elementor source content into Divi 4 Legacy output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Elementor → Elementor
Re-export and audit
Stable
Clean and re-emit Elementor structures through the universal layer
Useful for validation, cleanup, and portability checks before larger migrations.
Strong on same-builder structural validation, preserved shortcode handling, and route audit work.
- Addon-heavy pages may still need review warnings
- Dynamic theme metadata is preserved structurally, not always rehydrated natively
View route
Elementor → HTML / Code
Stable route
Stable
Use Elementor to HTML / Code conversion
Convert Elementor source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Divi → Elementor
Legacy rescue
Stable
Move Divi layouts into Elementor output
Useful for inherited client sites, legacy rescue work, and teams moving into Elementor-based delivery.
Strong on Divi 5 and Divi legacy structural routes, with growing support for addon-heavy modules.
- Migration
- Legacy
- Client handover
- Advanced addon modules still rely on deterministic coverage or preserved fallback
- Theme-level behavior remains outside strict 1:1 parity
View route
Divi → HTML / Code
Stable route
Stable
Use Divi to HTML / Code conversion
Convert Divi source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Divi 4 Legacy → Elementor
Legacy shortcode route
Stable
Move Divi 4 legacy layouts into Elementor output
A legacy-specific route for shortcode-heavy Divi 4 sites that need Elementor-ready output without a full rebuild from scratch.
Stable on legacy shortcode parsing and structural output, with higher review expectations on bespoke or addon-heavy legacy modules.
- Bespoke shortcode wrappers may preserve structure rather than become native widgets
- Addon-heavy legacy pages still need manual review before import
View route
Divi 4 Legacy → HTML / Code
Stable route
Stable
Use Divi 4 Legacy to HTML / Code conversion
Convert Divi 4 Legacy source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Divi 4 Legacy
- HTML / Code
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Code → Elementor
Code handoff
Stable
Translate code and templates into Elementor-ready output
Best for landing pages, section libraries, and developer-to-marketer handoff.
Strong on structural HTML/CSS and preserved code blocks, with safe handling for PHP templates and JSX-oriented sources.
- Code
- Developer handoff
- Section libraries
- Complex app-shell behavior is preserved rather than rebuilt as native widgets
- Pixel-perfect script-driven UI remains out of scope
View route
Code → Divi
Template reuse
Stable
Turn code-based layouts into Divi-compatible output
Useful for modular landing pages, template reuse, and Divi-first delivery teams.
Strong on structural conversion and preserved code modules, with route-aware validation before export.
- Code
- Divi workflow
- Landing pages
- Custom interactions are preserved rather than rebuilt as native behavior
- Highly bespoke markup may land as code modules or preserved blocks
View route
Code → Divi 4 Legacy
Stable route
Stable
Use Code to Divi 4 Legacy conversion
Convert Code source content into Divi 4 Legacy output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Translate structural Figma data into Divi-oriented output
A beta landing route for Figma to Divi workflows where archive-safe extraction and structural output matter more than strict design parity.
Beta on archive-safe ingestion and shell semantics. Not yet a production-safe claim for broad design fidelity or component parity.
- Full binary-canvas parity is not yet live
- Component mapping remains beta and review-heavy
View route
Figma → Elementor
Beta route
Beta
Translate structural Figma data into Elementor-oriented output
A beta landing route for Figma to Elementor workflows where structural extraction and layout promotion matter more than design-fidelity promises.
Beta on archive-safe ingestion, shell semantics, and layout normalization. Not yet production-safe for broad design fidelity claims.
- Component resolution remains beta
- Do not treat this as a pixel-perfect design-to-builder promise
View route
Figma → HTML / Code
Beta route
Beta
Use Figma to HTML / Code conversion
Convert Figma source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Webflow → Divi
Beta route
Beta
Bring Webflow structure into Divi-oriented output
A beta landing route for Webflow to Divi experiments where layout extraction and shell semantics matter more than strict parity.
Beta on structure, shell semantics, and experimental builder output. Not yet a production-safe claim for Webflow interaction parity.
- Interaction semantics remain beta
- Component fidelity and production-ready parity are not yet guaranteed
View route
Webflow → Elementor
Beta route
Beta
Bring Webflow structure into Elementor-oriented output
A beta landing route for Webflow to Elementor experiments where structural extraction matters more than strict visual or interaction parity.
Beta on structure, grid semantics, and shell-level output. Not yet a production-safe parity claim for Webflow interactions or component fidelity.
- Interactions, variants, and component fidelity remain beta
- Use as a structure-aware starting point, not a 1:1 migration promise
View route
Webflow → HTML / Code
Beta route
Beta
Use Webflow to HTML / Code conversion
Convert Webflow source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Wix → Divi
Experimental route
Experimental
Use Wix to Divi conversion
Convert Wix source content into Divi output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Wix → Elementor
Experimental route
Experimental
Use Wix to Elementor conversion
Convert Wix source content into Elementor output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route
Wix → HTML / Code
Experimental route
Experimental
Use Wix to HTML / Code conversion
Convert Wix source content into HTML / Code output with route-aware validation.
Route coverage follows the engine-supported path for this source and target.
- Widget parity depends on route coverage and deterministic mappings.
- Preserved structures should still be reviewed before import.
View route