
Multiple Studios
Multiple Studios configured for different teams, each with its own schema and workflows.
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.
The problem
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.
New layouts, content types and campaign pages wait in the development queue.
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
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.
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.
Editors build pages from approved blocks in Sanity Studio, with live preview, scheduling and roles.
We audit what you have, then design a content model for how you publish now. You keep what matters and leave the clutter behind.
Every Drupal path alias is mapped to its new URL and redirected, metadata is carried over, and rankings are monitored after launch.
Powerful features for content teams

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

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

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

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

Tasks with deadlines and assignments. Track review work where the content lives.
The services we bundle together to move a Drupal site to Sanity.
How it works
The people you meet in discovery are the people who move your site.
Audit your Drupal content, modules, integrations and analytics. Talk to the people who publish.
Map content types, fields and taxonomies to a new Sanity content model, and agree what moves, what merges and what retires.
Design system, Studio and Next.js front end, built in sprints you can review.
Scripted content migration, a redirect for every URL, and SEO and tracking checked before go-live.
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.

Conservation International's website had become too focused on the organisation itself. We rebuilt it around storytelling that puts donors and impact first, across three areas people already care about: oceans, climate and biodiversity.

Reimagining how conservation data is designed, delivered and used at scale.

Too Good To Go's website was not converting B2B customers to join the fight against food waste: a legacy CMS, outdated information architecture and poor performance were holding it back.

A fresh brand and a new digital home for a global property portfolio.
Sanity CMSIn this article, I'll walk you through the most common Sanity implementation issues we encounter, explain why they happen, and share how we fix them. No jargon, no unnecessary complexity. Just practical solutions for issue I've solved dozens of times before.
Sanity CMSThis article is going to help you figure out which CMS pairs best with React - Headless CMSs, Hybrid setups, or Traditional options - and what you should actually care about when choosing one.
Sanity CMSWe're experts in WordPress Migrations. Find out what a modern editing experience feels like. Let's migrate you to SanityCMS.
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.
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.
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.
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.
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.
Yes. Sanity supports translated content at field or document level, and we choose the approach that fits how your team works.
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.
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.
Get in touch to see how this could work for you.