Skip to content

PHP Version Upgrades

PHP 8.2 receives its last security fixes on 31 December 2026. After that date, a flaw found in PHP itself stays open on every server still running it, and hosting companies start moving customers off it on their own timetable rather than yours.

We upgrade PHP applications that a business depends on: Laravel and Symfony systems, WordPress and WooCommerce sites, and custom code written years ago. The work is done one version at a time, in your repository, with tests around the parts that matter before anything changes.

Support dates

Where each PHP version stands

Dates from php.net, the PHP project's own list of supported versions, checked on 13 November 2026. Security support is the date after which no fixes are released at all.

PHP 7.4, 8.0 and 8.1

Already out of support. No security fixes are released for them. Linux distributions that still ship them may backport some patches to their own packages; check what yours does.

PHP 8.2

Security fixes until 31 December 2026. This is the version most commonly left behind by hosting changes in 2027.

PHP 8.3

Security fixes until 31 December 2027. Upgrading here buys one year.

PHP 8.4 and 8.5

Supported until 31 December 2028 and 31 December 2029. The usual target for an upgrade done now, provided your framework and packages support them.

Scope

What an upgrade covers

A PHP upgrade is rarely only PHP. These are the parts we check and move together.

  • Every Composer package and its supported PHP range, with replacements for abandoned ones
  • The framework, one major version at a time (Laravel, Symfony, CodeIgniter)
  • WordPress plugins and themes, checked against the target version before the switch
  • Deprecations fixed in the code, such as dynamic properties and implicit nullable parameters
  • PHP extensions the server must provide, agreed with whoever runs the hosting
  • Tests written around payments, logins and anything that sends money or documents
  • A staging copy where your team checks the upgraded system before release
  • A written way back for the release itself
Order of work

How an upgrade runs

  1. Inventory

    We read the code and the server: PHP version, framework, every package, extensions, cron jobs and anything that talks to another system. You receive a written list of what blocks the upgrade and what it costs to clear.

  2. A safety net

    Before changing code, we add tests around the paths the business cannot lose. Where tests are impractical, we record how each path behaves today so the upgraded version can be compared.

  3. One step at a time

    Each framework or PHP step is a separate change, reviewed and run on staging, rather than one large jump that is hard to debug.

  4. Your check

    Your team uses the staging copy with real tasks. We fix what they find before release.

  5. Release

    At a time agreed with you, with the previous version ready to return to. We watch errors and logs for the following days.

Judgement

When an upgrade is not the answer

An upgrade suits

  • The application still does what the business needs
  • The framework has an upgrade path to a supported version
  • Someone at your company can tell us what the important tasks are

Something else may suit better

  • The framework is abandoned with no route forward; replacing parts of the system may cost less than forcing it onto new PHP
  • The system is being retired within months; isolating and hardening it may be enough
  • Nobody can say what the system must keep doing; that needs an assessment first
Questions

Common questions

Can we keep running PHP 8.2 after December 2026?

It will keep running, but PHP itself will not fix new security flaws in it. Some Linux distributions patch their own packaged PHP for longer; if you rely on that, confirm it with your hosting provider in writing.

How long does an upgrade take?

It depends on the size of the code, the number of packages and how far behind the framework is. The inventory gives you a range before you commit to the upgrade itself.

Will the site go down?

The upgrade is prepared and checked on staging. The release happens at a time you choose, with the previous version ready to return to, and is normally a short switch rather than an outage.

Do you upgrade WordPress sites too?

Yes. Plugins and themes are the usual blockers, so each one is checked against the target PHP version; abandoned plugins are replaced or their function rebuilt.

Our Laravel version is old as well. Does that change things?

It usually means more steps, not a different method. Our Notes article on upgrading Laravel one major version at a time explains the order we follow.

For enterprise buyers

What your procurement team will ask, answered before the call

  • Your paper or oursNDA, data-processing agreement, master agreement and statement of work.
  • Named peopleThe statement of work names the delivery lead and the escalation contact above them.
  • Your code, your accountsWork is committed to your repository and assigned to you on final payment.
  • Local sales teamsSales teams in the UAE and Singapore; engineering in Rajkot and Ahmedabad, India.
Next step

Tell us your PHP version and framework

The PHP version, the framework and its version, roughly how many people use the system and when your hosting changes, if you know. If you do not know the versions, say so; finding out is the first step of the inventory. You will hear from us within one business day.

Discuss a PHP upgrade

Goes straight to our team on WhatsApp and email. We reply within one business day.