If your website runs on Craft CMS, you may have heard that the next version is being rebuilt on something called Laravel. Clients have started asking me what that means for them. This is the answer without the jargon.
What’s Changing
Every CMS is built on top of a framework, which is a set of general-purpose code that handles things like databases, security and sending email. Craft has used one called Yii for its whole life. Craft 6 swaps it for Laravel.
Laravel is the most widely used framework in PHP. More developers know it, more tools are built for it, and it’s under very active development. Yii is none of those things any more, which is why Pixel & Tonic, the company behind Craft, decided to move.
Think of it as putting a new engine in the same car. Where you sit and how you drive stay familiar. What’s under the bonnet is different, and the mechanic needs to know the new engine.
What Stays the Same
Your content stays. Your pages, entries, images and users all come across.
Your design stays too. The templates that turn content into pages are written in a language called Twig, and Craft 6 keeps it. A site shouldn’t look any different after the upgrade.
The way you edit content will be familiar. The control panel has been rebuilt for Craft 6, so it’ll look fresher, and it gains a dark mode and a layout that works on a phone. Sections, entries and fields are all still where you’d expect them.
What Changes for Your Developer
Most of the work is in the parts you never see.
Any custom code written for your site was written for the old framework and will need updating sooner or later. That includes custom plugins and the small bespoke features developers call modules. Craft is shipping a compatibility layer that keeps a lot of old code running in the meantime, so this doesn’t all have to happen on day one.
Plugins from other companies each need a version that works with Craft 6. The popular, well-maintained ones will get there quickly. A plugin that hasn’t been updated in years may never get one, and will need replacing.
The server needs a newer version of PHP, and the way the site is deployed changes a little because some folders are renamed.
Why I’m Glad About It
I said the mechanic needs to know the new engine. I already do. Sentinel, the monitoring service I built and run, is a Laravel application. It checks uptime, runs Lighthouse audits and watches SSL certificates and domain expiry for other people’s websites around the clock, so I’ve spent a lot of time in exactly the parts of Laravel that Craft is adopting, like its queues, scheduled jobs and database layer.
For most Craft developers this move means learning a second framework. For me it joins up two things I already work in. When a Craft 6 site needs a custom feature, I’ll be writing it the way I’d write it for my own product.
Do You Have to Upgrade?
Not soon, as long as you’re on Craft 5.
Craft 6 is in beta now, which means it’s being tested and isn’t meant for live sites. The finished version is planned for March. After that, Pixel & Tonic have said Craft 5 will keep getting security updates until March 2032. That’s years of breathing room.
So the question for most site owners isn’t about Craft 6 at all. It’s which version you’re on today.
Find Out Which Version You’re On
Log in to your control panel and look at the bottom of the left-hand menu, or under Utilities, then System Report. You’ll see a number like 4.16 or 5.8.
If it starts with 5, you’re fine. Keep the site updated and plan the move to 6 for some time after it’s been out a while. I’d expect most sites to do it during 2027.
If it starts with 4, that needs attention now. Craft 4 stopped getting security updates on April 30, 2026. You also can’t jump from 4 straight to 6. The site has to go to 5 first, so the gap only gets wider the longer it’s left.
If it starts with 3, the site has been unsupported since April 2024 and is two upgrades behind. It’s still fixable. It just needs doing in order, and I’d start soon.
What It Costs
It depends on the site, and mostly on two things. One is how many plugins it uses and whether they’re still maintained. The other is how much custom code was written for it.
A fairly plain site with a few healthy plugins is a modest job. One that leans on a dozen plugins, including a couple that have been abandoned, takes longer, because each of those has to be replaced with something else and the content moved across.
I can usually tell which kind you have from a look at the plugin list, and that’s a twenty-minute conversation.
What You Can Do Now
If you’re on Craft 5, there’s useful preparation that doesn’t need Craft 6 to be finished. Clearing out unused plugins, updating the server’s PHP version and tidying old code all make the eventual upgrade smaller. I’ve written a more technical list for developers in Getting a Craft 5 Site Ready for Craft 6.
If you’re on Craft 3 or 4, the first step is getting to Craft 5. That’s worth doing for the security updates alone, and it puts you in position for 6 whenever you’re ready.
Either way, tell me which version you’re on and I’ll tell you what I’d do next.
Leave a Reply