A 52-step, seven-phase checklist Gspikes uses for every Drupal 7 migration to Drupal 10/11. Covers audit, content model, module mapping, 301 mapping, build, verification, and a rollback-friendly cutover.
Treat the migration as a sequence of 52 discrete decisions across seven phases so nothing is missed.
Redirect discipline and a complete crawl of every legacy URL are essential to preserve search rankings.
Before going all-in, I led SEO at Chain Reaction — one of the region's largest digital agencies — and shipped production code at Orange and Forbes. LinkedIn Last updated · September 2026 Roughly 30% of the Drupal web still runs Drupal 7 — nineteen months past end of life. Every step on this list earned its place by being skipped on some site we were later called to rescue.
It's long because migrations fail in the details — but each step is one decision, and none of them is mysterious. First, this checklist is platform-agnostic about your destination version: if you're still choosing between Drupal 10 and 11, that decision has its own guide — for most sites migrating in 2026, go straight to 11. Second, the summary card below is free to print, share, and reuse with attribution.
This is the checklist we run on every Drupal 7 → 10/11 migration. Fifty-two steps, seven phases, in the order we actually do them. Print it, pin it next to the migration board.
The 52-step checklist tells you what to do. This is the calendar those steps actually run against — a realistic 90-day plan broken into three phases, with the milestones that decide whether you finish on time and the resourcing map showing who's busy when.
Drupal 11 is on 36% of reporting Drupal sites — and climbing at roughly half the speed Drupal 10 managed at the same age. On 9 December 2026 Drupal 10 reaches end of life, and the share of the Drupal web running unsupported code nearly triples overnight. The live numbers, the method, and what the curve actually says. U
Joomla 3 has been unsupported since 2023. An honest look at the three destinations — Joomla 5, WordPress or Drupal — what actually breaks, and what it costs.
Most articles with this title are written by Drupal shops. We build on both platforms, so here is the honest version: the four situations where Drupal genuinely wins, what actually moves versus what gets rebuilt, and why most WordPress sites should stay where they are.
We measured server response time on all 424 Drupal sites in the US federal and state .gov registry. Pantheon vs Acquia, CDN tails, and 12 sites on unsupported Drupal.
Open the app view to save this story, compare related coverage, and continue from the same source.