Custom module audit before Drupal migration
Drupal core has a documented upgrade path. The real project risk often lives in custom modules that have become critical to the business over the years.
What to look for in custom code
Drupal update documentation describes the general path, but custom modules must be reviewed project by project.
An audit should check:
- whether the module uses deprecated APIs;
- which hooks and services are critical;
- whether the data model is documented;
- whether the module depends on an old contrib module;
- whether the feature can be replaced by standard Drupal functionality.
How this helps estimation
When the state of custom code is known, migration becomes a set of decisions: what to port, what to rewrite and what is no longer needed. This reduces the chance that developers discover major risk in the middle of the work.
WebPro reviews custom modules as part of audit and testing. If code needs redesign, the work moves into a custom Drupal development or migration plan.
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.