Laravel upgrade service · UK/EU hours
A Laravel upgrade service at a fixed price: tests green, nothing touched in production until it is rehearsed.
Laravel 5 to 11 and PHP 7 applications brought to the supported versions, abandoned packages replaced, and hand-over notes your next developer can read. Start with the audit — it is free and tells you which package you need.
Paste your composer.json. Get the real state of the app, in one page. Within 24 hours.
Two packages
The difference is distance: how many majors stand between you and current, and how many packages have been abandoned along the way.
Upgrade Sprint
$2,500
£1,900 · €2,300 · 7–10 working days
One or two Laravel majors plus the PHP runtime, with the test suite green.
Start with the free auditFull Upgrade
$4,500–$6,000
£3,400–£4,500 · €4,100–€5,500 · 2–3 weeks
Three or more majors, abandoned packages replaced, tests backfilled.
Start with the free auditWhat each package covers
| Scope | Upgrade Sprint | Full Upgrade |
|---|---|---|
| Laravel and PHP brought up to current supported versions | ||
| Every third-party package replaced or updated, with the reasons written down | ||
| Existing tests passing; smoke tests added where there were none | ||
| Deployment rehearsal on a staging copy before anything touches production | ||
| Hand-over notes your next developer can read | ||
| Replacement of abandoned packages with maintained equivalents | ||
| Test coverage backfilled around the code paths the business depends on | ||
| Security review of authentication, sessions and file handling | ||
| A written risk register of what we found and what we left alone | ||
| Price | $2,500 | $4,500–$6,000 |
| Duration | 7–10 working days | 2–3 weeks |
Not in the Upgrade Sprint
- Rewrites of application features
- New functionality
Not in the Full Upgrade
- Front-end framework migrations (quoted separately)
- Infrastructure moves (quoted separately)
Why now
The dates that decide whether your app is receiving security fixes this month.
- 10 August 2027
Laravel 13 bug fixes end
Security fixes continue to 24 February 2028.
- 24 February 2027
Laravel 12 security fixes end
Bug fixes already ended on 13 August 2026.
- 31 December 2026
PHP 8.2 security support ends
Every Laravel 10 and 11 app still on PHP 8.2 loses runtime security fixes on this date.
- 12 March 2026
Laravel 11 security fixes ended
Every Laravel 11 app is now unpatched.
- 31 December 2025
PHP 8.1 security support ended
PHP 8.0 and 8.1 still run roughly a quarter of PHP 8 sites.
Still on PHP 8.2? Read what the end of PHP 8.2 security support means for a Laravel 10 or 11 app. On Laravel 11 or 12? Read the end-of-life guide for owners.
What forces the date
An end-of-life date on its own is advisory. These three are not, and each is quoted from its source.
Cyber Essentials v3.2 (April 2025)
“All software on in-scope devices must: be licensed and supported; removed from devices when it becomes unsupported or removed from scope by using a defined sub-set that prevents all traffic to / from the internet; have automatic updates enabled where possible; be updated, including vulnerability fixes, within 14 days of release, where the update fixes vulnerabilities described by the vendor as 'critical' or 'high' risk”
Bespoke application code is out of Cyber Essentials scope, but the PHP runtime and operating system on an internet-facing server are not. A Laravel app pinned to an end-of-life PHP branch fails the certification through its server.
Source, checked 16 October 2026
Cyber insurance renewal
“Use of any outdated or unsupported software or systems”
Listed among the exclusions on Hiscox UK's cyber and data insurance policy. Policies are re-assessed every twelve months, so the renewal questionnaire is usually where an owner first meets the version problem. The UK Cyber Security Breaches Survey 2025 found 62% of small and 65% of medium businesses hold cyber insurance.
Your host retires the PHP version
“If your project uses a retired version, you must update to a supported version.”
Upsun (Platform.sh) lists PHP 8.1 and older as retired and 8.2 and 8.3 as deprecated. Ubuntu 20.04, which shipped PHP 7.4, left standard support in May 2025. Shared hosts force the runtime change on their own schedule, and the application breaks on their date rather than yours.
Source, checked 16 October 2026
How an upgrade runs
Five steps. You see the scope and the price before anything is touched, and the rehearsal before anything is deployed.
- 1
Audit
You paste composer.json. We return the versions against their end-of-life dates, the abandoned packages, and which package fits. Within 24 hours.
- 2
Fixed quote
A one-page scope: what moves, what gets replaced, what we will not touch. The price on it is the price you pay.
- 3
Staging rehearsal
The whole upgrade runs on a copy first. Tests green, deploy rehearsed, rollback written down. Nothing reaches production untested.
- 4
Production
Deployed in a window you choose, with us watching logs and queues afterwards. Downtime is minutes, and usually none.
- 5
Hand-over
Notes your next developer can read: what changed, why each package was replaced, and what we left alone and why.
Questions we get before an upgrade
Sprint or Full Upgrade — how do I know which?
Count the Laravel major versions between you and current. One or two, with the PHP runtime, is a Sprint. Three or more, or a codebase with several abandoned packages that need replacing, is a Full Upgrade. The free audit does the counting for you and names the package.
What if there are no tests?
In a Sprint we add smoke tests around the routes and jobs the business depends on so we can prove the upgrade did not break them. In a Full Upgrade we backfill coverage around the critical code paths properly, and the test suite is part of what we hand over.
How much downtime should I plan for?
Minutes, in a window you pick. Everything is rehearsed on a staging copy first, including the deploy itself and the rollback. Most upgrades go out with no visible downtime at all.
Who owns the code afterwards?
You do, from day one. The work happens in your repository, under your access controls. There is nothing to hand back at the end because it was never ours.
What is not included?
Rewrites of application features, new functionality, front-end framework migrations and infrastructure moves. We quote those separately so the upgrade price stays fixed.
Can you take over an app another developer abandoned?
Yes — that is most of the work we do. We need repository access and a database copy. We do not need the previous developer.
Terms
- Half of the fixed price up front, half on hand-over. No surprises in between.
- Fixed means fixed: if we underestimated, that is our cost, not yours.
- You own every line. Code lives in your repository from day one.
- Care plans run month to month after a three-month minimum.
- Working hours overlap the UK and EU day in full; the US East Coast morning in part.
What you are actually buying
The answer to "why an agency in India?", in writing.
Who you contract with
Jigomit LLP, Ahmedabad, India. The company name on the contract and on every invoice.
UK/EU working hours
Working hours overlap the UK and EU day in full; the US East Coast morning in part.
NDA before requirements
We sign your NDA, or send ours, before you share a repository or a brief.
You own every line
You own every line. Code lives in your repository from day one. All IP in the work transfers to you on payment.
Named engineer
The same engineer stays on your account. No junior substitution.
Fixed means fixed
Fixed means fixed: if we underestimated, that is our cost, not yours.
Data-processing terms published
UK GDPR Article 28 processing terms are published and signed as a schedule to the engagement letter. Read the data-processing terms
Written SLAs
Response times in the contract, not on a slide.
Find out which package you need
Paste your composer.json. The audit is free, takes a minute, and comes back within 24 hours with the price.
Run the free Laravel audit