Page builder services  ›  WPBakery WPBakery developer · Legacy sites and clean exits

WPBakery Developer: Keep Your Site Running or Plan the Exit

WPBakery usually arrives bundled with a ThemeForest theme and is inherited far more often than chosen. We keep those sites updated, secure, and working, and when upkeep starts costing more than a rebuild, we plan the move properly.

✓  Legacy sites welcome ✓  Tested on staging ✓  Honest keep-or-leave advice
Inherited WPBakery? Answer three questions
1
Is your theme still being updated? If the theme author has stopped releasing updates, the bundled WPBakery stops updating too.
2
Does WPBakery update, or show a licence notice? Bundled copies usually update only through theme updates, not on their own.
3
Which PHP version is the site on? Old themes often pin sites to PHP versions hosts are retiring.
Two or more worrying answers? The site needs attention before something breaks.
Why WPBakery sites break

Three causes behind most WPBakery problems

The builder itself is rarely the fault. The trouble comes from how it arrived on the site.

01

The bundled licence

A copy bundled with a theme usually updates only when the theme updates. If the theme is abandoned, WPBakery quietly falls behind, and direct updates and support need your own licence.

02

Theme updates that scatter layouts

The theme and its bundled builder version move together. An update to one without the other is the classic cause of rows, columns, and elements shifting overnight.

03

An old PHP version

Older themes and builder versions can break on the newer PHP versions hosts move sites to, which is why some sites are stuck on PHP versions that no longer get security fixes.

The real decision

Keep it running, or plan the exit?

Both are legitimate. The right one depends on the site, not on which option earns a developer more.

Keep it running Plan the exit Best when The site works, earns money, and a redesign is at least a year away Upkeep is growing, the theme is abandoned, or a redesign is due anyway Cost now Low: updates, fixes, and a PHP compatibility check Higher: pages are rebuilt, because shortcodes do not convert cleanly Risk Grows over time if the theme stays abandoned Front-loaded, and handled on staging with a URL map What we do Update safely on staging, repair layouts, keep PHP current Plan the new build, map every URL, rebuild, redirect, launch
What we check first

The WPBakery health check

Before quoting anything on an inherited WPBakery site, we check the same five things. Together they tell you whether keeping it is cheap, or whether the exit is closer than it looks.

Leaving? Our guide to redesigning without losing SEO covers keeping your rankings through the move.

1

Theme status: when it was last updated, and whether the author still supports it

2

Builder version: how far behind the bundled WPBakery is

3

PHP version: what the site runs on, and what it will break on

4

Shortcode spread: how many pages depend on WPBakery layouts

5

Custom elements: theme-specific elements that exist nowhere else

What it costs

How much does WPBakery work cost?

Two ways to work, both with the same team.

Hourly By the hour

Updates, repairs, and keeping a legacy site safe. No minimum engagement.

Fixed price Per project

Health checks, PHP upgrades, and planned exits, quoted against a written scope.

The rate or fixed price is confirmed in writing before any work starts. Our guide to what it costs to fix a WordPress website explains why the same job quotes so differently across the market.

How it runs

How WPBakery work runs

Every change is rehearsed on a staging copy first.

1

Send the site

A URL and what is wrong, or just "we inherited this".

2

Health check

Theme, builder, PHP, and shortcode spread, written up plainly.

3

Keep or exit

You choose, with the costs of both paths in front of you.

4

Work on staging

Updates, fixes, or the rebuild, tested before anything goes live.

For agencies

White label WPBakery work

Survyc is an AI-first digital agency. We deliver WPBakery work white label for agencies, with an NDA signed before any client material changes hands and no contact with your client.

Questions we get

Common questions about WPBakery sites

Why is WPBakery not updating on my site?

Most likely it came bundled with your theme. Bundled copies usually update only when the theme releases an update, so an abandoned theme leaves WPBakery behind too. Direct updates and support from WPBakery need a licence of your own, which is worth checking before anything else.

Why did my WPBakery layout break after an update?

Usually the theme and the bundled builder moved out of step, or a PHP upgrade exposed old code. The layout data is normally still there. We restore a working combination on staging, then update both in the right order so the layout holds.

Should I move away from WPBakery?

Not automatically. If the site works and a redesign is at least a year away, keeping it updated and secure is usually cheaper. Moving makes sense when the theme is abandoned, upkeep keeps growing, or you are redesigning anyway, because pages have to be rebuilt either way.

What happens to my content if WPBakery is removed?

Your text stays, but it is wrapped in shortcodes like [vc_row] and [vc_column], so pages show raw code instead of a layout. That is why leaving WPBakery means rebuilding pages rather than converting them, and why the move needs a plan and a URL map.

How much does WPBakery work cost?

Maintenance and repairs can run hourly or as a fixed price per job. A move away from WPBakery is quoted as a fixed project after the health check, because the cost depends mostly on how many pages rely on WPBakery layouts.

Free build review

Inherited a WPBakery site?

Send the URL. You will get back the health check: what state the theme and builder are in, what it will cost to keep running, and whether the exit is closer than it looks.

Get a free build review

Reply within one working day. No obligation.
Thanks. We have your request and will reply within one business day.

Get an Expert