Upgrade Drupal
Free · No login required

Drupal Upgrade Readiness Scanner

Paste your composer.json and instantly see which contrib modules block your upgrade, your exact upgrade path, and how much manual work you can skip.

Drop composer.json here or click to browse
or paste directly
💡On Drupal 7? Drupal 7 doesn't use Composer, so this scanner won't work for it. Check out the D7 Migration Blueprint ($249) — it analyzes your D7 codebase directly and delivers a ready-to-go D11 scaffold as a standalone branch.

How it works

  1. 1Paste or upload your composer.json. The file is processed entirely in your browser — the raw composer.json is never sent to our servers.
  2. 2Module-by-module compatibility check. We send only the list of module names (no site-specific data) to check each one against the Drupal.org release API. Results are color-coded: green (compatible), red (no D11 release), amber (unknown/abandoned).
  3. 3See your exact upgrade path and effort estimate. The results show your mandatory intermediate version steps, which modules block the upgrade, estimated manual hours for just the incompatible modules, and the total cost at your rate.
  4. 4Automate the work. If you want Upgrade Drupal to apply the changes automatically and open a Pull Request to your repository, subscribe or order a one-time upgrade.

Frequently asked questions

Is this scanner really free?

Yes, completely free. No account required, no credit card, no usage limits. The analysis runs in your browser so we never see your composer.json. Only module names are sent to check compatibility.

What Drupal versions does it support?

The scanner handles Drupal 8, 9, 10, and 11 composer.json files. It identifies your current core version and shows the recommended upgrade target — typically Drupal 11.x — along with any mandatory intermediate versions.

What does "incompatible" mean for a module?

A module is flagged incompatible when the Drupal.org release history shows no stable release that declares support for your target Drupal version. These are the modules that cause composer update to fail — and the ones that take hours to resolve manually.

Can I skip intermediate Drupal versions?

Not always. Going from D9 to D11 requires stepping through D9.5+ then D10.3+ first — Drupal removes older update hooks at each major release. The scanner shows your exact required path based on your current major version.

Can it handle Drupal 7 sites?

Drupal 7 sites do not use Composer, so there is no composer.json to scan. For a D7 migration analysis, see the D7 Migration Blueprint instead.

How accurate is the effort estimate?

The estimate is based on the number of incompatible contrib modules (those with no official D11 release) and the typical hours required to patch or replace each one. Compatible modules are excluded from the count. It is intentionally conservative — actual effort varies depending on custom code, theme complexity, and how actively each module is maintained upstream.