Skip to content

Drupal to Sanity migration

For organisations running a large Drupal site that has become hard to change. We plan and run the move to Sanity end to end, from content model to launch, so your team keeps its content and its search rankings, and publishes without waiting on developers.

  • Sanity partner logo
  • Vercel partner logo

The problem

Drupal is getting harder to live with

  1. Upgrades turn into rebuilds

    Each major Drupal version brings another round of module updates, custom code fixes and testing. Drupal 7 has had no community security support since January 2025.

  2. Every change needs a developer

    New layouts, content types and campaign pages wait in the development queue.

  3. Content is stuck in the old structure

    Years of content types, fields, Paragraphs and Views make the site hard to reshape, and hard for search engines and AI tools to read.

What you get

A faster site your team can run themselves

We move your content into Sanity, rebuild the front end on Next.js and Vercel, and set up the Studio around how your team publishes.

  • No core CMS to patch

    Sanity's content platform is hosted and kept up to date by Sanity, so there is no Drupal core or module stack to upgrade on your own servers.

  • Publish without developers

    Editors build pages from approved blocks in Sanity Studio, with live preview, scheduling and roles.

  • Content rebuilt around your team

    We audit what you have, then design a content model for how you publish now. You keep what matters and leave the clutter behind.

  • Search rankings kept

    Every Drupal path alias is mapped to its new URL and redirected, metadata is carried over, and rankings are monitored after launch.

Sanity Editorial Features

Powerful features for content teams

  • A stack of Studios for different teams, from Retail Group to Global Enterprise, above one Studio's content list

    Multiple Studios

    Multiple Studios configured for different teams, each with its own schema and workflows.

  • A comment thread on an image crop field in Sanity Studio, with a reaction and a reply box

    Inline Comments

    Inline comments on any field. Review images, leave feedback, and resolve without leaving Studio.

  • Text editor showing a collaborator's live cursor and a review panel crediting a word change to another editor

    Multiplayer Editing

    Real-time multiplayer editing. See who's changing what, field by field, as it happens.

  • A scheduled "Spring Release" listing documents to add, change or unpublish together

    Content Releases

    Content Releases: bundle changes across documents. Preview together, publish on schedule.

  • New task form with an assignee and a deadline field, its calendar picker open on May 2026

    Tasks

    Tasks with deadlines and assignments. Track review work where the content lives.

How it works

Five stages, one senior team

The people you meet in discovery are the people who move your site.

  1. Discover

    Audit your Drupal content, modules, integrations and analytics. Talk to the people who publish.

  2. Model

    Map content types, fields and taxonomies to a new Sanity content model, and agree what moves, what merges and what retires.

  3. Build

    Design system, Studio and Next.js front end, built in sprints you can review.

  4. Migrate and launch

    Scripted content migration, a redirect for every URL, and SEO and tracking checked before go-live.

  5. Grow

    Support, optimisation and new features once you are live.

Drupal to Sanity projects typically start from £80k + VAT. We'll give you a timeline after the first call.

Talk to us about yours

Relevant case studies

Frequently asked questions

Why move from Drupal to Sanity?

Sanity keeps your content as structured data on a hosted platform, with an editing studio shaped around your team. There is no core CMS to patch, editors build pages themselves, and the same content can feed your website, apps and AI tools.

Will we lose our search rankings?

We map every Drupal path alias to its new URL, set up redirects, carry over metadata and structured data, and monitor rankings after launch. Redirects are planned from the first week, because a missed one costs rankings that took years to earn.

Can our content move across automatically?

Most of it. After the content audit we write migration scripts that move content, media and files into the new model, and your team reviews what comes across. Content that needs rewriting or merging is flagged in the audit, so it is dealt with before launch.

What happens to our content types, Paragraphs and Views?

Content types become Sanity document types, Paragraphs become modular blocks your editors arrange, taxonomies become references, and Views become queries in the front end. We map each one in the Model stage.

What about our modules and integrations?

We list every module and integration in discovery and decide what each becomes: a feature of Sanity or Next.js, a connected service, or something you no longer need.

Can we keep multiple languages?

Yes. Sanity supports translated content at field or document level, and we choose the approach that fits how your team works.

Do we have to redesign at the same time?

No. We can rebuild your current design on the new platform, or redesign as part of the move. Many teams use the migration to fix what is not working.

How much does a Drupal migration cost?

Projects typically start from £80k + VAT. The final figure depends on the number of templates, the amount of content and the integrations you need. We'll give you a range after a short call.

Let's talk about your project

Get in touch to see how this could work for you.