Migration · Guide collection
WordPress Page Builder to Astro Guides
Choose your WordPress page builder to find one complete Astro migration guide: Elementor, Beaver Builder, Divi, or WPBakery.
On this page
At a glance
- Choose the builder your site uses. Each guide covers its migration in one place.
- Content, design, editing, and working features need a plan; the builder-specific guide explains what to inspect.
Moving a WordPress page builder site to Astro starts with the builder you already use. Your text, images, domain, and a design you like can provide the foundation. The layouts and features need a new implementation, and WordPress can remain the place your team edits.
Choose your builder below. Each guide covers its migration in one place, including content recovery, design, working features, editing, and launch.
Choose your migration guide
| Your builder | Complete guide | The source-specific work to understand |
|---|---|---|
| Elementor | Elementor to Astro | Exports and widget data, Theme Builder, design preservation, and form actions |
| Beaver Builder | Beaver Builder to Astro | Content fallback, the theme and Themer layers, field connections, and ownership |
| Divi | Divi to Astro | Divi 4 and 5 content, legacy modules, shared templates, and module mapping |
| WPBakery | WPBakery to Astro | Nested shortcodes, theme-supplied elements, bundled updates, and feature replacement |
If you’re unsure what runs the site, start with WordPress’s Plugins > Installed Plugins and Appearance > Themes. Older WPBakery installations may be described as Visual Composer in agency notes; its guide explains that naming distinction. A site can also use more than one builder, so check representative pages rather than only the homepage.
What does Astro change?
Astro is a framework developers use to build public websites from reusable components. WordPress can supply the content while Astro controls the pages visitors receive. The official WordPress integration guide describes the API connection between them.
This can give your developer more control over layouts and page assets, and give editors a focused set of content controls. It takes a rebuild, content mapping, and a reliable publishing connection. Builder exports don’t automatically become Astro templates.
Your existing design can guide that work. A change of technology doesn’t require a new brand or a different appearance. Each builder guide explains what to capture and which dependencies need closer attention.
When is a move worth considering?
A site with repeated layouts, clear content, and a manageable set of integrations gives the project a useful starting point. Frequent custom page design, complex checkout, accounts, or unusual plugins need more investigation. A targeted repair or builder upgrade may be enough for a team that likes its current workflow.
Compare the required features and ongoing support, including WordPress maintenance and the new public deployment. Measure performance with the real site’s images, forms, tracking, and embeds included. Choosing a framework alone doesn’t establish the result.
For the common editorial questions, read what the next edit should look like. For an overview of retained plugins and features, use our compatibility notes.
Bring the site you want to keep improving
The most useful starting information is the website URL, what already works, and the recurring problem you want to solve. Add a page with a complicated feature if there is one.
Our WordPress-to-Astro service covers the public rebuild and its connection to WordPress. Send us those details when you’re ready to discuss how the work applies to your site.