A conservative sorter.
Anything the engine does not recognise goes to review with a plain reason.
MOVE · MIGRATION · HOW IT WORKS
What converts.
What each part of a WordPress site becomes in Praxis, and how far each one goes, read from the engine as of October 2026. Native means native: pages become sections and fields you edit, not a copy of the old HTML. Where a part cannot be rebuilt without losing words, it is kept as it was and held for a person's review.
What becomes what
How to read this
- "Converted" means it becomes native Praxis content you edit. "Converted in part" means the structure comes and a person finishes the rest, with every gap named. "Carried as a record" means the data is kept, without the plugin's behaviour. "Named, not converted" means it does not come, and it is listed by name before you switch.
- "Compared to the eye" means our engineers have checked the migrated pages against the originals, whole page, on test sites of our own. Elementor and the WordPress block editor are compared this way.
- How much of your site the engine reaches depends on the way in; see "Four ways in".
Page builders
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| Elementor | Native rows holding headings, text, images, buttons, galleries, icons, questions and answers, stats, ratings, testimonials, lists, social icons and video, with their spacing, backgrounds and values for each screen width | Converted in part: our most complete builder, compared to the eye on our own test sites |
| Elementor Pro, and widgets the engine does not know | A "platform gap" finding that names every setting | Named, not converted |
| The WordPress block editor (Gutenberg) | Native sections and rows for pages; native rich text for posts | Converted in part, compared to the eye on a test site of our own |
| Beaver Builder | Native rows at Beaver's own breakpoints, with every page marked for review | Converted in part |
| Divi, WPBakery | Each page's rows and common modules | Converted in part: the structure, and our engineers finish the design by hand |
| Spectra, Brizy, classic HTML | Sections built from the page's structure, kept only when no words are lost | Converted in part |
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| Posts, pages and their hierarchy; custom post types | Native collections with their nested addresses, all as drafts; a custom type becomes a collection after "Import as collection" | Converted |
| Categories, tags and custom taxonomies | Native taxonomies and their terms | Converted |
| Menus | Native menus; a menu with the same name replaces the live one | Converted |
| Comments | Threaded native comments | Converted |
| Authors and user accounts | Bylines, and accounts kept as unclaimed rows with no passwords | Converted; passwords never move |
| A multisite network | Each site of the network becomes its own Praxis site, with its own database | Converted, site by site |
| Old addresses, and Redirection plugin rules | Native redirects, live at import where possible; the rest become review items | Converted; Redirection rules come across through the exporter |
Plugin data
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| ACF and SCF custom fields | Typed native fields; repeaters and flexible content as structured data; galleries and relationships linked | Converted, proven on SCF, the free fork of ACF |
| Contact Form 7, Gravity Forms, WPForms, Ninja Forms, SureForms | Native forms with 11 kinds of field and their notifications | Converted |
| Yoast, Rank Math, SEOPress, All in One SEO | A native search record for each item: title, description, canonical address, robots settings and social cards | Converted; All in One SEO 4 and later keeps data an export file cannot carry, so it comes through a fuller way in |
| Booking and event plugin tables, Jetpack, other plugins | Private records, or a named list of what the plugin held | Carried as a record |
| Shopify Buy Buttons on WordPress pages | A native Shopify product section, and a review item | Converted |
Commerce
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| WooCommerce | Products, variations, categories, coupons, tax and shipping in Praxis's own tables; orders, including WooCommerce's newer order storage, as history | Converted; a moved store runs on Praxis's own checkout, and our engineers scope and test every store move with you |
Translations
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| WPML, Polylang | Native translation groups for posts; WPML through the exporter | Converted in part, into the English and Spanish versions a Praxis page can carry |
The look and the media
| In WordPress | In Praxis | How far it goes |
|---|---|---|
| The site's look | A browser measures your live pages' colours, fonts, sizes and widths into a native theme, and makes it active | Converted in part, measured by a browser in our jobs service |
| Media | Every file checked for status, type, size and a SHA-256 checksum, duplicates merged, stored on Cloudflare R2; through the exporter, each file is checked against your site's own checksum, and a mismatch blocks the cutover | Converted |
How the look is checked
- The original page and the migrated page open in the same browser. The comparison reads the whole page's pixels and every visible element's position and style.
- The full run covers six widths, from 390 to 1920 pixels, at two pixel densities.
- It runs every night against our own test sites. On a customer's import, our operators start it.
- The bar is whole-page likeness: to the eye, you could not tell the two apart.
How nothing is lost in silence
Every page accounted for.
Each page states how many of its source constructs were answered, and how many were mapped and how many named.
Loss counted by class.
A record of loss for each class, a list of every plugin and what it held, and a coverage report.
Safe to switch, only at zero.
"Safe to turn off the source" needs every class of loss at zero, and the cutover receipt runs 11 checks.
Every word, or the original.
For Spectra, Brizy and classic HTML pages, a conversion is kept only when no words are lost.
A promise in print.
"The migration is the site: plugin data is absorbed natively, plugin software does not come, and no loss is silent."
Common questions
My site is built with Divi. Will it look the same?
The engine brings Divi pages across as structure: rows and common modules. Our engineers finish the design by hand, and you compare every page before you switch.
What about a builder that is not on this page?
The scan recognises Elementor, Divi, WPBakery, Beaver Builder and the block editor. For any other builder, our engineers look at your site with you and scope the move as a project of its own. The engine is built for WordPress, and sites on other platforms are moved by our engineers the same way.
Do my custom fields come across?
ACF and SCF fields become typed native fields, with repeaters and flexible content kept as structured data.
Is anything from my plugins lost without a word?
No. What could not come is named before you switch, page by page and class by class.