WHY LEAVE
Why people leave Drupal.
And when it's time.
Drupal can do a lot, but it needs a developer who knows it. Once your version gets old, an upgrade costs almost as much as a new site.
End of support
Drupal 7 reached end of life on 5 January 2025, Drupal 10 does on 9 December 2026. Security fixes for Drupal 7 now come only from paid third-party services.
An upgrade is a rebuild
You don't get from Drupal 7 to 10 or 11 with an update. The content gets migrated, and the theme and custom modules are written again.
Modules with no successor
Some Drupal 7 modules have no version for newer Drupal. Field collection, older translation modules or your own custom modules need a replacement.
A complicated admin
Nodes, blocks, views and permissions. Editors often don't know where to change the text on the homepage.
Old PHP and hosting
Older Drupal and its modules often don't run on current PHP. Sooner or later, your host stops offering the old version.
Few people who know it
There aren't many developers who understand Drupal. Every change waits until one of them has time.
MIGRATION TARGET
Where to from Drupal?
Depends on who runs the site.
Not sure? I'll recommend one after an audit.
WHAT CARRIES OVER
What carries over.
And what replaces the modules.
I pull the content out of Drupal, from the database or through the API, and move it into the new structure. Here's where everything goes.
| DRUPAL | WEBFLOW | SANITY CMS |
|---|---|---|
| Nodes (articles, news) | CMS collections | Documents in Sanity |
| Basic pages | Pages and templates | Pages built from blocks |
| Taxonomies | Reference fields in the CMS | References between documents |
| Files and media | Assets, compressed | Sanity media library |
| Metatag and URL aliases | Title, description, OG, canonical URL | The same fields on every document |
| Webform | Webflow forms | Forms connected to your system |
| Content types, fields and Paragraphs | CMS collections with custom fields | Content schema in Sanity |
| Users, roles and comments | Not migrated, handled separately | Not migrated, handled separately |
What replaces the add-ons
| MODULE | WEBFLOW | SANITY CMS |
|---|---|---|
| Metatag, Pathauto | SEO settings and fields in Webflow CMS | SEO fields in Sanity, metadata in Astro |
| Content Translation, i18n | Webflow Localization | Language versions in Sanity and Astro |
| Views | CMS lists and filtering through an extension | Sanity queries and filters in website code |
| Webform | Webflow forms with integrations | Custom forms with storage and integrations |
| Paragraphs, Field collection | Components and the Webflow visual editor | Pages assembled from prepared blocks in Sanity |
| Core and module security updates | Managed Webflow hosting | Separate Sanity CMS and managed website hosting |
PROCESS
How a Drupal migration works.
From export to rank monitoring.
Drupal audit
I crawl the whole site, go through the database and list the content types, taxonomies, modules, languages and URLs.
URL map and redirects
/node/ and /taxonomy/term/ URLs and old aliases become clean new URLs, each with a 301 redirect.
Content conversion and cleanup
I move content from fields, Paragraphs and old HTML into a clean structure, with no inline styles or embedded code.
Your content review
You go through the site in a dedicated feedback tool. You leave comments right on the page, and I fix them.
Launch
I switch the domain, check redirects, forms and analytics, and submit the new sitemap. You keep a backup of your Drupal site and its database.
Post-launch monitoring
I watch Search Console and traffic. Whatever shows up after launch, I fix.
Send me your site's URL. I'll tell you what it takes.
I'll go through your site, modules and content types and suggest whether to move to Webflow or go custom. No commitment, no sales pitch.
STATUS:OPEN FOR PROJECTS· REPLY WITHIN 2 DAYS· NO COMMITMENT
FAQ
What people ask
about leaving Drupal.
Isn't upgrading to Drupal 11 enough?
From Drupal 10, yes, that's a regular update. From Drupal 7, though, the path goes through a content migration, a new theme and replacement modules. That's about as much work as a new site, so it's worth comparing whether to stay on Drupal at all.
Will nodes, taxonomies and old URLs carry over?
Yes. I pull the content from the database, move it into the new structure and redirect every old URL, including /node/123 and aliases, to its new one with a 301.
What happens to the modules we use now?
I go through every one. Most get replaced by what Webflow or Sanity does natively, some get connected to an external service, and some you won't need at all.
Our site is in several languages. Can it be migrated?
Yes. I move the language versions into Webflow Localization or into a multilingual schema in Sanity. Language URLs and hreflang get set up again.
We have users with roles. Do they carry over?
Editor accounts and their permissions get set up again in the new system. Public registration or a members' area is handled separately, because neither Webflow nor Sanity runs that on its own.
Will our editors have to learn a new system?
A little, but less than with Drupal. Webflow and Sanity both have a simpler admin, and I name the fields so it's clear what goes where.
Does Drupal have to go offline during the migration?
No. Drupal keeps running until you approve the new site. Anything published in the meantime gets synced before launch.
DIDN'T FIND YOUR ANSWER? .
MORE PLATFORMS