Drupal 7 Migration Estimator
Estimate the work needed to migrate a Drupal 7 site to Drupal 11: content types, modules, theme, languages, integrations. Range in days of work and details of the calculation.
100% local processing — nothing leaves your browser.Learn more
Estimate of the migration to Drupal 11
Order of magnitude for a team used to Drupal, including acceptance testing and go-live.
Details of the calculation
| Estimated total |
|---|
The range goes from 80% to 130% of this total: the real state of the code and data changes the effort.
Indicative estimate, calculated in your browser from averages: only an audit of the code and database gives a reliable quote.
Go further
Your Drupal site is no longer maintained
Without security fixes, every newly found vulnerability stays open. DG Tech, the Drupal business of Youtilz's publisher, audits your site and prepares its migration to a supported version.
Ask DG Tech for a migration audit (opens in a new tab)Service in French.
How Much Work Does It Take to Leave Drupal 7?
Drupal 7 has not received security fixes since January 5, 2025. For a site still on Drupal 7, the question is no longer whether to migrate, but how much it will cost.
The Drupal 7 migration estimator gives an order of magnitude in days of work, based on a few questions about your site. The calculation runs in your browser and its details are shown: nothing is sent unless you request a detailed estimate.
How to Use
- Count the content types and views in the Structure menu of your Drupal 7 site
- Note the number of contributed modules and custom modules on the Modules page
- Enter the type of theme, the languages, the volume of content and the integrations
- The estimate updates with each answer; expand "Details of the calculation" to see each item
Why a Migration, Not an Upgrade
Drupal 8 was rewritten on top of Symfony components: between Drupal 7 and Drupal 8 and later, the architecture, the module API and the theme engine (Twig) changed. So a Drupal 7 site is not upgraded: you build a new site and migrate the content into it.
What Gets Migrated
Content, users, taxonomies, files and part of the configuration go through the Migrate API in Drupal core, which handles the mappings between the old site and the new one.
What Gets Rebuilt
The theme (rewritten in Twig), custom modules (hooks partly replaced by services and plugins) and contributed modules with no direct equivalent.
How the Estimate Is Calculated
Each answer adds a number of days, based on the following averages:
- a base of 5 days for the new site: installation, configuration, acceptance testing and go-live;
- half a day per content type, a quarter of a day per view, a fifth of a day per contributed module;
- 3 days per custom module to rewrite and per external integration;
- 5 days for a contributed theme, 12 for a custom theme;
- extra time for a multilingual setup, the volume of content, an online shop or a members area.
The range shown goes from 80% to 130% of the total, to account for the actual state of the code and data. The target is Drupal 11: security support for Drupal 10 ends on December 9, 2026.
Before You Start the Migration
- Take an inventory of the modules: which ones are still used, which ones have an equivalent in Drupal 11, which ones have moved into core.
- Use the opportunity to delete content, fields and views that are no longer used: every item removed makes the migration smaller.
- Check the PHP version of your hosting: Drupal 11 requires at least PHP 8.3.
- Check the exact version of your site with the Drupal version detector.
Limitations
- This is an order of magnitude: the quality of the custom code, the consistency of the data and the redesign choices greatly affect the effort.
- The estimate does not include a new graphic design, content writing or hosting.
- A reliable quote requires an audit of the code and of a copy of the database.