Drupal readiness
Know what your Drupal transition needs.
Assess the compatibility, content and integration risks before committing to an upgrade or migration. The Drupal 11 Readiness Audit gives your team a clearer basis for implementation, testing and cutover.
A supported path starts with the current site.
Drupal 7 reached community end of life on January 5, 2025. Drupal 8 and Drupal 9 are also unsupported. A supported destination and a tested transition plan matter more than a version-number swap.
Drupal 7 requires migration of content and configuration, with evaluation of custom functionality. Drupal 8 and 9 sites need a supported sequential upgrade path through Drupal 10 before Drupal 11. Drupal 11 requires at least Drupal 10.3 as the starting point; modules, themes, custom code, PHP and database requirements must also be compatible.
What the audit examines.
Code and dependencies
Inventory contributed and custom modules, themes and Composer dependencies. Identify deprecated code, compatibility gaps and functionality that needs an alternative or custom work.
Content and publishing
Review content types, fields, taxonomy, paragraphs and editorial tasks. Identify broken or duplicated code, content relationships and items to migrate programmatically or recreate manually.
Design and integrations
Assess the existing theme and whether the scope calls for a re-theme or redesign. Review integrations, maintenance needs and the hosting/runtime requirements that shape the transition.
Preservation and release checks
Define checks for URLs, metadata, media, integrations and editorial tasks. Plan a rehearsal with backups and a tested rollback approach before cutover.
The starting version changes the work.
Drupal 8 or 9
Audit deprecated code and Composer compatibility, identify dependency issues and define the supported upgrade sequence. Use those findings to estimate implementation and testing effort.
Drupal 7
Review the site’s functionality, entity types, content structure and theme. Map migration candidates, identify manual recreation where appropriate, and evaluate replacements for custom or unavailable contributed modules. This is a migration assessment, with effort determined by the actual site.
A report your team can act on.
Receive a prioritized list of findings, recommended actions and associated effort estimates. The report explains the dependencies, content and URL preservation checks, implementation sequence and tests needed before release.
We present the findings, answer questions and discuss next steps. The assessment informs a separately agreed implementation plan; it does not promise a direct or effortless upgrade.
Agree the scope before work begins.
Discuss your Drupal readiness audit. We will agree the audit scope and fee with you before work begins. Migration and implementation are scoped separately.
For design, development, integrations and ongoing care, explore our Drupal expertise.