Laravel 12 vs 11 vs 10: Should Your Perth Business Upgrade?

If your business runs a Laravel application — and in Perth, a surprising number do — you have probably noticed that Laravel releases a new major version every year. Laravel 10 arrived in February 2023, Laravel 11 in March 2024, and Laravel 12 in February 2025. Each brings new features, performance improvements, and eventually, the end of security support for older versions.

The question is not whether to upgrade. It is when, and whether the cost is justified for your specific situation.

We have been building Laravel applications in Perth since 2013 — starting on Laravel 4 and shipping through every major version since. This post is the honest comparison we give our own clients when they ask us about upgrading. (Still deciding whether Laravel is the right framework at all? See Laravel for Australian business — is it the right fit?.)

The short answer

Laravel 10: Security support ends 6 August 2025. If you are still on Laravel 10, start planning now.
Laravel 11: Security support runs until March 2026. You have time, but not unlimited time.
Laravel 12: Current release. Actively supported with bug fixes and security patches.

If your application is on Laravel 9 or earlier, it is already running on an unsupported version with known unpatched vulnerabilities. That is not a technical-debt conversation — it is a security conversation.

What changed between versions

Laravel 10 → 11: The big simplification

Laravel 11 was the most significant architectural change since Laravel 5. The application skeleton was simplified dramatically:

Streamlined directory structure: The default app/Http/Kernel.php, app/Console/Kernel.php, and many config files were removed or consolidated. Middleware is now registered in bootstrap/app.php.
Per-second scheduling: The task scheduler can now run commands every second, not just every minute.
Laravel Reverb: A first-party WebSocket server for real-time features, replacing the need for Pusher or third-party WebSocket services.
Health check routing: Built-in /up endpoint for load balancer and monitoring health checks.
Dumpable trait: Native dd() and dump() support on any class.
PHP 8.2 minimum: Dropped support for PHP 8.1 and earlier.

Breaking changes that affect upgrades: The middleware registration change is the biggest. If your application customises the HTTP kernel extensively, expect 1–2 days of migration work. The simplified config structure is optional for existing applications — you do not have to adopt it.

Laravel 11 → 12: Refinement, not revolution

Laravel 12 is a refinement release. There is no architectural upheaval:

PHP 8.2 minimum (same as Laravel 11, but PHP 8.4 support is fully tested).
New starter kits: React, Vue, and Livewire starter kits with modern tooling.
Improved Eloquent casting: Better type safety and custom cast improvements.
Performance improvements: Lazy service resolution and streamlined container bindings reduce memory usage on large applications.

Breaking changes: Minimal. Most Laravel 11 applications upgrade to Laravel 12 in under a day. The largest effort is usually updating third-party package compatibility.

When upgrading is worth it

Upgrading makes clear financial sense when:

Your current version is approaching end-of-life. Running unsupported software exposes your business to known vulnerabilities. For regulated industries (government, healthcare, finance), this can be a compliance violation.
You are paying more for maintenance than the upgrade would cost. Legacy Laravel applications on old PHP versions cost more to host (fewer hosting options), more to maintain (fewer developers willing to work on them), and more to extend (modern packages require modern Laravel).
You need features from the new version. Laravel Reverb (real-time WebSockets), improved queue batching, and Filament support all require Laravel 10+ or 11+.
You are about to start a major feature build. Upgrading before a new feature phase means the new code is written against current framework patterns, not patterns that will be deprecated by the time the feature ships.

When upgrading can wait

Upgrading can be deferred (but not indefinitely) when:

Your application is stable and in maintenance mode. If no new features are planned and the application is not exposed to the public internet, the urgency is lower — but security patches still matter.
You are planning a full rewrite. If the application is being replaced within 6–12 months, upgrading the legacy version may not be the best use of budget. But be honest about the rewrite timeline — "6–12 months" has a way of becoming "24 months."
Budget is genuinely constrained. A Laravel upgrade is an investment, not an expense. But if cash flow is tight, a phased approach (audit now, upgrade next quarter) is better than no plan at all.

What an upgrade actually involves

For a typical mid-sized Laravel application (50–200 routes, 30–80 models, 10–20 third-party packages):

Version jump	Typical effort	Typical cost
Laravel 11 → 12	2–5 days	$5,000–$10,000
Laravel 10 → 12	1–2 weeks	$10,000–$20,000
Laravel 8/9 → 12	2–4 weeks	$15,000–$35,000
Laravel 5/6/7 → 12	4–8 weeks	$30,000–$60,000

These ranges assume a codebase with reasonable test coverage. Applications with no tests, abandoned packages, or heavy custom framework modifications will be at the higher end.

The process always starts with a codebase audit — a one-week assessment that produces a detailed report with every breaking change, every outdated dependency, and a fixed-price quote for the full upgrade. The audit costs $2,500 and is credited against the upgrade if you proceed.

For most business software — customer portals, internal tools, SaaS products, admin panels, document workflows, API backends — Laravel remains the fastest path from requirements to production for a competent team, which is exactly why keeping your version current pays off. (For where Laravel fits best in the first place, see Laravel for Australian business — is it the right fit?.)

What to do next

If your application is on an unsupported Laravel version (9 or earlier), the first step is a codebase audit. It takes one week, costs $2,500, and gives you a clear picture of the effort and cost involved.

If your application is on Laravel 10, start planning the upgrade before security support ends in August 2025.

If your application is on Laravel 11, you have time — but upgrading to Laravel 12 during your next feature sprint is the most cost-effective approach.

Need help deciding? Book a free discovery call with our Laravel team to discuss your specific situation. No obligation, no jargon — just an honest assessment of whether upgrading is worth it for your business.

Nano Solutions has been building Laravel applications in Perth since 2013. We are on the WA Government CUAICTS2021 panel (Contractor #225) and active members of the Australian Laravel community. Learn more about our Laravel development services or our Laravel modernisation service.