UK businesses running legacy PHP should modernise in phases: audit the system, add automated tests, upgrade to a supported PHP 8 release, re-platform to modern hosting, then migrate the parts that change most into Laravel. With PHP 8.1 already unsupported and PHP 8.2 reaching end of life on 31 December 2026, the first two phases are urgent for most firms; the later ones can be planned around budget.
Why 2026 is the year to act
PHP 8.1 stopped receiving security fixes at the end of 2025, and PHP 8.2 follows on 31 December 2026. Unsupported versions are a frequent finding in penetration tests, Cyber Essentials preparation and enterprise supplier audits, and they make it harder to recruit developers who want to work on current tools.
The roadmap
Durations are indicative for a small to medium application; large or untested codebases take longer.
| Phase | What happens | Typical duration |
|---|---|---|
| 1. Audit | Inventory PHP and package versions, hosting, integrations and personal data flows | 1–2 weeks |
| 2. Safety net | Automated tests around the journeys customers and staff rely on | 1–3 weeks |
| 3. Upgrade | Move to a supported PHP 8 release with Rector, static analysis and manual fixes | 2–6 weeks |
| 4. Re-platform | Containers, CI/CD, backups and monitoring on UK or EU cloud hosting | 1–3 weeks |
| 5. Laravel migration | Move the most frequently changed modules into Laravel, one at a time | Ongoing, in phases |
UK-specific checks
- UK GDPR: map which personal data the system holds and make sure test data is anonymised.
- Hosting region: decide whether data must stay in the UK or EU, for example AWS London.
- Supplier requirements: check what your customers' security questionnaires and Cyber Essentials need.
- Contracts: make sure you own the code and credentials after modernisation.
Budgeting
Phases 1–4 for a focused application are often achievable as a single fixed-price project; at Lytnex these start at £12,000. Laravel migration of larger systems is best budgeted per module. Our bespoke software cost guide gives wider UK price ranges.
Common mistakes to avoid
- Starting with a full rewrite instead of upgrading first.
- Changing code before any automated tests exist.
- Adding new features to the system while it is being modernised.
- Leaving the upgrade until after a version is already unsupported.
Frequently asked questions
What is legacy system modernisation?
Updating an ageing system (its language versions, framework, architecture or hosting) so it is secure, maintainable and able to support the business, usually in phases rather than a single rewrite.
Should we upgrade PHP or migrate to Laravel first?
Upgrade PHP first. It removes the security risk fastest; migrating modules into Laravel can then happen gradually.
How long does legacy PHP modernisation take?
The audit, test, upgrade and re-platform phases typically take 5–12 weeks for a small to medium application. Laravel migration continues in phases after that.