WPBakery fix
Moving Off WPBakery: Block Editor, Another Builder or a Rebuild?
There is no export button. A WPBakery page is a stack of shortcodes in the content field, with its spacing and colors held as generated CSS, and no other editor reads either. Leaving means rebuilding the layouts somewhere else. The useful questions are where, in what order and how much of the old site deserves the trip.
What you are seeing
- A new theme was activated on a test copy and every page turned into brackets
- A converter plugin produced plain text with the headings and buttons missing
- The redesign quote lists every page as a rebuild
- Editors avoid changing pages because the builder is slow or will not load
- The theme that supplied WPBakery has stopped releasing updates
Why it happens on WPBakery
Most common first.
- 1
Layout stored as shortcodes in the content
Rows, columns and elements are saved as nested tags in the same field as your text. The block editor, Elementor and every other builder keep their own formats and read none of this. Whatever the destination, each layout is rebuilt in the new tool, by hand or by a script written for that site.
- 2
Words kept inside the tags
Text blocks hold their words between tags, but headings, buttons and many other elements store theirs as attributes within the tag itself. Strip the shortcodes and those words are deleted with them. Raw HTML elements go further and store their content in an encoded form no person can read.
- 3
Design that only the builder prints
Spacing, borders and backgrounds set in an element's Design Options are written as generated CSS under class names beginning vc_custom, held with the page and printed by WPBakery when the page loads. Without the builder nothing prints it. The new system receives the content and none of that styling.
- 4
Images referenced by number
An image element records the media library ID of its picture, not the file's address. A migration has to look up each ID and place the real image in the new layout. Skip that and the new pages arrive with their text and none of their photographs.
- 5
Elements only your theme provides
Portfolio grids, sliders, team rows and pricing tables often come from the theme, not from WPBakery. They have no equivalent to map to. Each one needs a decision: rebuild it, replace it with something simpler or drop it.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Count what is actually built with the builder
List every page and post, then mark which contain vc_ tags. Blog posts are frequently plain text and move untouched. Record the element types in use and how many pages use each, because twenty pages sharing three layouts is a different project from twenty one-off designs.
- 2
Choose the destination by what the site must do next
The block editor with a maintained theme suits content sites that want to stay on WordPress with fewer moving parts. Another builder keeps drag-and-drop editing and renews the dependency under a different name. A rebuild off WordPress suits a site where speed, security or upkeep are complaints of their own.
- 3
Fix the addresses before touching a layout
Export the full list of URLs with their titles and meta descriptions. Keep every slug you can. Where one must change, write the redirect down now, in a sheet, before any page is rebuilt.
- 4
Rebuild templates first, then pages by traffic
Start with the shared parts: the header, the footer and the two or three page types that cover most of the site. Then rebuild individual pages in order of the visits and enquiries they bring. Low-traffic pages with dated content are candidates for merging or retiring, not for faithful reproduction.
- 5
Keep WPBakery running until the last page is across
On a staging copy, convert pages one at a time and leave the builder active so unconverted pages still render. Replace the page content with the new layout, check the images and forms and move on. The work can then be done in phases without a week of broken pages.
- 6
Search for leftovers, then remove the builder
Before deactivating js_composer, search the database for [vc_ in posts, widgets and theme options. Clear what remains, then deactivate the builder and the theme's companion plugins on staging and click through every template. Only then repeat it on the live site and test the redirects.
Keep it from coming back
- Whatever you move to, keep content in standard fields or core blocks where you can
- Avoid elements that exist only in one theme or one add-on pack
- Keep the URL map and the redirect sheet with the site's records
- Ask of any new tool what the pages look like with it switched off
The permanent fix
A faster Next.js build, with a CMS made for your business
A migration is the one moment when every page is being touched anyway, which makes it the cheapest time to ask whether the next system should be another builder. Moving to a different builder trades one private format for another. A Next.js build with a custom CMS stores each page as plain fields, such as a heading, a paragraph and an image, renders them as static files and leaves nothing for a future theme change to strand.
| On WPBakery today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your WPBakery site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Tools exist that attempt it, and results vary with how the pages were built. Simple text-and-image layouts can come across usable. Theme-made elements, Design Options styling and nested rows generally do not. Test any converter on a staging copy with your most complicated page, not your simplest.
No. Elementor stores layouts in its own format and does not read WPBakery's tags. The text can be copied across, and the layouts are built again in the new builder. It is a real option if your team wants visual editing, as long as you accept that the next exit will look like this one.
Yes, and for larger sites it should. With WPBakery left active, converted and unconverted pages can sit side by side. Work proceeds on staging in batches and each batch goes live once it is checked. The builder comes out only when a database search finds no tags left.
Often not. Many sites used the builder for pages and wrote posts in the ordinary editor, and those posts move as they are. Check a sample for vc_ tags first. Posts that did use the builder usually hold a single text block and are quick to clean.
Keep reading
- ServiceWebsite Migration ServicesMove off WordPress, a page builder, an e-commerce platform or a slow host without losing rankings, forms or tracking — inventoried, redirected, watched.
- ServiceReplacing WordPressWhen WordPress becomes the thing you fight instead of the thing that works, it's time to move. We migrate you without losing rankings.
- ServiceCMS DevelopmentGive your team a cleaner way to publish. We build content systems with clear templates, safe editing fields, reusable blocks, and SEO structure that survives the next update.