Laravel apps upgraded, taken over and kept current.
Laravel 11 security fixes ended on 12 March 2026, and Laravel 12 gets them only until 24 February 2027. We move Laravel applications to Laravel 13, take over apps whose developer has left and keep them patched every month, with tests in place first and one fixed price.
Why now
Laravel 12 is in its last months
Bug fixes ended on 13 August 2026. Security fixes end on 24 February 2027.
Laravel 11 and older are out of support
Security fixes for Laravel 11 ended on 12 March 2026, for Laravel 10 on 4 February 2025. Occasional backports still appear, but you cannot plan on them.
PHP 8.2 support runs out
No security fixes from php.net after 31 December 2026. Laravel 13 needs PHP 8.3 or newer.
Nobody knows the code anymore
The developer or agency that built the app has moved on, and every change takes longer than it should.
The dates that matter
| Version | What ends | When |
|---|---|---|
| Laravel 13 | bug fixes | Q3 2027 |
| Laravel 13 | security fixes | 17 March 2028 |
| Laravel 12 | security fixes | 24 February 2027 |
| Laravel 11 | security fixes (ended) | 12 March 2026 |
| PHP 8.2 | security fixes | 31 December 2026 |
When an automated upgrade is not enough
Laravel Shift automates the mechanical part of a Laravel upgrade: for each version it opens a pull request with the changes and comments on what needs a closer look. For an app with good tests and few versions to go, that can be most of the work.
We take the cases where it is not enough:
- Your own packages, and forks of abandoned ones, which no upgrade tool knows.
- No tests, so nobody can say whether the upgraded app still does what it did. We write characterization tests on the critical paths first.
- Several major versions at once, for example Laravel 6 to 13. Each Laravel version supports only a range of PHP versions, so PHP has to move between the steps.
- An old PHP on the server, so the runtime, its extensions and the deployment move together with the framework.
Laravel is built on Symfony components (HttpFoundation, HttpKernel, Console, Routing and more), so our Symfony work covers the layer underneath.
Typical paths
| From | To | How |
|---|---|---|
| Laravel 5–9 | Laravel 13 | One major version at a time, PHP raised between the steps, the tests run after each one. |
| Laravel 10–12 | Laravel 13 | Fewer steps. composer why-not laravel/framework 13.0 shows which packages hold the upgrade back. |
| PHP 7.x, 8.0–8.2 | PHP 8.4 or 8.5 | Rector for the mechanical changes, PHPStan with Larastan to find what is left, an engineer for the rest. |
Upgrade, takeover, care
-
Upgrades
Laravel and PHP to supported versions at a fixed price, one version at a time. How an upgrade runs.
-
Takeover
When the developer or agency has left: access, documentation, tests on the critical paths and a runbook, so the app can be maintained again. Takeover.
-
Care
Monthly Laravel and package updates,
composer audit, monitoring and fixes, so the next upgrade stays small. Care.
How it runs
01
Code Audit
We measure the gap: PHPStan with Larastan, a Rector dry run,
composer outdatedandcomposer audit, plus a read-through of the code.02
Fixed price
You get the scope, the steps, the schedule and one price before we start.
03
Tests first
Characterization tests on the critical paths, and CI that runs them on every change.
04
One version at a time
Each step is a merge request you can review. The details: how an upgrade runs.
Laravel questions
Why not just run Laravel Shift?
Run it where it fits: it does the mechanical changes well. It does not know your own packages, it cannot write the tests your app does not have, and it does not move the PHP on your server. When your app needs those, that is the part we take on.
Can we stay on Laravel 12 for now?
For a while. Laravel 12 gets security fixes until 24 February 2027, but its bug fixes ended on 13 August 2026. Plan the move to Laravel 13 before then; it needs PHP 8.3 or newer.
Do you have Laravel case studies?
Not on this site. Laravel is part of the stack we work with today (Experience), and it runs on the Symfony components we know well. Before you commit, a Code Audit shows whether our approach fits your app.
Our Laravel app was built by someone else. Is that a problem?
No, most of our work is exactly that. When nobody knows the app anymore, a Takeover comes first.
What does it cost?
Upgrades from €3,000. The fixed price for your app comes in the quote after the Code Audit.
Find out what your Laravel upgrade involves
Send us your composer.json and your PHP version. Free first look: we reply with the first step and its fixed price.