A successful scan cannot tell you whether an editor can still complete your organization’s particular approval process. Someone needs to exercise that workflow.That answer is often more valuable than an immediate estimate.The practical concern is straightforward. Code that quietly handles an important form, integration, or publishing rule needs to keep doing its job when the underlying software changes.
What is changing with Drupal .module files?
Execution order is one example of why details matter. Drupal provides explicit hook-ordering options, including running an implementation before or after another module. Where custom behavior depends on that sequence, developers need to preserve it during conversion. Source: hook ordering documentation.Schedule the remaining work. Give each item an owner and a place in the maintenance backlog. Revisit progress alongside Drupal upgrade planning.This approach can make dependencies more explicit and help developers organize and test responsibilities separately. Those are opportunities for better maintenance; the quality of the implementation still matters.
Are Drupal modules and hooks going away?
Tools can assist, but review remains necessary.Has your team started moving Drupal hooks into classes, or is this still on the future-upgrade list? What is the biggest obstacle: time, older-version compatibility, or understanding what the existing code does?“Deprecated” means developers should move away from an approach because support is scheduled to end. It does not mean the functionality suddenly disappears when the deprecation begins.A clear assessment makes it easier to judge scope, budget, and timing. It also gives the next developer something better to work from than a mysterious function and a comment saying “temporary fix.”Inventory the custom behavior. List the forms, publishing rules, integrations, and other features that depend on custom code. Record their purpose and owner.
When does this happen?
Start with a contained change. Choose a small area that is easy to verify. Review the conversion before repeating the approach elsewhere.
| Milestone | What website teams should know |
|---|---|
| Drupal 11.5 | The published change record targets this version for .module deprecation. |
| Week of December 7, 2026 | Drupal 11.5.0 and Drupal 12.0.0 are scheduled for release. |
| Drupal 13 | Automatic loading of .module files ends. Its release planning currently targets 2028. |
Modules remain part of Drupal. So do hooks—the mechanisms that let custom code respond to or modify Drupal’s behavior.For broader upgrade planning, Upgrade Status checks a site’s environment and components for compatibility with the next major Drupal version. It can identify deprecated API usage, but it does not directly fix those issues. Its findings are a useful input to an upgrade plan, not a guarantee that every behavior has been verified. Source: Upgrade Status.
Which parts of a website need attention?
The conversion depends on what each function does.
| Area | Practical next step |
|---|---|
| Community-contributed modules | Review maintained releases, compatibility information, and relevant project issues. |
| Custom modules | Assign someone to inspect the code and identify the required changes. |
| Custom themes | Include theme-specific PHP logic in the review. |
| Integrations and shared helpers | Identify other code that depends on the functions being changed. |
Imagine two modules changing the same form. If the second modification assumes the first has already happened, moving the code successfully is only half the job. The resulting form still needs to behave correctly.Drupal’s conversion guide links to automation for moving hooks into classes and explicitly notes that it can miss functions. Treat the generated changes as work to inspect and test. Source: Drupal’s conversion guide.These are published plans, and release timing can change. On October 9, the .module deprecation itself was still in review in Drupal core, so confirm it in the 11.5.0 release notes. Check the Drupal core release schedule and Drupal 13 planning issue when setting project deadlines.
Why this is more than renaming a file
Test meaningful outcomes. Check submissions, permissions, content updates, notifications, and integrations affected by the changed code. Include both ordinary use and error conditions.The official guidance distinguishes between ordinary hooks, helper functions, and other procedural functions. It also identifies special cases, including requirements checks, initial template preprocessing, and hook ordering. Public functions used by other projects may need a compatibility layer while callers transition. Source: conversion requirements.If you have managed a Drupal website for a while, you may have heard a developer mention a .module file. You probably did not expect that file extension to become news.Share your experience in the comments.Our recommendation is to make this part of a staged maintenance plan.Drupal has supported object-oriented hook implementations since Drupal 11.1. Developers can place these implementations in classes, typically under src/Hook, and identify them using the #[Hook] attribute. Drupal automatically registers these classes as autowired services. Source: object-oriented hook support.As of October 9, 2026, the relevant milestones are:A useful first question for your development partner is: “Which custom modules and theme functions do we own, and who is responsible for updating them?”
How to prepare without creating unnecessary disruption
For example, a module might use a hook to adjust a form. Traditionally, developers could implement that hook as a specially named function inside a .module file.Themes deserve attention because Drupal has separately deprecated .theme files for 11.5, with automatic loading also scheduled to end in Drupal 13. The replacement guidance covers hook classes and helper methods, but themes have different service limitations from modules. Developers should follow the theme-specific instructions. Source: .theme deprecation record.Start by identifying who maintains each part of your website.For website owners, this creates a maintenance task to plan and budget for. Deleting files because their names appear in a deprecation notice would be a particularly adventurous interpretation of housekeeping.In everyday language, the code gets a more structured home.There is a more immediate consideration for organizations still using Drupal 10: its end of life is scheduled for December 9, 2026. Keeping the site on a supported version should take priority over treating this particular file conversion as a standalone project. Source: Drupal’s support schedule.Ask for a short assessment covering three things:
What should you ask your Drupal team now?
The aim is to understand and distribute the work while there is time to make careful decisions.
- Which custom modules and themes need review?
- Which changes can fit into regular maintenance?
- Which dependencies or workflows need more extensive testing?
Agree on supported versions. A module used only on your current site may have different compatibility needs from a public module serving many organizations.Yet a change to this familiar part of Drupal raises a useful question: how much of your website’s custom behavior is ready for the next generation of the platform?Drupal’s published change record identifies Drupal 11.5.0 as the version introducing .module file deprecation. Drupal 13 will stop automatically loading those files. Functions inside them need appropriate object-oriented replacements. Source: Drupal’s official change record.
