WordPress Development

Moving from the Classic Editor or a Page Builder to WordPress Blocks

Moving from the Classic Editor or a Page Builder to WordPress Blocks

A lot of WordPress sites still use the Classic Editor, either because they were built before the block editor arrived or because someone installed the Classic Editor plugin to avoid change. Others were built with page builders that were popular at the time, and their content is now wrapped in layers of shortcodes and builder-specific markup.

Both situations work, until they don’t. Page builders add weight that slows pages down. Their licences need renewing. Classic content can’t take advantage of patterns, block themes or the editing improvements WordPress has made in recent years. And eventually, someone wants a redesign, and the old content structure gets in the way.

I’ve migrated a number of sites from classic and builder content to blocks. It’s very achievable, but it rewards planning. Here’s how I approach it.

Why migrate at all?

Moving to blocks isn’t mandatory. But common reasons include:

  • Performance. Native blocks typically produce lighter pages than page builders, improving speed and Core Web Vitals.
  • Reduced dependency. No reliance on a third-party builder’s continued development, pricing and compatibility.
  • Better editing. Patterns, reusable layouts and consistent design controls through theme.json.
  • Future compatibility. WordPress development is focused on blocks, from block themes to the Site Editor.
  • Cleaner content. Block content is stored as readable HTML with block comments, which survives theme changes far better than shortcodes.

If your current setup works well and performance is fine, there’s no need to rush. But if you’re planning a redesign, new theme or performance improvements, it’s a natural moment to move.

Step 1: Audit your content

Start by understanding what you have:

  • How many posts and pages are there?
  • Which use the Classic Editor, and which use a page builder?
  • Which shortcodes are used, and by which plugins or themes?
  • Which pages have complex layouts, and which are mostly text?
  • Which pages are most important, by traffic, conversions or business value?

You can search the database for shortcodes and builder markers. WP-CLI helps:

The exact markers depend on the builder. Some builders store layouts in post meta rather than content, so check the builder’s documentation.

Typically, you’ll find a mix:

  • Blog posts that are mostly text and images, easy to convert.
  • Key landing pages with complex builder layouts, which need rebuilding.
  • Pages using shortcodes from plugins, which need replacement.

Step 2: Plan the target setup

Decide what you’re moving to:

  • A block theme or a classic theme with good block support? A lean block theme gives the most benefit.
  • Which custom blocks or patterns will you need to recreate key layouts?
  • Which plugins will replace shortcode functionality, like forms, sliders or tabs?

Build a small library of patterns for the layouts your site uses most: hero sections, feature grids, testimonials, calls to action. Recreating pages becomes much faster when you can assemble them from patterns.

Do all of this on a staging site. Never migrate content directly on production.

Step 3: Convert Classic Editor content

Classic content opens in the block editor inside a single Classic block. The content still displays correctly, but it isn’t broken into individual blocks.

To convert it, select the Classic block and use the “Convert to blocks” option. WordPress turns paragraphs, headings, lists, images and other HTML into the corresponding blocks.

Most simple posts convert cleanly. Watch for:

  • Shortcodes, which become Shortcode blocks and still need their plugin.
  • Custom HTML that doesn’t map neatly to blocks, which becomes Custom HTML blocks.
  • Inline styles from old editors, which may need cleaning.
  • Image alignment and captions, which occasionally need adjusting.

For sites with hundreds of posts, converting each manually is tedious. Some plugins offer bulk conversion of classic content to blocks. Test bulk conversion on staging with a representative sample, then review results before applying it widely.

You don’t have to convert every old post. Classic blocks display fine. Many sites convert only content they actively update, plus important pages, and leave older archives as they are.

Step 4: Deal with shortcodes

Shortcodes are the trickiest part of most migrations. If you deactivate the plugin or theme that provides a shortcode, the raw shortcode text appears on the page, like [contact-form-7 id=”12″] or [button url=”…”].

For each shortcode:

  1. Identify what provides it.
  2. Decide on a replacement: a core block, a block from a plugin, a pattern or a custom block.
  3. Replace instances, manually or with a script for large volumes.

You can find all instances of a shortcode across your content:

Many modern plugins offer blocks that replace their old shortcodes. For theme-specific shortcodes, which disappear when you change themes, you’ll need replacements or a small compatibility plugin that keeps old shortcodes working during the transition.

Step 5: Rebuild page builder layouts

Page builder content usually can’t be converted automatically into clean blocks. Builders store layouts in their own formats: nested shortcodes, custom markup or data in post meta. When the builder is deactivated, pages often show a mess of shortcodes or lose their layout entirely.

For builder pages, the practical approach is rebuilding:

  1. Prioritise pages by importance: homepage, key service pages, landing pages and high-traffic content first.
  2. Rebuild each page with blocks and patterns on staging, keeping the content but improving structure.
  3. Preserve SEO elements: page titles, meta descriptions, headings, image alt text, internal links and URLs.
  4. Compare old and new visually and functionally.

Rebuilding is also an opportunity to improve. Many builder pages have accumulated inconsistent styles and outdated content. Rebuilding with a consistent pattern library often makes pages better, not just lighter.

Some builders offer export tools or have third-party converters to blocks. Results vary widely; test them, but expect manual cleanup.

Step 6: Handle builder content you don’t rebuild

If you have many old builder pages that don’t justify rebuilding, options include:

  • Keep the builder active for those pages during a transition period, while new content uses blocks.
  • Convert to simplified content: extract the text and images into basic blocks, accepting a simpler layout.
  • Remove or merge outdated pages, with redirects.

Running a builder only for legacy pages keeps its scripts loading on those pages, but it gives you time to migrate gradually.

Step 7: Preserve SEO

Content migrations can affect SEO if you’re not careful:

  • Keep URLs unchanged wherever possible.
  • Preserve titles, meta descriptions and structured data.
  • Keep heading structure logical; builders sometimes use heading tags for styling, so fix them during rebuilds.
  • Keep internal links intact.
  • Check images and alt text.
  • Monitor Search Console after the migration for errors and changes in performance.

Faster pages and cleaner HTML often improve performance after a well-executed migration.

Step 8: Test thoroughly

Before switching the live site:

  • Review every important page visually on desktop and mobile.
  • Test forms, buttons, tabs, sliders and any interactive elements.
  • Search content for leftover shortcodes.
  • Run speed tests and compare with the old pages.
  • Check accessibility, including headings and keyboard navigation.

A quick database search for common shortcode patterns, like opening square brackets followed by known shortcode names, helps catch leftovers.

Step 9: Train editors

Editors used to the Classic Editor or a builder need some help adjusting:

  • Show them how to insert blocks and patterns.
  • Explain the block toolbar and settings sidebar.
  • Show them how to create common page types from patterns.
  • Explain any restrictions, like locked patterns or limited colour choices, and why they exist.

A short training session and a reference guide reduce frustration and keep content consistent.

Step 10: Remove what you no longer need

Once everything is migrated and tested:

  • Deactivate and remove the page builder, if no longer used.
  • Remove the Classic Editor plugin.
  • Remove shortcode plugins that have been replaced.
  • Clean up leftover builder data in post meta and options, carefully and with backups.

Removing these reduces maintenance, security exposure and performance overhead.

Frequently asked questions

Will my content be lost if I switch from the Classic Editor?

No. Classic content opens in a Classic block and displays as before. You can convert it to blocks when you’re ready.

Can page builder layouts be converted automatically?

Rarely cleanly. Some tools help, but most builder pages need rebuilding with blocks for good results.

Do I need to convert all old posts?

No. Classic blocks work fine. Focus on important pages and content you’ll update, and convert others gradually or leave them.

What happens to shortcodes when I remove a plugin?

They appear as raw text on the page. Replace them with blocks or keep a compatibility solution before removing the plugin.

Final thoughts

Moving from the Classic Editor or a page builder to blocks is an investment that pays off in speed, maintainability and editing experience. Audit your content, plan your patterns and replacements, convert simple content, rebuild important builder pages, deal with shortcodes carefully, protect your SEO and test everything on staging. Then train editors and remove what you no longer need. Done step by step, the migration is smooth, and the result is a cleaner, faster site.