Which Drupal 7 modules have a Drupal 10 or 11 release?

How to read a row

The status column is mechanical. For each project we read every published release in the feed, take the core_compatibility constraint that ships with it, and ask whether a release exists that runs on Drupal 10 or 11 — preferring a stable release over an alpha, beta, RC or dev snapshot.

• No Drupal 8+ release (26) — Nothing has been published for Drupal 8 or later. Either the job moved into core, a differently named project took over, or the functionality has to be rebuilt.
• Stopped at Drupal 8/9 (11) — The port stopped before Drupal 10. Treat it the same as the row above: something else has to do this job.
• Only a pre-release for Drupal 10/11 (11) — There is a Drupal 10 or 11 release, but only an alpha, beta, RC or dev snapshot. Usable, often for years, but you are choosing to run unreleased code.
• Stable release for Drupal 10 (3) — A stable release runs on Drupal 10 but nothing yet declares Drupal 11. Fine for a migration to 10; re-check before targeting 11.
• Stable release for Drupal 11 (77) — A stable release declares Drupal 11 compatibility. This module is not what makes your migration hard.

Two columns are separate from the verdict, and both matter. Maintenance is the status the maintainers themselves publish on drupal.org; 16 of these 128 projects are unsupported, abandoned or seeking a new maintainer, and a few of those have a perfectly good Drupal 11 release that nobody is looking after. What to do instead is the only hand-written column on the page, and it is the reason the page is worth reading rather than generating: 37 of these projects have no Drupal 10 or 11 release at all, and for 28 of them that is because the job is already done for you — it moved into Drupal core, or a differently named project took it over. Reporting those as "no port" would send you rebuilding something you now get for free. The remaining 9 carry no note, which means exactly that: we have nothing to tell you beyond the release data, and you need to look at what the module does on your site.

The 50 that need a decision

These are the rows worth reading before you quote the work. Everything not listed here has a stable Drupal 10 or 11 release and an active maintainer.

• No Drupal 8+ release (26) — addressfield, apachesolr, bean, boxes, email, entity_translation, facetapi, globalredirect, hybridauth, i18n, jquery_update, l10n_update, lightbox2, link, location, media_youtube, migrate, nodewords, page_title, print, references, restws, strongarm, transliteration, uuid, wysiwyg.
• Stopped at Drupal 8/9 (11) — admin_menu, date, entityreference, media, menu_attributes, mollom, picture, profile2, special_menu_items, ubercart, views.
• Only a pre-release for Drupal 10/11 (11) — boost, calendar, conditional_fields, context, filefield_sources, fivestar, nice_menus, nodeaccess, services, varnish, votingapi.
• Stable release for Drupal 10, but nobody is maintaining it (2) — ckeditor, panelizer.

What this table is not

• It is not every contributed module. It is 128 projects chosen as the ones a Drupal 7 site is most likely to have. The scanner reports anything outside this list as "not in this tool's table" rather than guessing at it, and so should you.
• It is a snapshot, dated 2026-09-26. Releases happen. Re-check anything the project depends on against drupal.org before you commit to a plan.
• A stable Drupal 11 release does not mean the upgrade is easy. It means the code exists. Your fields, your views, your files and your URLs still have to move, and the module's Drupal 11 version may configure itself nothing like its Drupal 7 version did.
• The status is derived, not editorial. A dev snapshot that has run in production for three years reads here as "only a pre-release", because that is what it is. Whether that is acceptable is your call, not this table's.

Next: what is in your codebase

This table answers the question for a module you already know you have. Finding out what you have — including the custom code, the fields, the entity types, the URL and file handling and the permissions that no module list will tell you about — is what the free scanner does, offline, in one file with no dependencies.

Get the free scanner

It prints these same 128 rows for the modules it finds, flags the ones needing a decision, and links each finding to the matching section of the free Drupal 7 migration kickoff checklist.