To new businesses, give you the expertise, approaches, and techniques you should know to be a super hero.
Your Laravel app works. Nobody wants to touch it. Then a host drops an old PHP version, a security scanner flags a package, or a new developer refuses to work on a version that stopped getting patches years ago. The longer the upgrade waits, the more versions it has to cross, and every version adds its own breaking changes.
This guide gives a practical order of work for upgrading a Laravel application, from checking whether you need to, through seven steps that keep production safe. It also compares doing it yourself, using an automated tool, and hiring it out, so you can decide before you start.
Laravel supports each major release with bug fixes for 18 months and security fixes for two years. Once security fixes end, a newly found vulnerability in the framework is not patched for your version.
| Version | PHP versions | Security fixes until |
|---|---|---|
| 10 | 8.1 to 8.3 | February 4, 2025 |
| 11 | 8.2 to 8.4 | March 12, 2026 |
| 12 | 8.2 to 8.5 | February 24, 2027 |
| 13 | 8.3 to 8.5 | Q1 2028 (planned) |
Source: the Laravel release notes. Versions 8 and 9 ended before this table starts.
If your app runs on 11 or older, it no longer receives security fixes. If it runs on 12, you have time, but not much of it, and a version-by-version upgrade is easier to plan than an emergency. If you would rather hand the work over, that is part of our Laravel development services, covered further down.
Most upgrade pain falls into five areas. Know them before you start.
| Area | What breaks | How to find it |
|---|---|---|
| PHP version | Each Laravel version needs a minimum PHP version, and servers on old PHP cannot run it | Check the table above againstphp -v on every environment |
| Packages | Abandoned or slow-to-update packages block the upgrade | composer why-not laravel/framework:^13.0 |
| Removed or changed framework methods | Code that worked on your old version fails or behaves differently | Your test suite, plus the upgrade guide for each version |
| Third-party services | Payment, mail and storage integrations depend on library versions | Test each integration on staging with test credentials |
| Hosting and deployment | Old servers, shared hosting limits, build scripts tied to old Node or PHP | A staging server that matches production |
One note on structure. Laravel 11 introduced a slimmer default application skeleton, but the official upgrade guide does not require existing apps to adopt it. Upgrade first and restructure later, as a separate task
Create a branch for the upgrade and stop merging unrelated features into it. Copy the production database to a staging environment, with personal data removed, so you test on realistic data. Take a full backup of production before any deploy.
If the app has no tests, write them before you upgrade. They do not need to be perfect. Cover the flows that make money or lock people out: sign in, checkout, payments, password reset, exports and any scheduled job. Then run them to get a baseline:
An upgrade without tests is a guess. You find breakage when a customer does.
List what is outdated, check what blocks the target version, and check for known vulnerabilities:
Replace or fork abandoned packages now. A package that no longer updates is the most common reason an upgrade stalls halfway.
Move staging to a PHP version your next target supports. Run the tests again before touching Laravel. If the suite passes on the new PHP, you have already separated the PHP problems from the Laravel problems.
Follow the upgrade guide for each version, in order, and run the tests after every step:
Then repeat for 10, 11, and so on. Going from version 8 to 13 is five hops. Teams with strong tests sometimes skip hops, but every skipped version multiplies the unknowns in one big change. Commit each hop on its own so you can find which step broke what.
Once you are on the target version, clean up the deprecation warnings. Add a static analysis tool such as Larastan to catch type problems the tests miss, and run Laravel Pint to keep style changes separate from logic changes. This is the step people skip, and it is where quiet bugs hide.
Run the full test suite and a manual pass on staging. Test every payment webhook with test credentials, because failures there are silent until money goes missing. Our guide to fixing payment gateway problems is written for Shopify, but the failure patterns it describes apply to any checkout. Deploy at a quiet time with a rollback plan, then restart queue workers so they load the new code:
Watch your error logs and your scheduled jobs for the first few days.
| Option | Works best when | Watch out for |
|---|---|---|
| Do it yourself | You have a developer who knows the app, good test coverage and time to spare | The upgrade competes with feature work, and gaps in tests surface late |
| An automated tool such as Laravel Shift | The app is conventional and mostly follows framework defaults | It automates framework changes, not your custom code or abandoned packages |
| Hire a Laravel team | The app is business critical, has weak tests, takes payments or runs on an end-of-life version | Choose a team that shows you a written plan and demos on staging before touching production |
Tools help with the mechanical part, and they are worth using. They do not decide what to test, which packages to replace, or when to deploy. Those decisions are the real work.
Sometimes the app has deeper problems: no structure, logic spread across views, queries that fall over under load. An upgrade will not fix those, and it can make them harder to see. In that case, plan the upgrade together with a cleanup, using the principles in our guide to building scalable Laravel applications. And if the app is mostly pages and posts, ask whether Laravel was the right tool at all, using our Laravel vs WordPress comparison.
When we upgrade a client application, you get a written plan before work starts, one branch per version hop, a staging site you can click through, and notes on every change that touched your code. That is how a team that works in your time zone keeps an upgrade readable instead of a black box.
php artisan --version in the project folder, or open composer.lock and find the laravel/framework entry. The lock file shows the exact installed version, while composer.json shows only the allowed range. Check both, since the two can differ on long-running projects. A reader opens your 2,000-word guide looking for one answer. They scroll, lose their place, scroll back up, and leave. Long posts only work when readers can jump to the part they came for, and WordPress does not ship a table of contents that does that. This guide shows three ways to add a sticky […]
Read moreYou hand a client a finished website. The design is theirs, the copy is theirs, and then they open wp-login.php for the first time and see the WordPress logo. Click it and it opens wordpress.org. To a client who just paid for a custom brand, that looks like unfinished work, and it is the page their whole team sees every day.
Read moreYou publish on Medium, but your own website shows none of it. A visitor who lands on your homepage has no idea you write at all, and the stories you spent hours on sit on someone else’s domain. Linking to them by hand works for a week. Then you publish again and the page is out of date.
Read more