Elementor, Divi and other page builders: what survives a website move

The short answer
When you move a site built with Elementor, Divi or another page builder off WordPress, your words, images, page addresses and SEO titles and descriptions can all come with you. The layouts cannot: the sections, columns, styling, sliders, popups and other builder widgets are saved in the builder's own format, and the new site rebuilds them as templates, so every page has to be compared with the old one before anything switches.
- What survives is everything a visitor reads. Text, images, page addresses and the SEO details Google sees belong to your site, not to the builder, and all of them can be carried over and checked.
- What gets rebuilt is everything the builder draws. Layouts, builder shortcodes and saved layout data, dynamic widgets, popups and theme-builder headers and footers only work while the builder runs.
- The proof is a page-by-page comparison. Check words, images, links, forms and SEO details on every address, and look at the important pages side by side on a phone and a desktop.
A page builder does not make a site impossible to move. It makes the move a rebuild of the look and a careful copy of the content, and you should know which part you are paying for.
What survives: text, images, addresses and SEO details
Everything a visitor reads on your pages can come with you. The builder decides how a page looks, but the words, pictures and addresses are yours, and every one of them is visible on the live page, where it can be copied and checked even when the builder's own data cannot be imported.
What it is | Does it survive? | What to watch |
|---|---|---|
Headings and body text | Yes | Text inside tabs, accordions and sliders is hidden until clicked, so it is easy to miss |
Images in the page | Yes | Images set as section backgrounds live in the layout settings, not the content, so they travel with the layout rebuild |
Page addresses | Yes | Addresses are WordPress settings, not builder settings, so each page can keep its address. Anything that changes needs a redirect |
SEO titles and meta descriptions | Yes | They come from your SEO plugin, such as Yoast or Rank Math, not the builder |
Links and buttons | The destinations, yes | A button is a builder widget, so it is redrawn, but where it points is content and must match |
Embedded maps and videos | Yes | They move with the page's content |
Two of these deserve a closer look.
Text in hidden panels. Tabs, accordions and sliders show one piece of text at a time. The rest is on the page but folded away, so a quick look at the old site will not show it. Open every panel when you record what each page says.
Page addresses. On WordPress, a page's address comes from its slug and the site's permalink setting, not from Elementor or Divi. That means a builder page can keep the same address on the new site. EmDash's own guide to porting a theme still ends with "Prepare redirects for every changed permalink before cutover" (EmDash docs), because some addresses do change, and each one needs a redirect.
What gets rebuilt: layouts, builder data, dynamic widgets and popups
Everything the builder draws is rebuilt, because it only works while the builder is running. EmDash, Cloudflare's open-source CMS built on Astro that calls itself "the spiritual successor to WordPress", does not run WordPress plugins, and its documentation says plainly that EmDash "is not a visual page builder" (EmDash docs). On the new site, the design lives in templates.
The reason is how builders save your pages.
- Elementor keeps each page's design in its own data. Its developer documentation says it "stores the page data and layout in a JSON format as WordPress post metadata", and that this data "is saved as a private custom field which is not visible in the WordPress dashboard" (Elementor developer docs). JSON is a structured text format that only Elementor knows how to draw.
- Divi 4 wraps page content in its own shortcodes, short bracketed codes such as
[et_pb_section]that the theme turns into layout. Elegant Themes, Divi's maker, writes that "If you have ever disabled Divi and visited a page you built with the Divi Builder, you would have seen these shortcodes" (Elegant Themes). Divi 5 moved to a storage format that "mimics WordPress's native blocks" (same source), which helps, but the layout still needs Divi to draw it. - Beaver Builder, WPBakery and Avada work the same way in principle: the builder stores the design, and the design stops when the builder does.
EmDash's theme guide names page builders directly: "Builder shortcodes and proprietary JSON usually require a deliberate Portable Text conversion or a redesigned page template" (EmDash docs). Portable Text is the structured format EmDash stores page content in. In plain terms, someone has to decide what each builder section becomes on the new site, either content you can edit or part of a template.
EmDash's importer has the same limit. Its migration guide says the standard export file import "writes the standard imported fields rather than copying every arbitrary meta key" (EmDash docs), and Elementor's layout lives in exactly that kind of hidden field. The guide also says to "Inspect complex blocks, embeds, shortcodes, page-builder markup, and plugin-defined blocks in the rendered EmDash site" (same source).
Here is what that means part by part.
Builder part | What happens on the new site |
|---|---|
Section and column layouts, spacing, fonts and colors | Rebuilt as templates and styles |
Builder shortcodes and saved layout data | Not used. The content inside them is kept, the wrapping is dropped |
Theme-builder headers, footers and page templates (Elementor Pro, Divi Theme Builder) | Rebuilt as the site's shared header, footer and page templates |
Dynamic widgets: post grids, "latest posts" lists, counters, countdowns | Rebuilt so they read from the new site's content |
Sliders, carousels, tabs and accordions | Rebuilt, or turned into plain sections if the extra motion was not doing a job |
Popups and their display rules | Rebuilt, or dropped if nobody needed them. Decide one by one |
Builder form widgets, such as Elementor's form | Rebuilt as a working form, then tested by sending a real message |
Separate phone and desktop versions of a section | Rebuilt once, as a layout that adapts to the screen |
The quiet failure is the dynamic part. EmDash's docs give a close example from WordPress's own editor: blocks that WordPress builds on the fly, such as a Latest Posts list, are imported as code comments that "show no content on the site" (EmDash docs). A builder's posts grid has the same problem. The page loads, nothing errors, and a section is simply empty. Our guide to what happens to your contact form after a website move covers forms in detail.
How to compare your old and new pages
Compare every address on the new site against a record of the old one, made before anything changes, and check the important pages side by side on a phone and a desktop. A builder page that loses a section still looks finished, so the comparison has to be against what the page said before, not against whether it looks fine now. EmDash's porting guide asks for the same: "Compare representative public URLs at mobile and desktop widths" (EmDash docs).
- Record the old site first. List every public address. Save the text of each page with every tab, accordion and slider opened. Take screenshots of the home page and your most important pages at phone and desktop width. Write down every popup, form, slider and listing, and what each one does.
- Compare the words, page by page. Every heading and paragraph should be there. Look for two kinds of leftover: stray codes in square brackets, such as
[et_pb_text], and text that appears twice because the old page had one copy for phones and another for desktops. - Compare the images. The same images, in the same places, with their alt text, the short description that screen readers read aloud. Check section backgrounds by eye, because they are not in the page content.
- Click every link and button. Each one should go where it went before.
- Send a test message through every form. Confirm it arrives where the old one arrived.
- Check the dynamic parts. A latest-posts section should show your latest posts. A listing should list. An empty block of space where something used to be is the most common miss.
- Check the SEO details on every address. The title, meta description and canonical address, the one Google treats as the real version of a page, should match the old page or differ on purpose.
- Look at the pages side by side. Same order, same information, nothing important pushed out of sight on a phone. The new page does not need to be identical to the pixel, but a visitor should find everything they found before.
Keep the old site running until all of this passes. EmDash's docs say to keep the original WordPress site available "until imported media, old URLs, redirects, SEO metadata, forms, and plugin-dependent pages have been verified in the new deployment" (EmDash docs). The website migration SEO checklist covers the rest of the move: the address list, redirects, launch and the 90 days after.
Who should stay on WordPress
If you build and rearrange page layouts yourself every week by dragging and dropping, and that is the part of the site you enjoy, stay on WordPress with your builder. On EmDash you edit words, images and posts in the editor, and the layouts live in templates, so changing a page's structure becomes a small job for someone else.
Stay put as well if:
- The site's main job is builder logic, such as filterable directories, complex popups with conditions, or listings built from many custom fields. Moving it means rebuilding a feature, not just pages.
- It is a store, a member area or an online course. Those are rebuilds of a different kind.
- It works, costs you little and nobody touches it. The builder is not a problem on its own.
If what you want is to be rid of the builder but keep WordPress, that is a smaller job. Converter plugins exist for it, such as Migrate Off Elementor, which says it can "Turn your Elementor pages into the built-in WordPress editor automatically". Check the fit guide if you are unsure which side you are on.
How we handle a page-builder site
The free check spots Elementor, Divi, Beaver Builder and WPBakery on your public pages and ticks the page-builder add-on in your price, so the number you see already includes it. A builder on its own does not make a site a poor fit. The free result leaves plugin and builder names out until you pay the deposit.
The add-on, from our pricing:
- Page-builder layouts rebuilt: $390. For Elementor, Divi and similar. We rebuild the builder's layouts as parts of the new site.
Your current look is included in the move, so the new site can look like the old one.
The conversion itself starts at $790 for up to 25 pages. On every move from WordPress to EmDash, we check every URL, redirect, form, title, description, canonical and schema against your live site, and compare the titles, copy, images and descriptions on each page. You see the result on a private preview while your WordPress site stays live and untouched, approve it, and keep a written way back.
To see where your own site stands, check your site for free.
Frequently asked questions
Will my Elementor content transfer to EmDash?
Your text, images, page addresses and SEO titles and descriptions can all be carried over. Elementor's layouts cannot, because Elementor saves them in its own hidden data that only it can draw. The new site rebuilds the sections, styling and widgets as templates. Compare every page against the old one before launch.
Can I keep my site's design when I leave Elementor or Divi?
Yes, but it is rebuilt rather than copied. The builder's layout data does not run on another platform, so someone recreates the look in the new site's templates. Expect the same colors, fonts and page order, checked side by side on a phone and a desktop, rather than a pixel-perfect copy.
What happens to Divi shortcodes when I leave Divi?
They stop working. Divi 4 wraps page content in codes such as et_pb_section that only Divi can turn into layout, so without Divi they show up as stray text. A careful move keeps the text inside them, drops the codes, and checks every page for leftovers before launch.
Do Elementor popups and forms move with the site?
No. Popups and form widgets only run inside Elementor, so they are rebuilt on the new site. Decide which popups still do a job and drop the rest. Every form needs a test message after the rebuild, sent to the same inbox that received messages before.
Will I lose my Google rankings if I move away from Elementor?
Nobody can promise rankings, but the builder is not what Google ranks. Keep every page address or redirect it, carry over each title and description, keep the same words on each page, and check all of it before launch. A missing section or a broken redirect costs far more than a new layout.
Can I still drag and drop layouts after moving to EmDash?
Not the way a page builder works. EmDash describes itself as not a visual page builder. You edit words, images and posts in its editor, and page layouts live in templates. If rearranging layouts yourself every week matters to you, staying on WordPress with your builder may suit you better.