FREEFirst project with us? Your landing page design is on the house.See the offer
Booking for Q4'26

Drupal to Webflow, less to maintain.

Drupal is powerful, and that power comes with modules, updates and developer time. If your site is mainly marketing pages and a blog, you may be paying for a lot you do not use. We move the content, rebuild the design in Webflow and map every path alias.

  • Content types, fields and taxonomy mapped to Webflow collections
  • Path aliases and existing Redirect module rules carried over
  • Webforms rebuilt, and the old submissions exported for you
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Drupal move

Tell us a little. We reply within one working day with a price and timeline.

🔒 No spam. No sales calls unless you ask for one.

Got it. Thanks!

We will reply within one working day.

Trusted by founders and teams at

A Drupal to Webflow migration maps your content types, fields and taxonomy to Webflow collections, rebuilds the Twig theme in the Designer, and gives every old alias a 301 where its path changes. It suits marketing sites short on developer time. Sites with complex permissions, logged-in users or heavy integrations are often better off upgrading Drupal.

Why teams leave Drupal

An upgrade is due.
Is it worth it?

Teams often ask this when a version deadline comes up. Drupal 7 reached end of life on 5 January 2025, and Drupal.org lists 9 December 2026 as the end of life for Drupal 10. Each upgrade means checking modules and custom code, and that cost is worth questioning if your site is mostly pages and posts.

Moving to Webflow removes the patching and hosting work. It also removes a lot of power, so if you need that power, upgrading Drupal is the right answer.

Drupal 10 end of life

Drupal.org gives 9 December 2026. Sites on it need an upgrade plan or a move.

Alias and system path

Aliases and old /node paths both get checked, so links from any era still land.

Of daily checks

Search Console gets looked at each day for two weeks after launch.

From nodes to collections

What moves, and what
stays behind.

Drupal has many moving parts. Each one gets a line in the plan.

Content types and fields

Each type becomes a collection. Field collections and nested paragraphs get flattened, or built as page sections.

Twig theme

Themes do not transfer. We rebuild the design with classes, variables and components in the Designer.

Views and blocks

Lists built with Views become Collection lists with filters. Blocks become components.

Webform

Multi-step forms and conditional logic need planning. Submissions can be exported first, for your records.

Files and media

Files move to Webflow assets. Old /sites/default/files links get redirects where they matter.

Users and roles

Drupal accounts, roles and permissions have no match in Webflow. Team logins get set up again by hand.

Getting the content out

JSON:API,
then a clean-up.

Drupal has JSON:API in core, which gives a structured view of your content by entity type, with filters and paging. On older versions we may read the database or use a Views export instead.

Body fields usually hold years of editor markup. So we clean them as they come across, and we resolve taxonomy terms and media references, because the raw data has IDs rather than names. Your team then gets tidy Webflow collections rather than a copy of the old mess.

Launch checklist

Checked against
the Drupal site.

Drupal sites tend to have more URL variations than you expect, so we test more of them.

  • Aliases and system paths both resolve, including /node/ and /taxonomy/term/ forms.
  • Redirect module rules are exported and still make sense.
  • Pathauto patterns are written down and matched where Webflow allows it.
  • Each Webform submits and sends to the right place.
  • Translated pages keep their language and hreflang.
  • Taxonomy listing pages are kept, or redirected on purpose.
  • Metatag values match on page and template level.
  • Files linked from outside such as PDFs in old emails, still resolve.

What moves

Your site,
moved layer by layer.

Moving from Drupal to Webflow is more than copying pages. These are the seven layers we move, in the order we move them.

  1. 01
    Audit

    Every URL, page, form and script on your Drupal site, listed in one sheet before anything moves.

  2. 02
    Content

    Pages, posts and collections moved into Webflow, field by field, so nothing is retyped by hand.

  3. 03
    Design and build

    Pages rebuilt in Webflow as reusable components, matching the look you have or a new design.

  4. 04
    Redirects

    Every old URL gets a 301 to its new address, so old links and search results still land on the right page.

  5. 05
    SEO carried over

    Titles, descriptions, schema and image alt text move with each page.

  6. 06
    Forms and tracking

    Forms, analytics and connected tools set up again and tested before launch.

  7. 07
    Launch and watch

    DNS switched and the sitemap submitted, then we watch Search Console for errors.

Review before launch

Every template,
every screen.

Drupal sites often have more templates than anyone remembers. We check each one on staging at desktop, tablet and phone, and send you the link to look over too.

Comments go directly on the page, so nobody has to file tickets. Once each is closed and you agree, we set a launch date.

staging.fieldandclay.comStaging
Field & ClayShop
STONEWAREMade slowly. Used daily.
1Field & Clay teamCan the photo be bigger?Resolved
DesktopSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
2Field & Clay teamMenu feels crampedResolved
TabletSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
3Field & Clay teamButton text too smallResolved
MobileSigned off
Waiting for sign-off on 3 screensAll screens signed off. Checklist green.Switch domain

Drupal vs Webflow

Power against
upkeep.

Drupal does much more. The question is how much of that you need.

FeatureWebflowDrupal
Security updates and hostingHandled by the platformYours, or your developer's
Editing a layoutVisual, in the DesignerDepends on your build
Permissions and rolesEditors and designersVery fine control
Logged-in usersThird party toolsBuilt in
Custom logicCustom code and integrationsModules and your own code
Cost of upkeepA plan fee, little elseDeveloper time on top of hosting
Best forMarketing sites short on developersComplex sites with a technical team

What you get

What comes with
every Drupal move.

No add-on surprises. These come with every project.

01

Site audit

Content types, Views, modules and every URL form.

02

Redirect map

Aliases, /node paths and Redirect module rules, joined up.

03

Theme rebuild

The Twig theme redone as a Webflow system.

04

Content migration

Nodes, terms and media moved and cleaned.

05

Metatags carried over

Titles, descriptions, social images and schema.

06

Forms rebuilt

Webforms redone in Webflow or your form tool, then tested.

07

Domain move

Pointed at Webflow on a call with you. Email stays.

08

Search watch

Two weeks of daily reads, then one a week.

Our process

How a Drupal to
Webflow move runs.

A common plan for a Drupal marketing site. Larger builds take longer, and your quote will say so. Coloured bars are ours, striped bars are yours.

Drupal to Webflow · scope to launchYou

Our work

Webflow sites
we have shipped.

Try us first · Try us first · Try us first ·

Upgrade Drupal or leave it? Ask us first.

We look at your modules, your content and your URLs for free, and send a plain note. If your site really needs Drupal, we will say so.

Get my free auditFree, no strings

The guide

The Drupal to Webflow migration guide

How to take a Drupal marketing site to Webflow, and how to tell if you should.

What is a Drupal to Webflow migration?

You leave a self-managed open source CMS for a managed visual platform. Your content moves into Webflow collections, your design is rebuilt, and your old paths are redirected. Hosting, updates and SSL then belong to Webflow.

There is no one-click route. The move is mapped and carried out by hand, with scripts for the content.

When staying on Drupal is the better call

  • You need fine control of roles, permissions and editorial approval
  • Members or staff log in to the site
  • Custom modules connect it to systems you depend on
  • It serves many sites or languages from one install
  • You have a Drupal team who keep it healthy

Then upgrade, and do not move. Read Webflow vs Drupal for the full picture.

Auditing modules and content

We read the module list first, as it tells you what the site really does. Most marketing sites use a small part of what is installed. Whatever is in use, such as search, forms or translations, needs a home in the new setup.

Next we map each content type and field to a collection, and decide what happens to paragraphs and field collections. Deep nesting usually gets simplified, because Webflow has plan limits on references and nested lists.

Getting content out of Drupal

The JSON:API module is part of core and exposes entities with filtering, includes and paging, so it suits modern versions. For older sites we might use a Views export or read the database. Files are pulled separately.

Editor markup gets cleaned as it moves, and Webflow removes elements it does not support when it imports rich text. So we check a sample of old posts by eye.

Forms and logged-in features

The Webform module offers multi-step forms, conditional logic and stored submissions, and it can export them. Save those exports first. Then we rebuild simple forms in Webflow, and use a form tool for the complex ones.

If members log in today, plan for that early. Webflow retired its User Accounts feature in January 2026, so this needs a third party tool, or a good reason to stay on Drupal.

URLs, redirects and launch

Drupal can answer on an alias, a /node path and sometimes more. We crawl and read Search Console to see which ones get real visits. Then we combine that with your Redirect module rules, and make a 301 for each changed path. Webflow runs rules in the order they were made, so specific rules go in first.

  1. We lower the TTL ahead of time.
  2. We point the domain on a call with you.
  3. We test the redirects, forms and tags.
  4. We send the sitemap and check Search Console daily for two weeks.

Every old URL is mapped to protect your rankings. Some movement is normal after launch, and we cannot promise there will be none.

FAQs

Drupal to Webflow
questions.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

If you use its permissions, integrations or logged-in features, upgrade. If it is mostly pages and news, and upgrades feel like a heavy cost, moving is worth a look. We give an honest view for free.

Any version, including Drupal 7. The method changes: newer versions have JSON:API in core, and older ones may need a Views export or database read.

Each one that gets traffic or links gets a 301 to the new page, along with the alias. We check both, because Drupal can answer on either.

Not closely. Webflow has site and workspace roles for your team, not Drupal's fine control. If approval steps and per-section access matter a lot to you, stay on Drupal.

We map every old URL, carry over Metatag values and test on staging, then check Search Console daily for two weeks. Rankings may still shift a little, which is normal, and no one can guarantee them.

You get a fixed quote after a 20 minute call. It depends on content types, forms, languages and pages. First-time clients get $500 off projects of $2,000 or more.

Webflow Localization can handle many sites, depending on your plan, so check current pricing. We map each translation to its locale and keep hreflang correct. Very complex translation workflows may suit Drupal better.

For 30 days after launch we make safe changes for free: copy edits, image swaps, colour tweaks and link updates, and we fix anything we built that does not work. New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.

Wall of love

Don't take
our word for it.

Hear it from the founders and teams we have built for.

Bailey McElligott, Design Director
Bailey on working with Kookies.
Bailey McElligott · Design Director0:17
Verified review
5.0
★★★★★
"They are very professional and the best at what they do."

Juned Khatri, Chief, BubbleWrap
Web development · Dec 2022 to Jan 2023 · Quality, schedule, cost and willing to refer: 5.0

Read it on Clutch
"Fast, efficient and beautifully designed! Kookies nailed our website with pixel-perfect execution and smooth interactions."
Juned KhatriFounder, ClanX
"They are very professional and the best at what they do. Kookies surpassed expectations with Webflow. Thrilled with the results!"
Juned KhatriChief, BubbleWrap
"Kookies' professionalism, dedication and exceptional design skills exceeded our expectations. Highly recommended for high-quality work and timely delivery."
AA
Ali Al MuttawaCo-founder, Artal Invest
"A thorough job, with high-quality work in a short timeframe. Abdul and his team were prompt, professional and patient with all our inputs. Happy to recommend them."
Sejal SinghiManaging Consultant, Baraka Impact Finance

Ready when you are

Let's retire
the upgrade plan.

Send the form and get a price and timeline within one working day. Or book a quick call with our team.

WebflowPremium PartnerProud to build the Webflow way★★★★★5.0 on Clutch
Abdul Quadir
Talk to our teamA senior lead runs your call. Abdul, our founder, often joins.

Book a free 20 minute call

Pick a day that works for you.

See open timesOpen calendaror email hello@kookies.io
Book a callGet a quote