Laravel upgrade service: from any version to Laravel 12 and PHP 8.4.
Controlled upgrades of applications that cannot afford to go offline, done by engineers who have upgraded Laravel since version 4 and still maintain systems from 2013.
- Laravel 5 to 12, PHP 7 to 8.4
- One major version at a time, app stays online
- Penetration test after the upgrade
Why upgrade now
Every Laravel and PHP version has a date after which security fixes stop. PHP 8.1 stopped receiving them at the end of 2025, Laravel 10 in early 2025, and the packages your application depends on drop old versions even sooner. An application that cannot be patched is a liability for your customers, your insurer and your auditors.
Security fixes stop
Unpatched framework and PHP versions are the first thing a penetration tester, an auditor or an attacker looks for.
Packages stop working
Payment, PDF, queue and authentication packages require current Laravel versions. Staying behind means forking or freezing them.
Slower and more expensive to change
Modern PHP is faster and Laravel 12 code is shorter. Every feature on an old version costs more than it should.
Hiring and hand-over
Engineers want to work on current versions. An upgraded codebase is easier to staff, review and take over.
How an upgrade runs
-
Step 1
Audit
We read the code, run the tests that exist and list what blocks the upgrade: abandoned packages, raw queries, deprecated APIs. Written report within a week, with a fixed quote.
-
Step 2
Safety net
Tests on the critical paths before we touch them, a staging environment that mirrors production, and a rollback plan.
-
Step 3
One major version at a time
Each step ends with a green test suite and a deployable state. Automated refactoring where it is safe, hands where it is not. The application stays online throughout.
-
Step 4
Hand-over
Penetration test and dependency audit on the result, documentation of what changed, deployment, and a care plan if you want one.
What you get
An upgrade is not only a version number. You get a codebase your team can work in, with the parts that were holding it back replaced or documented.
Current versions
Laravel 12, PHP 8.4, current major versions of every package, Vite for assets.
Tests where there were none
Feature tests for the critical flows, so the next upgrade is routine.
Clean dependency tree
Abandoned packages replaced, forks removed, security advisories clear.
Documentation
What changed, why, and what to watch. Written for the next engineer, not for us.
Questions about upgrades
Will the application stay online during the upgrade?
Yes. Work happens in your repository on a branch and on a staging environment. Each major version is deployed in a planned window with a rollback ready, usually without any visible downtime.
What about packages that no longer exist?
The audit lists them. For each one we propose a replacement, a maintained fork or a small in-house implementation, with the cost in the quote.
Do you upgrade the front-end too?
If you want. Laravel Mix to Vite, Bootstrap or jQuery front-ends to Tailwind and Alpine or Livewire, old Vue versions to current ones. It is quoted as a separate milestone.
Can you maintain it afterwards?
Yes. Most upgrade clients continue on a care plan: monthly security updates, monitoring and an hours bank for small changes.
How long does it take?
A single major version on a mid-sized application takes one to two weeks. Laravel 5 to 12 with PHP 7 to 8.4 typically takes six to ten weeks, with the application live the whole time.
Send us the repository and we will tell you what the upgrade involves.
An audit with a written report and a fixed quote usually takes a week.