Drupal 10 reaches end of life on December 9, 2026. This is the full playbook for deciding whether to upgrade or move, and for running the migration of a 300-page site in 8 languages without losing a year of search traffic.
If you run a large Drupal site, the end-of-life date means a major project is coming either way. The question is whether to spend that budget on another upgrade or on a platform your editors and developers will both be faster on.
This paper is the honest version of that decision, including the cases where staying on Drupal is the right answer. It is written for marketing and engineering leaders evaluating the move, and for the agency or in-house team that would run it.
The business case: what the next Drupal upgrade actually costs against a replatform, and the conditions under which staying put is the cheaper answer.
Content modeling: turning a decade of Drupal nodes, paragraphs and taxonomy into document types, references and Portable Text.
Localization for 8 languages: document-level against field-level translation, and the out-of-date-translation signal Sanity does not give you by default.
Migration scripts: extracting through JSON:API, converting WYSIWYG HTML to Portable Text, and keeping runs idempotent so you can repeat them.
SEO preservation: the redirect map, metadata parity, hreflang, and the automated tests to run before cutover.
The cutover runbook and a 47-question agency handoff checklist covering ownership, migration integrity, security, documentation and costs.
It also covers working on a Sanity project with the official MCP server and Claude Code, including the guardrails to put around an agent that can write to your content.
Prefer the short version first? The summary is on the blog.
We build Sanity sites with Next.js front ends for teams that need structured content and multiple languages. Bring us the Drupal site and we'll tell you plainly whether a move makes sense.
Explore Sanity CMS