Drupal7EndofLife:TheCompleteMigrationPlaybookfor2026

Drupal 7 reached official end of life on January 5, 2025. If you're reading this in 2026 and still running Drupal 7, your site is no longer receiving security patches from the Drupal Security Team or the official D7 Extended Support partners. This guide is the playbook.

We've migrated dozens of Drupal 7 sites — to Drupal 10, to Drupal 11, to WordPress, and in two cases to headless architectures with Drupal as a content API. The right path depends on the site's content model, editorial workflow, integrations, and budget. Below is how to think about it.

What end of life actually means in 2026

Drupal 7 EOL means three things:

1. No security patches from the Drupal Security Team, the official Drupal.org D7 Vendor Extended Support program, or any commercial extended support tier.
2. No PHP version support — D7 was never officially compatible with PHP 8.3+, and modern hosting providers are sunsetting older PHP versions.
3. No module maintenance. The contributed module ecosystem has moved on. Any module bug or compatibility issue is now your team's problem to fix.

The practical risk in 2026: unpatched CVEs, hosting providers refusing to renew, payment processors and SSO partners requiring TLS and PHP versions D7 can't support, and accessibility regressions that legal counsel will flag.

Your four migration options

/Option 1: Drupal 7 → Drupal 10 or 11

Best for: Sites with complex content models, robust editorial workflows, hundreds of users, or government / higher-education accessibility requirements.

What it really is: A rebuild, not an upgrade. Drupal 8+ is a different architecture (Symfony-based). You migrate content, but theme, custom modules, and views must be rebuilt.

Realistic timeline: 12–24 weeks for a typical 200–500-page site. Longer for multi-site or multilingual.

Realistic budget: $60K–$250K depending on content volume, integrations, and accessibility scope.

When this is the right call: You have an editorial team trained on Drupal, complex taxonomy or workflow needs, Section 508 / AODA / WCAG requirements, or integrations with SSO, CRMs, or research databases that already have Drupal modules.

/Option 2: Drupal 7 → WordPress

Best for: Marketing sites, brochure sites, and editorial sites where Drupal's complexity exceeded the actual content needs.

What it really is: A platform switch. Content migrates cleanly via WP All Import + a content-mapping spreadsheet; URL structure is preserved with redirects; editorial workflow gets simpler.

Realistic timeline: 8–16 weeks for a typical 100–300-page site.

Realistic budget: $30K–$120K.

When this is the right call: Editorial team prefers a simpler authoring experience, the original Drupal install was over-engineered, marketing now owns the site (not IT), or you need WooCommerce / a richer plugin ecosystem.

For the full WordPress-side playbook see Drupal to WordPress migration guide.

/Option 3: Drupal 7 → Headless (Drupal 10 + React or Next.js)

Best for: Brands where the front-end performance budget or product surface justifies decoupling.

What it really is: Drupal becomes a content API; the visitor-facing site is a React / Next.js / Astro front-end. Editorial keeps Drupal; visitors get a modern app.

Realistic timeline: 16–28 weeks.

Realistic budget: $100K–$400K.

When this is the right call: You need sub-second page loads for SEO or AEO, you're shipping a product surface alongside marketing content, or you have a front-end team that already knows React.

/Option 4: Stay on Drupal 7 (paid extended support)

Honest answer: Not viable as of 2026. The official D7 Vendor Extended Support program ended February 2025. Any vendor selling "D7 forever" support today is selling you a patching service with limited security depth. Treat this as a 6-month bridge, not a strategy.

The migration timeline — what actually happens

A typical Drupal 7 → Drupal 10 or WordPress engagement breaks into seven phases:

1. Audit (1–2 weeks) — content inventory, module inventory, integration map, URL list, analytics baseline, current LLM citation list.
2. Content modeling (1–2 weeks) — map D7 content types and fields to the new platform's structure.
3. Design and IA (2–4 weeks) — refresh navigation, templates, and design system.
4. Build (6–12 weeks) — theme, components, integrations, custom modules / plugins.
5. Content migration (2–4 weeks, parallel to build) — automated import, manual cleanup, redirects.
6. QA and accessibility audit (2–3 weeks) — WCAG 2.2 AA testing, regression, performance.
7. Cutover and post-launch monitoring (2 weeks) — DNS swap, 301 verification, GSC and analytics monitoring, LLM citation re-baselining.

Parallel to all of this, the marketing team should be republishing flagship content with AEO-shaped structure (question-as-H2, definition-first answers, FAQ schema) so the migration doubles as a content upgrade.

What you must preserve to keep SEO and AI citations

The single biggest mistake in a Drupal 7 migration: shipping new URLs without 301 redirects. The second biggest: failing to baseline LLM citations before cutover, so nobody notices when ChatGPT stops citing you for the queries that mattered.

A migration that preserves rankings ships:

• A complete 301 redirect map from every old D7 URL to its new equivalent. Verify with a crawler before cutover.
• Identical or improved page titles and H1s on flagship pages.
• Preserved or upgraded schema markup — Organization, Article, FAQ, BreadcrumbList.
• Refreshed `llms.txt` and `llms-full.txt` pointing to the new URLs.
• A pre- and post-launch LLM citation baseline across ChatGPT, Perplexity, and Gemini for the top 20 queries you currently rank for.

Cost, plainly

For a 200–500-page Drupal 7 site in 2026:

• Lift-and-shift to Drupal 10: $80K–$180K with a senior agency.
• Replatform to WordPress: $40K–$120K with a senior agency.
• Replatform to headless: $150K–$350K.

Anything significantly below those ranges is either a junior team or a scope that will balloon mid-project.

Who should run the migration

A senior agency with certified expertise on both sides of the migration. For Drupal-to-WordPress, that means a Drupal Association partner AND a WP Engine partner. For Drupal-to-Drupal, an Acquia partner with a published D10/D11 portfolio. Avoid generalist agencies that have done one or two D7 migrations — the migration playbook compounds with reps.

DoodleWeb is one of a small number of Seattle-area agencies certified on both stacks: Drupal Association Bronze Partner, Acquia Community Partner, and WP Engine Advanced Agency Partner. See the Drupal 7 to 10 migration page and the Drupal to WordPress page for our delivery model.

Start with a free Drupal 7 readiness audit

Before you commit to a path, get a readiness audit. A good audit covers content inventory, module risk, integration risk, accessibility risk, SEO baseline, and current LLM citation list. We offer this for free — book a discovery call or request a free website audit report.