Update WordPress and PHP on a site that's fallen behind
A site that's fallen behind, brought up to date without breaking it.
If you're wondering how to update an old WordPress site that nobody has touched for months or years, you're in the right place. Core, theme and plugins many versions behind, a hosting provider warning that PHP 7.x is being retired, the Site Health screen flagging an outdated PHP version: these are common situations, and they can be fixed. We handle WordPress updates on sites that have fallen behind and the WordPress PHP upgrade with a clear method: a test copy first, then the real site.
The risks of an out-of-date site
Security fixes for plugins, themes and core come out all the time. A site that's been left alone has missed all of them, and known holes are hunted automatically by bots scanning the web day and night: you don't need to be an interesting target, just to have the wrong plugin in the wrong version. The usual results are malware, spam pages indexed on Google and unknown admin users.
Then there's PHP. Unsupported versions no longer receive fixes, and sooner or later the hosting provider switches them off: if the site isn't ready for the new version, that's the day it stops working, even if the warning went unnoticed.
Why updating everything at once on the live site is risky
The "Update all" button makes core and plugins jump several versions in one go. On a site left for years, it's likely something is no longer compatible: a plugin using functions that have been removed, a theme that can't cope with the new editor, a premium extension that won't update because its licence has expired. The result can be a blank page or a "critical error" on the site your customers see, with no idea which update caused it. If that's already happened, there's a dedicated page for a WordPress site that's down.
How we do it, step by step
- Full backup of files and database, stored off the site, and a test copy (staging) identical to the real one.
- Inventory: versions of core, theme, plugins and PHP, abandoned plugins, expired licences, changes made directly to the theme.
- Updating the copy in a compatible order: for very old sites, where needed, we go in stages, through intermediate versions rather than straight to the latest.
- Checking the main pages and features: contact forms, members' areas, basket and checkout if there's a shop, plus the PHP error log.
- Deploying the verified version to the real site, at an agreed time.
- Rolling back to the previous version from the backup if something isn't right, with no improvising.
At the end you get a summary of what was updated, what was replaced and what still needs watching.
PHP: why and how to upgrade it
A WordPress PHP upgrade isn't only about security: recent versions are also generally faster. Today versions 7.x, 8.0 and 8.1 are out of support and 8.2 only receives security fixes until the end of 2026; WordPress recommends PHP 8.3 or later. Before switching, we test the site, theme and plugins on the copy with the new PHP, check errors and warnings, and only then change the version on the hosting or server. If the code isn't compatible, we tell you what needs fixing and what it costs, before doing it.
Prices and what's not included
- Updating a WordPress site that's fallen behind: from €199.
- WooCommerce and PrestaShop: €249, because basket, payments and shipping need more checks. For PrestaShop this applies within the same version; moving to version 9 is a separate job: PrestaShop 9 upgrade.
- PHP version upgrade: €149, with a compatibility check on a copy.
- Joomla, Drupal and Magento: free quote.
Not included are renewing premium plugin licences and the development needed when a plugin has been abandoned or the theme was modified without a child theme. In those cases we stop and give you a quote first, hourly (€75/hour) or with hour packages. Details of all fixed-price jobs are on the pricing page.
A typical case
A brochure site on WordPress untouched for four years, running PHP 7.4, with the hosting provider announcing that version is being switched off. The test copy reveals an unmaintained forms plugin and a theme edited directly. Core is updated in stages, the plugin is replaced with an actively maintained one, the changes are moved into a child theme (quoted and approved beforehand) and the site moves to a supported PHP version. The real site is switched over in a few minutes, with the backup ready in case of problems.
Who it's for
- Businesses and professionals with a WordPress site nobody has updated since it was handed over.
- Anyone who's had the hosting warning about PHP 7.x being retired, or sees the alert on the Site Health screen.
- WooCommerce shops that can't afford to block orders and payments.
- Anyone who's inherited a site from a provider who no longer replies.
How we work
We start with a check of the site to understand versions, plugins and risks; that gives you a clear price before we touch anything. We work Monday to Friday, 09:00-18:00, and quotes are free. To avoid falling behind again there's monthly CMS maintenance, from €49/month; if you're after broader support covering hosting, performance and security, it's all on the WordPress support page.
Frequently asked questions
Why not just update everything with one click from the dashboard?
On a site updated recently, it often works. On a site left untouched for months or years, updating everything at once on the live site means jumping many versions in one go: if a plugin is no longer compatible the site can crash, and it's unclear which of twenty updates caused it. That's why we work on a copy, one step at a time.
Which PHP version do I need?
One still supported by the PHP developers: today versions 7.x, 8.0 and 8.1 no longer receive security fixes, and 8.2 stops at the end of 2026. WordPress recommends PHP 8.3 or later. The right version for your site also depends on the theme and plugins: we choose it after testing them on the copy.
What happens to premium plugins whose licence has expired?
Without an active licence you usually can't download updates. We tell you which ones they are and what renewing would cost; if a plugin is no longer worth it, we look at an alternative together. We don't install "nulled" copies or downloads from unofficial sites: they're one of the most common ways malware gets in.
What if a plugin has been abandoned or the theme was modified?
Those are the cases where updating isn't enough and development is needed: replacing the plugin, fixing its code or moving the theme changes into a child theme. We stop, explain what we found and give you a quote before going ahead, either hourly (€75/hour) or with an hour package.
Will the site be offline during the update?
Almost never. The heavy lifting happens on the test copy; on the real site we only deploy the version we've already verified, usually in a few minutes and at an agreed time. For an online shop we pick a quiet moment for orders.
How much does it cost?
Updating a WordPress site that's fallen behind starts from €199; WooCommerce and PrestaShop €249 (for PrestaShop within the same version: the upgrade to version 9 costs €600). Moving to a supported PHP version costs €149. Joomla, Drupal and Magento are quoted individually, and quotes are free.
How do I avoid falling behind again?
With regular updates instead of one every few years. Monthly CMS maintenance starts from €49/month and includes tested updates, backups and checks: small, frequent steps are far less risky than one big leap.
Other fixed-price fixes
Need a hand with your infrastructure?
Tell us the problem: we reply with a clear plan and a quote.