Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Drupal upgrade to version 10 or 11 is stuck

Short answer

Drupal's official guide treats a major upgrade as its own process: separate guides exist for 9 to 10 and 10 to 11, and a Drupal 6 or 7 site is migrated rather than updated. A stuck upgrade usually means custom code, modules or themes that are not ready for the new version. The first safe step is a backup.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The upgrade started and now the site shows errors or will not load.
  • My developer says a module is not ready for the new version.
  • Pages and content look different or are missing after the upgrade attempt.
  • The project has been described as nearly done for weeks.
  • I was quoted a small update, and it has grown into a rebuild.

Why does this happen?

  1. Major upgrades have their own guides

    Drupal's upgrade documentation covers major version upgrades of core, with separate guides for 9 to 10, 10 to 11 and 11 to 12. Minor and patch updates have separate instructions, so treating a major move like a routine update misses steps.

  2. Drupal 6 and 7 are migrations

    For a legacy Drupal 6 or 7 site the guide has pages on preparation, choosing an upgrade approach, upgrading by web browser or Drush, known issues and customising migrations. It is a data move, not a version change on the same site.

  3. Code has to be made ready first

    The guide links to deprecation checking and correction tools for preparing for a new major version. Custom modules and themes that use removed or changed code must be corrected before the new version will accept them.

  4. Third-party modules may not be ready

    Contributed modules each follow their own release schedule. A module that has no release for the new version, or has been abandoned, holds the whole upgrade until it is replaced.

  5. The upgrade was tried on the live site

    Without a copy to rehearse on, every mistake is a live outage, and a half-finished upgrade can leave the database and the code at different versions.

What can I do about it today?

  1. Stop retrying on the live siteRepeated attempts can leave the database in a state that is harder to recover. Pause until someone has taken a copy.
  2. Ask for a backup of files and databaseBoth, taken now, stored away from the server, with the date written on it.
  3. Put up a maintenance notice if visitors see errorsAsk your host or developer to show a plain maintenance page instead of broken pages.
  4. Ask for the blocking listA short written list: which modules, themes or custom features stop the upgrade, and what each needs.
  5. Decide what is essentialMark which features of the old site you really use. Dropping an unused feature is often the fastest way past a blocker.

When should I bring someone in?

  • The live site is down or showing errors after an upgrade attempt.
  • The same blocker keeps coming back and the plan has no end date.
  • You do not have a recent backup and the upgrade has already been started.

How do I handle it?

  1. Restore a safe stateIf the site is half upgraded, I restore from backup or stabilise it first, and take a fresh copy to work on.
  2. Run the deprecation checksI use the checking tools the Drupal guide points to and turn the result into a plain list of blockers.
  3. Replace or remove blockersEach blocking module is replaced, rewritten, or dropped if you no longer use it, and each choice is written down.
  4. Rehearse the full upgrade on a copyThe live site is not touched until the whole upgrade has run cleanly on a copy and been checked page by page.
  5. Switch with a tested way backThe change goes live with a backup taken just before and a rollback that has been tried.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is moving from Drupal 9 to 10 the same as moving from 7 to 10?

No. Drupal's guide has separate major-upgrade guides for the newer versions and treats Drupal 6 and 7 sites as migrations with their own approach.

Can I just update the modules and be done?

Minor and patch updates are covered by separate instructions. A major version change needs the major-upgrade guide and checks that custom code is ready.

Do I need to rebuild the site?

Not necessarily. It depends on how much custom code there is and what is no longer supported. I would say which in writing after looking at the site.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.