Beaver Builder to Astro: a practical migration guide

Moving a Beaver Builder site to Astro means replacing the code that presents your website, while keeping useful content, the design you like, and WordPress for editing. Astro is a framework developers use to build public pages from reusable components and the content those pages need.

With Beaver, the important first step is understanding which layer does each job. The page builder, the active WordPress theme, and Beaver Themer can all contribute to the same URL. Once you’ve separated them, the migration becomes a set of identifiable pieces of work.

This guide follows those pieces through content recovery, design, publishing, and launch. It also covers the ownership and caching questions that often prompt a rebuild conversation in the first place.

Separate Beaver Builder, the theme, and Themer

Open a service page, a blog post, and an archive. For each, identify who supplies the header, main content, sidebar, and footer. Check Plugins > Installed Plugins for Beaver Builder, Beaver Themer, and add-ons, then Appearance > Themes for the active theme and any child theme.

Beaver Builder usually handles the content area. The active theme supplies the surrounding structure, unless another template system replaces it. Beaver Themer can control site parts and templates, including singular pages and archives. Beaver’s layout overview explains how the content area and theme fit together.

A Beaver Builder installation doesn’t establish that the site uses Beaver Builder Theme or Themer. Record the actual arrangement, including custom code in a child theme. That code may register a content type or connect a form even if its filename makes it look like presentation work.

Use a few real URLs to prove the map. A header that changes only on campaign pages is an exception worth finding before the developer estimates one universal header.

Decide whether a rebuild solves your problem

Astro is useful when you want the public templates maintained separately from the visual builder. Your developer can control what each page loads, reuse layout components, and keep everyday edits focused on content. Prebuilt pages can serve the latest successful deployment without asking WordPress to generate each visitor request.

Those benefits come from the implementation. An embedded calendar, video background, or analytics script still has a cost. Keeping WordPress means retaining its hosting, updates, backups, and any plugins that still do useful work.

Beaver is also a maintained product with its own reusable design features. For example, its 2.10 changelog records the introduction of Components with selected settings editable per instance. Don’t sell a rebuild on the assumption that the existing builder has no way to share layouts or defaults.

Compare the tasks your team needs. If editors regularly invent new layouts, retaining or improving their current builder may fit. If they mostly update service details, articles, and staff profiles, WordPress fields with maintained Astro templates can provide a clearer workflow.

If Beaver Builder changes are not showing

Confirm that the change was published, then compare the saved content with the logged-out page. Text that hasn’t changed and styling that hasn’t changed can point to different causes.

Beaver’s cache documentation describes generated CSS and JavaScript in wp-content/uploads/bb-plugin/cache. It also covers clearing the builder cache. Browser, optimization-plugin, hosting, and CDN caches can add other layers. Use the controls for the system actually serving the stale response.

The documented control is Settings > Beaver Builder > Tools > Clear Cache. Beaver’s Tools tab reference also lists integrations with caches such as WP Super Cache, W3 Total Cache, and Cloudflare. Record which layers the site actually uses and change one at a time, then reopen the published URL while logged out. On multisite, the Network Admin’s Clear Cache control applies across the network, so account for that scope before using it.

If the problem began after an update, record versions and follow the vendor’s upgrade troubleshooting on staging. A stale page isn’t enough evidence for a rebuild. Recurring publication failures, unclear responsibilities, or a workflow your team can’t maintain may justify a broader change.

Can you remove Beaver Builder and keep the content?

Beaver documents a useful fallback: deactivating or deleting the plugin through the Plugins screen leaves a simplified HTML version of the layout available in the native WordPress editor and retains layout metadata. The documentation distinguishes this from its settings-level uninstall, which also clears settings and cache. See the current deactivation and uninstall guidance.

That is a content-recovery route, not a finished Astro migration. Check the fallback on a staging copy using the installed version and modules. Compare headings, links, media, lists, downloads, and the order of sections. A contact form or dynamic listing needs more than recovered text.

Keep a complete database and file backup before experimenting. The documented layout metadata includes _fl_builder_data and _fl_builder_draft; preserve that source while assessing conversion options. There is no need to wipe it to begin building the replacement.

For pages needing a richer content model, inspect the saved layout and map its values deliberately. A service introduction, a benefits list, and an inquiry panel are more useful editing concepts than an unlabelled sequence of rows. Ordinary WordPress posts may already have an appropriate structure and need much less transformation.

An export or HTML fallback can help recover information. It doesn’t automatically recreate Themer rules, shared defaults, custom module behavior, or the new publishing connection.

Map Themer templates and field connections to Astro

For every Themer layout, write down three things: where it applies, what it displays, and where that content comes from. Include exclusions and page-level overrides.

Themer’s Singular layout documentation describes field-connected modules for post details and a Post Content module that can draw from either the WordPress editor or a Beaver Builder layout. It also documents how a page’s Beaver layout can override a Singular Themer layout. Seeing a Themer template in the dashboard doesn’t prove every expected page uses it.

Consider an illustrative service site: most services share one Singular template, but a campaign page uses a different layout and omits the normal enquiry sidebar. In Astro, the shared template can become a service layout, the service fields can stay in WordPress, and the campaign exception can select a separate layout. The location rule and the content need separate mappings.

Review global content too. A centrally edited phone number should still have one source. A repeated service card may share its design while allowing its heading and image to vary. Agree which values are global and which are local before reproducing the current controls.

For archives and post grids, record the query as well as the appearance: content type, taxonomy filters, sort order, pagination, and empty results. A screenshot shows only one set of records. Test the rule with a new post and with no matching content.

Preserve the design and replace working features

The existing website can serve as the design brief. Capture fonts, content widths, spacing, colors, image crops, and responsive behavior. Include open navigation, sticky headers, expanded accordions, and form errors. Keep the source site available so the developer can inspect behavior between the screenshots.

Rebuild shared visual patterns in Astro, then compare representative pages at the same viewport and with the same content. Test long headings and optional fields. Fix shared components before reviewing dozens of instances separately.

List the actual modules supplied by add-ons or custom code. If a form comes from Gravity Forms and is merely displayed within a Beaver layout, replacing Beaver doesn’t replace the form’s backend. Decide how the Astro page will submit to that system, or define a replacement. Check server validation, spam handling, submission storage, notifications, and any CRM connection.

A gallery needs captions and keyboard behavior as well as images. A filter needs working queries and an empty state. Commerce, accounts, memberships, and booking flows need their own integration work within the migration. Keep each retained function tied to a concrete test.

Prove WordPress editing and publishing on one page

Astro can fetch content through WordPress’s REST API or an additional GraphQL integration, as described in the official WordPress integration guide. Custom fields and content types need the appropriate API exposure; private data and credentials should remain private.

Build a representative page early. Have the editor update a heading, replace a photo, add a service, preview a draft, publish, and correct a mistake. Test whether changes to a shared field appear on every intended page.

The WordPress dashboard can remain familiar while layout controls change. Explain which sections editors can rearrange, which templates they can select, and what requires development. Astro doesn’t provide the Beaver Builder canvas automatically.

For a prebuilt site, saving content must trigger a build and successful deployment before the public page changes. Other rendering arrangements need explicit cache rules. Agree preview access, expected publishing delay, failure notifications, and the recovery process. Our editing workflow guide gives the editor’s side of that review.

Make the handover independent of the old agency

Before changing platforms, confirm that your organization can keep the current site running. An administrator login alone doesn’t establish access to the domain, hosting, subscription accounts, or form services.

Use this handover checklist:

• Domain and DNS: the account owner, renewal responsibility, and access to change the public destination.
• WordPress hosting: a usable backup, a demonstrated restore, and access to files and the database.
• Builder and theme accounts: installed versions, who supplies updates, and what continues after the agency’s service ends.
• Custom features: source code, the person maintaining it, and credentials for connected services.
• The Astro replacement: repository ownership, public hosting, deployment access, and a named maintainer.

Confirm the actual subscription arrangement rather than assuming an agency’s account transfers with the website. Resolving these responsibilities may improve the situation even before any rebuild. Carry the same clarity into the new support agreement.

Launch, verify, then retire the old dependencies

Record URL decisions and their test results in the SEO migration inventory. Pair it with the Builder, theme and Themer layer inventory so shared templates and field connections have an owner as well as a destination.

Preserve useful public URLs and explicitly redirect any that change. Check titles, descriptions, canonicals, social images, structured data, and sitemap entries in Astro’s output. Settings stored in a WordPress SEO plugin need to reach the new templates; their presence in the dashboard isn’t enough.

Before switching traffic, compare important pages on mobile, test navigation with a keyboard, submit forms, and publish a real content change. Measure performance with the actual images, embeds, and tracking included. Keep the previous deployment recoverable, with a final content sync and rollback procedure agreed.

Deactivate Beaver Builder and Themer on staging only after the replacement no longer needs them for rendering, API content, or feature processing. Review the theme separately, because it may contain backend functions that still matter. Keep WordPress, the remaining plugins, and the Astro project maintained after launch.

For a scope discussion, send us your site URL and the part you want to stop wrestling with. If you know whether it uses Themer or a custom child theme, include that too. Our WordPress-to-Astro service covers the public rebuild and its connection to WordPress; the layer inventory helps establish what your particular move requires.

Still gathering requirements? The portable project brief helps you name the editing tasks and ownership you expect at handover. The cost worksheet keeps implementation and ongoing care separate when comparing quotes.