Yes — same policy as our general website audit: free for medium and enterprise-grade businesses. The economics are simple: some audited sites become upgrade clients, and the rest tell people about the report. Both outcomes work for us.

Do you need access to our code?

Not for the first pass — the URL plus what you tell us about plugins and custom modules already produces a useful report. Read-only access to composer.json or the repository makes the plugin register and effort estimate precise.

We are still on Craft CMS 4 (or 3). Is this audit relevant?

More than for anyone else. Craft CMS 4 security support ended April 30, 2026, so every month there is real exposure. Your report will center on the move to Craft CMS 5 first — that step is urgent; Craft CMS 6 can then be planned calmly.

When should we actually upgrade to Craft CMS 6?

For most production sites: 2027, after GA has proven itself in the wild. Earlier makes sense if the new editorial features (content releases, approval workflows, scheduled drafts) solve a problem you have today, or if your team wants Craft CMS running inside an existing Laravel application. Craft CMS 5 is supported to the end of 2030, security-patched to the end of 2031 — the deadline is real but distant.

Can our own developers do the upgrade using your report?

Yes — that is a design goal of the report, not a loophole. Findings come with enough context to hand to any competent developer. If they hit something gnarly mid-upgrade, you know where we are.

What if the audit finds nothing wrong?

Then the report says so, and you have a documented green light instead of a vague hope. "We will tell you when a feature is not worth building" applies to upgrades too — including the finding that yours is already easy.

Craft CMS · Free readiness audit

Is your site ready for Craft CMS 6?

Craft CMS 6 moves to Laravel — beta expected Q3 2026, GA in Q4. We audit your site against the actual alphas and tell you exactly what the upgrade will take: what is ready, what will fight you, and what to fix now while it is still cheap.

Reviewed by a senior engineer at a Craft CMS Verified Partner — we are already running the Craft CMS 6 alphas
A scorecard, a plugin risk register and an effort estimate in days — not vibes
Free, no obligation. If the honest answer is "wait until 2027", that is what the report says

The checklist

What we actually audit

Eight areas that decide whether your Craft CMS 5→6 upgrade is a quiet week or a rescue project.

Version & patch level

Where you stand today. The upgrade path starts at the latest Craft CMS 5 release — and if you are still on Craft CMS 4, whose security support ended April 30, 2026, that finding jumps to the top of the report.

The deprecation log

Craft CMS 5’s deprecation warnings are, in effect, your Craft CMS 6 readiness report. We read yours line by line and translate it into concrete fixes, each one safe to ship today.

Plugin risk register

Every installed plugin, classified: has a native Craft CMS 6 plan, will ride the Yii 2 compatibility adapter, or is abandoned. Abandoned plugins are the one genuine upgrade risk — better to know in 2026 than during the upgrade.

Custom modules & integrations

Custom modules face the same transition as plugins, except nobody else is maintaining them. We assess how much of your custom code leans on Yii APIs the adapter covers — and how much needs real porting work.

Legacy element types

Categories, Tags and Global Sets are on their way out in favor of entries. Converting is voluntary today and expected eventually — we scope exactly what your conversion involves.

PHP & hosting path

Craft CMS 6 requires PHP 8.5 minimum. We check whether your host has a credible path there — and whether the upgrade is the right moment to move to better infrastructure.

Template & front-end debt

Twig survives the transition untouched, so templates are rarely the blocker — but deprecated Twig patterns, inline hacks and abandoned front-end tooling still surface during upgrades. We flag them now.

Content model health

An upgrade is the cheapest moment to fix a content model that editors have outgrown. We note where your sections, entry types and fields will fight Craft CMS 6’s new publishing workflow instead of using it.

How it works

From URL to upgrade plan

01
Share your site
The form below takes two minutes. Read-only access to composer.json or the repo sharpens the report, but is not required for the first pass.
02
A senior engineer digs in
The eight checks above, run against what we know from the current Craft CMS 6 alphas — not against last year’s blog posts.
03
You get the report
Readiness scorecard, prioritized prep list, plugin risk register, and an upgrade effort estimate in days. Written to be handed to any developer — including your own.
04
You decide calmly
Upgrade with us, upgrade in-house using the report, or wait — Craft CMS 5 is supported to 2030, so "not yet" is a legitimate answer. We will say it when it is the right one.

What you walk away with

A report you own, whoever does the upgrade.

Readiness scorecard across the eight audit areas
Prioritized punch list of Craft CMS 5-safe prep work — every item shippable today
Plugin risk register: native plan / adapter path / abandoned, per plugin
Upgrade effort estimate in days, with the assumptions stated
Recommended timing for your site — the calm 2027 window, or sooner if something urgent surfaces
A fixed quote if you want us to do the work — no obligation to take it

Know before GA lands.

Beta is expected within weeks. Walk into the Craft CMS 6 era with a plan — not a surprise.

Jump to the form

Read the full Craft CMS 6 briefing·Craft CMS development service·General website audit

Fair questions

Is it really free?: Yes — same policy as our general website audit: free for medium and enterprise-grade businesses. The economics are simple: some audited sites become upgrade clients, and the rest tell people about the report. Both outcomes work for us.
Do you need access to our code?: Not for the first pass — the URL plus what you tell us about plugins and custom modules already produces a useful report. Read-only access to composer.json or the repository makes the plugin register and effort estimate precise.
We are still on Craft CMS 4 (or 3). Is this audit relevant?: More than for anyone else. Craft CMS 4 security support ended April 30, 2026, so every month there is real exposure. Your report will center on the move to Craft CMS 5 first — that step is urgent; Craft CMS 6 can then be planned calmly.
When should we actually upgrade to Craft CMS 6?: For most production sites: 2027, after GA has proven itself in the wild. Earlier makes sense if the new editorial features (content releases, approval workflows, scheduled drafts) solve a problem you have today, or if your team wants Craft CMS running inside an existing Laravel application. Craft CMS 5 is supported to the end of 2030, security-patched to the end of 2031 — the deadline is real but distant.
Can our own developers do the upgrade using your report?: Yes — that is a design goal of the report, not a loophole. Findings come with enough context to hand to any competent developer. If they hit something gnarly mid-upgrade, you know where we are.
What if the audit finds nothing wrong?: Then the report says so, and you have a documented green light instead of a vague hope. "We will tell you when a feature is not worth building" applies to upgrades too — including the finding that yours is already easy.

Sources: Craft CMS supported versions & LTS dates · "Craft’s Going Laravel" — official announcement · Official Craft 6 upgrade guide