How to Plan a Drupal Migration to Drupal 11 Without Losing Content or SEO

We cannot treat a Drupal Migration as a simple technology upgrade. Over the years, the platform has evolved into a broad strategic operation that influences digital results, integration stability, governance, SEO, security, and long-term scalability.

Organizations operating in complex environments, high content volume, multiple workflows, and critical integrations must migrate with precision and rigorous planning to avoid compromising performance, indexing, and operational continuity.

In the week of September 27, 2026, 215,404 sites were still running Drupal 10, more than were already on Drupal 11. All of them lose security support on December 9, 2026, the same week Drupal 12 ships. Drupal 7 sites are already past the deadline: official support ended on January 5, 2025. Moving off Drupal 10 is an upgrade; moving off Drupal 7 is a full migration to a new build. Both paths lead to Drupal 11.

Why Migrate Now: Drupal 7 and Drupal 10 End of Life

Proper preparation is what separates successful migrations from operations that generate rework, traffic loss, and unexpected downtime. To plan your Drupal Migration, several points are essential:

• Drupal 7 End of Life: Without official support, the platform no longer receives security fixes. Legacy systems become increasingly vulnerable, incompatible with new libraries, and harder to maintain.

• Drupal 10 End of Life: Drupal 10 stops receiving security fixes on December 9, 2026. The safe target is Drupal 11, which keeps receiving updates after Drupal 12 ships and, according to The DropTimes, is expected to be supported until around the end of 2028. Drupal 12 requires PHP 8.5 and removes from core the modules used to migrate Drupal 7 sites.

• Need for Architectural Review: Migration is the ideal moment to correct structural issues, consolidate content models, eliminate redundancies, and reorganize taxonomies.

• Infrastructure Compatible with Modern Requirements: Drupal 11 requires PHP 8.3 or later and updated, database engines, libraries, and server environments. Without these, migration is not feasible.

• SEO Preservation: Migration impacts URLs, metadata, and redirects. Without planning, a platform may lose years of organic authority.

These points sustain the entire project. Based on them, the most important phase begins: pre-migration. 

Drupal 10 to 11: An Upgrade, Not a Migration

Upgrading from Drupal 10 to Drupal 11 leaves your database, content, and URLs where they are. The work happens in the codebase: core, contributed modules, custom modules, and the theme.

The official Drupal 10 to 11 upgrade guide requires Drupal 10.3 or later and PHP 8.3 or later. The process has four steps: replace modules that were removed from core, run Upgrade Status to find and fix incompatible code, update core with Composer and run database updates with Drush, then test before you deploy.

Sites on Drupal 8 or 9 need to reach Drupal 10 first. Drupal 7 is a different path: according to the official documentation, content and configuration move to a new site, and the theme is rebuilt from scratch. That is where the steps below carry the most weight.

Step 1: Pre-Migration and Audit

Pre-migration is the foundation of the entire project. It defines the real scope, anticipates risks, maps dependencies, preserves SEO, designs the architecture, and guides every future decision. The most common error in problematic migrations is neglecting this phase or treating it as a short checklist. Pre-migration must be deep, systemic, and led by experienced specialists.

Below are the essential elements of this phase.

Module Audit: Compatibility with Drupal 10 and safe substitutions

Drupal's module ecosystem is one of its greatest strengths. However, over the years, many modules became unmaintained, deprecated, replaced, absorbed by Core, or lost relevance. A complete audit must identify:

• Compatibility of installed modules with Drupal 11

• Module status within the community

• Native alternatives within modern Core

• Associated security risks

• Impact on editorial workflows and integrations

• Custom modules that must be rewritten

• Opportunities to simplify the stack

• Hidden or poorly documented dependencies

• Modules that can be replaced by design system components or custom APIs

• Features that may evolve into decoupled architectures

In complex projects, this audit prevents the migration process from being blocked by incompatible modules or abandoned dependencies. It identifies in advance which components must be rewritten, which can be replaced with native Drupal 11 solutions, and which can evolve into a decoupled architecture, where Drupal exposes content via APIs to independent front-end interfaces. 

This evaluation reduces rework, prevents emergency rebuilds during development, and decreases long-term operational costs. Modernized modules operate using current Drupal and Symfony standards, become more predictable in testing, follow stronger security practices, and align with Core's continuous update flow, extending the platform's lifespan.

Content Architecture: Rethink to scale

Content architecture is one of the central pillars of any migration. It determines how content is created, maintained, retrieved, migrated, and related. A well-planned Drupal Migration uses this moment to correct historical issues, consolidate structures, and reorganize editorial logic.

The analysis must include:

• Inventory of all content types

• Evaluation of fields, formats, relationships, and dependencies

• Review of taxonomies and hierarchical structures

• Removal of redundancies accumulated over time

• Consolidation of similar content types

• Standardization of naming conventions

• Preparation for headless or semi-decoupled integrations

• Alignment with accessibility guidelines

• Modeling of an ecosystem prepared for years of growth

Example: A portal that has eight different content types for publications (articles, news, bulletins, updates, notices, releases, etc.) can consolidate everything into two versatile content types, adjusting taxonomies and fields for flexibility. This reduces editorial errors, improves governance, facilitates migration, and increases performance.

Technical SEO in a Drupal Migration

SEO is one of the most sensitive elements of a Drupal Migration. URLs, metadata, headings, structured markup, and sitemaps must be preserved with maximum precision. Platforms that ignore this step face traffic drops and authority loss.

SEO evaluation must include:

• Complete inventory of indexed URLs

• Performance and backlink analysis

• Preservation of titles, descriptions, and headings

• Review of navigation structure

• Maintenance of breadcrumb logic

• Mapping equivalence between old and new URLs

• Creation of a full 301 redirect set

• Analysis of pages with the highest traffic and authority

• Review of canonical tags

• Comparative crawling before and after migration

In Drupal, SEO risk concentrates in three places: URL aliases generated by Pathauto, redirects managed by the Redirect module, and metatags set per content type in Metatag. If alias patterns change on the new site, thousands of URLs change at once, and each one needs a 301 redirect. Google's site move guidance recommends keeping redirects in place for at least one year. For the full process, see our guide on how to protect organic traffic during a migration.

Tips to avoid SEO loss during migration:

Keep the current URL structure whenever possible, preserve 100% of metadata before transferring anything, apply 301 redirects while monitoring site behavior before and after launch, generate a new sitemap only after validating the entire environment, use crawling tools to monitor page behavior, and track Search Console daily for the first weeks to make quick adjustments.

Step 2: Environment and Infrastructure for Drupal 11

Migration only moves forward when the infrastructure and Core are fully prepared for Drupal 10. This stage ensures stability, compatibility, and performance.

Critical points include:

Updated environment

Drupal 11 requires PHP 8.3 or later, and Drupal 12 will require PHP 8.5, updated databases, support for new JS libraries, and modern security standards. Updates to servers, caching systems, and CDNs are essential for performance.

Complete core update

Includes revision of themes, components, libraries, accessibility, integrations, CKEditor 5, and compliance with modern security policies.

Adoption of CI/CD pipelines

Automating tests, linting, audits, and deployments reduces risks, improves quality, and guarantees predictable cycles.

Observability and advanced logs

Infrastructure modernization includes telemetry, metrics, error tracing, and event monitoring.

Step 3: Data Migration with the Migrate API

The Migrate API is Drupal's official and most powerful tool for transferring data safely, structurally, and auditably. It allows precise mapping rules, custom transformations, and integrity validation at every step.

For Drupal 7 sites, the Migrate Drupal and Migrate Drupal UI modules stay in core for the entire Drupal 11 lifecycle and are removed in Drupal 12. The migration UI was already deprecated in Drupal 11.3, which favors migrations run through Drush and version-controlled scripts.

An efficient migration includes:

• Templates for each entity

• Data normalization and cleanup

• Incremental migration to prevent data loss

• Reconciliation between the migrated and original data

• Detailed logs for each batch

• Automated reprocessing in case of failure

• Validation of complex entity relationships

• File migration with rewritten paths where needed

This approach prevents loss, duplication, inconsistencies, and silent errors, especially in platforms with large content volumes.

Step 4: QA, Editorial Validation, and Performance Testing

Testing is essential. After the technical migration, a complete verification phase ensures everything works as expected. Each stage directly impacts launch success.

Testing includes:

• Content Validation: Ensures everything migrated correctly, with no missing fields, formatting issues, broken relationships, or visual inconsistencies.

• Functional Regression Testing: Validation of modules, integrations, user permissions, editorial flows, dynamic pages, views, and components.

• Editorial Testing: The editorial team must validate usability in the new environment, CKEditor 5 behavior, previews, workflows, and access controls.

• Performance and Load Testing: Identifies bottlenecks, warms the cache, verifies behavior under heavy load, and ensures front-end and back-end stability.

• Accessibility: Verification of labels, contrast, keyboard navigation, ARIA, and WCAG 2.2 compliance.

• Post-Launch SEO: Full crawling, 301 verification, indexing checks, metadata review, and Search Console error analysis.

Migration quality depends directly on this phase.

Drupal Migration Scenarios and Risk Levels

Understanding the complexity of a Drupal Migration requires acknowledging that no project starts from the same point. Each platform carries a unique history of technical decisions, installed modules, content models, integrations, data volume, and SEO strategies. These elements create different contexts that directly impact scope, risks, and timing.

After analyzing dozens of migrations in corporate, governmental, and high-demand editorial environments, it becomes clear that success depends not only on technical updates but also on the ability to accurately map the organization's scenario.

This diagnosis guides planning, prevents rushed decisions, anticipates bottlenecks, and directs resources where they truly matter. The table below highlights the most common Drupal Migration scenarios, showing complexities, risks, SEO concerns, timeline impact, and key success factors. It helps readers quickly identify which scenario resembles their environment and what strategies are required for a stable, high-performance migration.

Consolidating multiple sites carries the highest SEO risk of any scenario. That was the challenge at Hospital Sírio-Libanês: in about five months, Dexa brought five portals running on different CMSs into a single multisite platform, migrating more than 2,000 pages through automated scripts, building 400+ new pages from reusable components, and launching with zero downtime.

Plan Your Move to Drupal 11

Dexa has worked with Drupal since 2009 and leads migrations and upgrades for enterprise portals, from the module audit through post-launch monitoring, with engineering, SEO, and editorial governance on the same team. Tell us which version you're running and talk to a specialist about the right path, the risks, and the timeline.

Talk to a Drupal specialist.

Drupal Migration FAQ