Drupal End of Life
Versions Upgrades Security Tell us your situation
Two-step major upgrade

Upgrade Drupal 10 to Drupal 12

Drupal 10 → 12 skips a major version, so it's really two managed updates (10 → 11 → 12) — and the point where most site owners fully meet Drupal's Composer-only, command-line workflow.

Message Us For Help →

Is Drupal 10 to 12 a direct upgrade?

Not quite — in practice you step through Drupal 11 on the way: bring the site current to Drupal 11, then move to Drupal 12. The good news is that Drupal 10, 11, and 12 all share the same modern architecture, so each hop is a managed update, not a rebuild. The cost is simply that you do the work twice.

What the upgrade involves

  1. Readiness check — run Upgrade Status to inventory module compatibility and deprecated code.
  2. 10 → 11 — update modules to Drupal 11-ready releases, clear deprecations (Rector helps), bump core to ^11, run updates, test.
  3. 11 → 12 — repeat the cycle for Drupal 12: module updates, deprecation cleanup, core to ^12.
  4. QA & deploy — verify on staging and deploy.

Each step is routine for someone fluent in the workflow; the effort is mostly in contributed-module compatibility, which can vary from release to release.

Can I upgrade Drupal 10 to Drupal 12 myself?

It's feasible for a technically comfortable team — but meaningfully harder than an adjacent-version jump, for two reasons.

Two majors, and a workflow change. You're clearing module and deprecation issues twice, and this is where you fully commit to Drupal's Composer-only approach. Drupal 11 removed the admin-UI ZIP module install that Drupal 10 still had, so from here on, modules are managed through Composer on the command line.

Realistically, doing this in-house assumes command-line/SSH access (or a local environment like DDEV), comfort with Composer and Drush, and a Composer-friendly host. With those, Drupal 10 → 12 is a manageable project. Without them, it's where many site owners realize their Drupal site has outgrown their in-house skill set — which is a completely reasonable place to bring in help.

If you're comfortable at the command line, the lighter Drupal 11 → 12 path shows the core workflow; if you're further back, Drupal 9 → 12 shows how it compounds.

Two-step upgrade feel like a lot?

Tell us what you're running as well as any additional tech stack details. From there we can figure out together if an upgrade makes the most sense — or if there's another option best suited for you and your organization.

Tell us what you need →

Tell us what you need

Share your site and any additional tech stack details. We'll flag your Drupal version and hosting setup and figure out together whether a DIY Drupal 10 → 12 upgrade is realistic for you — or better handed off. No obligation.

We'll email you back and may follow up if we spot significant issues worth fixing. No spam.

Drupal 10 to 12: frequently asked questions

Can I upgrade Drupal 10 to 12 myself?

Feasible for technically comfortable teams, harder than a single-version jump: it's two majors (10→11→12) of module and deprecation work, plus fully adopting the Composer/command-line workflow. Non-technical owners usually need help.

Do I have to go through Drupal 11?

Effectively yes — you update to Drupal 11, then Drupal 12. Both share the modern architecture, so each is a managed update, not a rebuild.

How long does it take?

More than an adjacent-version upgrade but far less than a Drupal 7 rebuild — typically weeks, driven mostly by contributed-module compatibility.