Drupal 7 reached its official end of life on 5 January 2025. Sites still running it no longer receive community security releases, and every month on an unsupported platform adds risk. The good news: a well-planned migration is also the best opportunity in years to clean up content, architecture and editorial experience.
Phase 1: Audit before you move anything
- Content inventory: list every content type, field, taxonomy, user role and the volume of each. Flag what is obsolete.
- Module inventory: map each contributed and custom Drupal 7 module to a Drupal 11 equivalent, a core feature, or a rewrite.
- Integrations: SSO, CRMs, payment gateways, search, feeds and APIs that the site consumes or exposes.
- URLs and SEO: export all path aliases and high-traffic URLs; they become your redirect plan.
Phase 2: Map the target architecture
Do not recreate Drupal 7 in Drupal 11. Consolidate near-duplicate content types, replace field collections with Paragraphs or structured entities, and design front-end components as Single Directory Components so editors get a consistent, reusable library from day one.
Phase 3: Build migrations with the Migrate API
Drupal's Migrate API (with contributed modules such as Migrate Plus and Migrate Tools) lets you define each migration as configuration: a source, a chain of process plugins and a destination. A simplified article migration might look like this:
id: d7_article
label: 'Articles from Drupal 7'
source:
plugin: d7_node
node_type: article
process:
title: title
body/value: body/0/value
body/format:
plugin: default_value
default_value: basic_html
field_tags:
plugin: migration_lookup
migration: d7_tags
source: field_tags
uid:
plugin: default_value
default_value: 1
destination:
plugin: 'entity:node'
default_bundle: article
migration_dependencies:
required:
- d7_tags
Run, roll back and re-run migrations as often as needed:
drush migrate:status
drush migrate:import d7_article --update
drush migrate:rollback d7_article
Phase 4: Validate continuously
Treat migration as a repeatable pipeline, not a one-off event. After every run, automated checks should compare record counts, sample field values, file references and URL aliases between source and destination. Continuous QA validation is what turns a risky cut-over into a routine deployment.
Phase 5: Launch with a safety net
- Freeze content on Drupal 7, or plan a final delta migration with
--update. - Deploy 301 redirects for every changed URL and resubmit your XML sitemap.
- Warm caches (Varnish or CDN) before switching DNS.
- Monitor 404s, Core Web Vitals and search console coverage for the first weeks.
The short version
Audit ruthlessly, redesign the architecture instead of copying it, script every migration, validate after every run and launch with redirects ready. Our data migration and Drupal development teams run this process end to end. Talk to us about your Drupal 7 estate.