WordPress page builder converter. Move a page, and see what it costs first.

Migrating a page builder across a whole site

The converter works one document at a time, which is the right unit for judging losses and the wrong unit for planning a migration. Before converting anything, get the whole picture: ask the agent to run list-convertible-documents, then convert-preview on every page that matters, and group the results by how much each page loses. Most sites split into three piles. Pages that come across almost whole can be converted and checked. Pages with a few approximations need a designer's pass after conversion. Pages that lean on forms, loops, dynamic bindings or display conditions are cheaper to rebuild by hand, because those are outside what the converter carries.

Run the previews on staging with both builders active and the source builder's add-ons switched on; a widget whose plugin is inactive reads as not carried, which overstates the loss.

Divi to Elementor and other common routes

• Divi to Elementor: Divi 4 shortcode pages and Divi 5 block pages can both be read, and Elementor can be written as classic or atomic. Divi 4 is never a target, so a Divi 4 site can leave but not arrive.
• Elementor to Gutenberg: the block editor target is queued and finished in a wp-admin tab, so the result is pending until that tab has run it. Plan for someone to have wp-admin open during a batch.
• WPBakery to anything: raw HTML blocks are read, but they stay raw HTML on the target. Expect the most reduced-to-markup items from older WPBakery pages built with add-on elements.
• Breakdance or Oxygen 6 to another builder: both share one reader, so the loss profile is similar for either.
• Anything to or from Mosaic: not supported; that move stays a manual rebuild.

Putting the converted draft live while protecting search traffic

A conversion creates a new draft with its own ID and URL; the original page is untouched and still live. Replacing one with the other is a separate decision, and it is where search traffic is most often lost if it is rushed. These steps reduce that risk; no migration can promise rankings stay where they were. Before swapping, compare SEO titles and descriptions on both posts; on Pro, seo-bulk-get-meta reads them from whichever SEO plugin is active and seo-bulk-update-meta can copy them across in one call of up to 100 posts. Then decide the URL: either move the old page aside and give the draft its slug, or publish the draft at a new URL with a 301 from the old one. redirects-status reports whether GoBuildWP's automatic slug-change redirects are on and which redirect store they write to; without a supported redirect plugin, WordPress's own old-slug fallback does not cover pages.

Keep the source pages as drafts or private until the converted versions have been live through a full crawl, so a rollback is a slug change rather than a rebuild.

A checklist for each converted draft

• Open the draft in the target builder's editor and save it once there; a page that will not open or save is not converted, whatever the report says.
• Read get-conversion-report against the draft and visit every item marked approximated or reduced to markup.
• Compare the draft and the source at phone, tablet and desktop widths. capture-page and compare-captures can score the difference if a wp-admin tab is open for captures.
• Rebuild forms, loops and conditional sections natively; the converter does not carry them.
• Check internal links and anchors, since section IDs from the old builder may not exist on the new page.

What to restyle after conversion

The source builder's stylesheet does not come with the page, so global styling has to exist on the target first. If the site has a saved GoBuildWP Design direction, brand-kit-apply on Pro writes its palette and type stack into the target builder's global colours and typography. That is a site-wide change, outside the new-draft guarantee: it restyles every page already using those globals, needs confirmation, and is best done on staging. Do it before converting: the converter's approximations snap colours to the nearest palette colour, so a palette that already exists on the target gives it the right colours to snap to. Without it, expect values that look close but drift from page to page.