Laravel upgrades for applications that cannot afford to break
Pixel upgrades older Laravel applications to the current version without breaking what already works. We audit first, add tests around the parts that matter, then move one version at a time until you are current.
A Laravel upgrade brings an older application up to the current, supported version of Laravel and PHP. It is for businesses running a Laravel system that is several versions behind and no longer receiving security fixes. Pixel audits the application for a fixed fee, then quotes the upgrade as a fixed price. Timeline depends on how many versions you are behind and how much test coverage already exists.
Why staying current matters
An old Laravel version does not stop working on the day support ends. The cost shows up later, usually at a bad time.
Security support ends
Each major Laravel version receives bug fixes for 18 months and security fixes for two years. After that, newly found vulnerabilities in your version are not patched.
PHP versions move on
Old Laravel versions cannot run on current PHP. When your host retires the PHP version you are on, an application that was merely old becomes one that will not start.
Packages stop supporting you
Payment, PDF, queue and admin packages drop older Laravel versions. Bug fixes and new features in those packages are then out of reach.
Third parties change their APIs
Payment and accounting providers retire old API versions. The SDK that supports the new one often needs a newer Laravel than you are running.
Hiring gets harder
Developers want to work on current versions. An application several versions behind is slower and more expensive to staff.
The gap compounds
One version behind is a small job. Five versions behind is five small jobs, plus every package that changed in between.
The Laravel Upgrade Process
Upgrades go wrong when several versions are jumped at once with no tests to show what broke. We do it in small, checked steps.
01
Audit
We record the Laravel and PHP versions, every package and its compatibility, any code that touches framework internals, and how the application is deployed.
02
Test coverage
Before changing versions we write automated tests for the paths that matter most: sign-in, payments, orders and anything else the business cannot afford to have break.
03
Staged upgrades
We upgrade one major version at a time, in order. After each step the tests run, deprecations are cleared and the application is checked on staging.
04
Dependencies
Packages are upgraded alongside the framework. Abandoned packages are replaced with maintained ones or with a small amount of code you own.
05
Release
The upgraded application goes to production in a planned release, with a database backup, a rollback path and monitoring in place for the first days.
06
Staying current
Once you are on the current version, the yearly upgrade is a routine task. Most clients hand it to us as part of a support retainer.
What makes a Laravel upgrade simple or hard
Two applications on the same Laravel version can need very different amounts of work. Before quoting, we look at four things.
How many versions behind. Each major version has its own upgrade guide and its own breaking changes. The work adds up version by version.
Test coverage. An application with a good test suite can be upgraded quickly, because the tests show what broke. One with no tests needs coverage written first, and that is often the largest part of the job.
Package choices. Well-maintained packages upgrade cleanly. Abandoned or heavily modified ones have to be replaced, and code that was edited inside the vendor folder has to be untangled.
How closely the code follows the framework. Applications written the way Laravel intends are straightforward. Ones that override framework internals or copy old framework code into the project take longer.
The audit answers all four, which is why the quote that follows is a fixed price and not an estimate.
Laravel 8 or earlier, and when a rebuild makes more sense
Applications on Laravel 8 or earlier are the ones we are asked about most. They are well past the end of security support and usually tied to a PHP version that hosts are retiring.
Most of them can still be upgraded. Laravel's structure has stayed consistent across versions, so a reasonably built application on Laravel 6, 7 or 8 can be walked forward one version at a time.
A rebuild starts to make more sense when several of these are true: the application is on Laravel 4 or 5.0 to 5.4, it has no tests and no documentation, it relies on packages that no longer exist, and the business also wants to change how the system works. At that point the upgrade and the rewrite cost about the same, and the rewrite leaves you with a better result.
When that is what the audit shows, we say so and explain why. The work then follows the same staged approach as our PHP to Laravel migration. If the application has wider problems than its version number, such as failing jobs, slow pages or no developer to maintain it, our Laravel rescue service covers the takeover as well as the upgrade.
Upgrades done by a Premier Laravel Partner
Pixel is Australia's only Premier Laravel Partner. The Laravel team awards that status to agencies it has reviewed, and it means we work on current versions of the framework every day.
For an upgrade, that matters in a practical way. We know which changes in each version cause real problems, which can be ignored and which newer features are worth adopting while we are there. The work is done by senior developers in Brisbane, and your code and data stay in Australia.
Laravel platforms we keep current
These production systems are upgraded by our team as each new Laravel version is released.
Canary
A pharmacy platform with government-approved production access to Australia’s national e-prescription network.
90 days
ADHA Conformance Achieved
Nationwide
Live e-Script Access
Post-launch
Evolved into SaaS
Nourish'd
A custom meal delivery platform managing subscriptions, funded-care billing, fulfilment, and operational reporting across three customer segments.
30+
Operational Reports
199
Support at Home Providers
3
Customer Segments
Laravel upgrade
FAQs
Couldn't find the answer you were looking for? No worries, get in touch with us.
Contact Us
How long does a Laravel upgrade take?
It depends on how many versions behind the application is, how much test coverage it has and which packages it uses. An application one or two versions behind with good tests is a short job. One that is five versions behind with no tests takes considerably longer, mostly because of the tests.
The audit gives you a timeline for your application before any upgrade work starts.
How much does a Laravel upgrade cost?
We quote upgrades as a fixed price after auditing the application. The audit, our Technical Blueprint, is $2,990 including GST and is credited against your first invoice if you go ahead with us.
Can you upgrade several versions at once?
We upgrade through each major version in order, but it is delivered as one project. Going one version at a time means that when something breaks, we know which change caused it.
You do not need to release each intermediate version to production. Usually only the final, current version is deployed.
Will the upgrade break our application?
The process is built to prevent that. We write tests for the critical paths before upgrading, run them after every version step and check the result on a staging copy of production before release.
The release itself has a database backup and a rollback path.
Our application has no tests. Can it still be upgraded?
Yes. Most applications we upgrade arrive with few or no tests. We write coverage for the parts the business depends on first, and that coverage stays with the application afterwards.
Is it worth upgrading, or should we rebuild?
Upgrading is nearly always cheaper for an application on Laravel 6 or later. A rebuild becomes worth considering for very old versions with no tests, missing packages and a business that also wants the system to work differently.
We make that call from the audit and show the reasoning.
Do you also upgrade PHP and our server?
Yes. A Laravel upgrade usually requires a newer PHP version, so we upgrade both together, along with the database version and server configuration where needed.
Find out what it would take to get your Laravel application current
A Technical Blueprint audits your application and gives you a version-by-version upgrade plan with a fixed price.
$2,990 inc. GST · credited against your first invoice if you build with us
Related services
Laravel Rescue
Taking over and stabilising a Laravel application that has become fragile or unsupported.
Learn more →
Laravel Support
Ongoing patching, monitoring and upgrades so the application stays current.
Learn more →
PHP to Laravel Migration
Rebuilding a legacy PHP application on Laravel in stages.
Learn more →