Laravel upgrade service
We move your Laravel app from any version to the current release, PHP included. The work happens on a separate branch, tested at every step, with a fixed written quote before anything starts.
- Upgrade assessment
- Free
- Upgrade assessment
- Written quote first
- Fixed
- Written quote first
Old versions stop getting fixes
Each Laravel release gets 2 years of security fixes, then nothing. If your app sits below the line, every disclosed bug stays open. See the full reference table.
| Laravel | Status today |
|---|---|
| Laravel 10 | End of life |
| Laravel 11 | End of life |
| Laravel 12 | Security fixes only |
| Laravel 13 | Supported |
| Laravel 9 and older | End of life |
| PHP | Status today |
|---|---|
| 8.2 | Security fixes only |
| 8.3 | Security fixes only |
| 8.4 | Supported |
| 8.5 | Supported |
| 8.1 and older | End of life |
An app on Laravel 9 or older, or PHP 8.1 or older, gets no fixes at all. That is the starting point for most upgrades we do.
The framework, the language, and everything around them
A major upgrade touches more than composer.json. We move each layer that the new release requires, and test after every one.
Framework and PHP
Laravel and PHP, one major at a time
Each major needs a newer PHP, so the two move together. We step through every release in order on one branch, follow its upgrade guide, and run the suite after each step.
Released together, once the last step holds.
Packages
First-party and third-party
Packages update after the framework lands. When a package no longer supports the target release, we replace it with a maintained one.
Breaking changes
Removed APIs and config
Each major removes helpers, renames methods and changes config. We work through the guide line by line.
- Removed helpers
- Renamed methods
- Config files
- Middleware
- Service providers
Proof
Tests, CI and servers
Where coverage is thin we add tests before changing the framework, and CI, deploys and the server move with the code.
- Tests
- Added around billing, auth and queues before the first major.
- CI and deploy
- Pipelines and Forge or server config updated for the new PHP.
- Staging
- You click through staging. Production ships with a rollback plan.
Assessment first, quote in writing, then code
You know the price before we touch the code. The assessment is free and sets a fixed price in writing.
Start with the free assessment →We read the code, lock file, PHP version, tests and hosting, and list every blocker.
You get: a blocker list
A written price, timeline and upgrade order. No work starts until you sign it off.
You get: price and timeline
Each major lands in order on one branch, and the suite runs green before the next.
You get: a branch per step
It deploys to staging first. You click through what matters and we fix what you find.
You get: a staging link
Backups first, traffic switched once checks pass, and a way back if anything looks wrong.
You get: a release record
Hand the app to the $49 a month care plan or managed hosting, and the next major is never a project again.
You get: no next project
- PHP 8.0 on the server, Laravel 13 needs 8.3
- laravel/framework 9.52.16
- spatie/laravel-permission on an old major
- No tests around billing
- Custom auth guard uses a removed method
Free, whatever you decide
Laravel upgrade questions
How the service runs, what it costs to start, and where it ends. Something not covered here? Ask us directly.
How long does an upgrade take?
It depends on the size of the app and how many major versions it is behind. The free assessment reads the codebase and lists the blockers, and the fixed quote includes a timeline for your app.
Can you upgrade an app another team built?
Yes. We take on apps built by other teams and freelancers, on any Laravel version. The assessment maps the codebase first, so unknown code does not become unknown cost.
Can you jump straight from Laravel 8 to 13?
We step through each major in order on one branch, following that version's upgrade guide, with tests at every step. The majors release together once the last step holds, so you get one tested release, not five risky ones.
Will there be downtime?
The upgrade releases like any deploy, with backups first and a rollback plan ready. Whether the switch itself is zero-downtime depends on your hosting, and we cover that in the assessment.
What if the app has no tests?
We add tests around the critical paths, such as billing, auth and queues, before changing the framework. The upgrade then proves itself at every step instead of at the end.
Do you upgrade PHP too?
Yes. Each Laravel release needs a minimum PHP version, so PHP moves first: the code the new PHP requires, plus the server runtime that runs it.
What does the assessment cost?
Nothing. We read the app, list the blockers, and send a fixed written quote. You can take the quote or leave it; there is no obligation.
Is this included in the care plan?
Minor and patch releases are. Major upgrades change more of your code, so they are planned with you and quoted separately.
See Laravel maintenance →Bring your Laravel app up to date.
Start with a free assessment. We read the codebase, list the blockers, and send a fixed written quote with a timeline. No work starts until you sign it off.