Coming soon

A studio is on its way.

I am growing my Webflow practice into QDS, a design and development studio. The new site launches soon. Until then, write to me.

[email protected]

Trusted by

Use cases

When this fits

Every update needs a developer.

Core and module updates take time and budget every year.

In Webflow

Hosting, security and updates are handled by Webflow.

Editors find the admin hard to use.

Publishing a page takes training, and mistakes break layouts.

In Webflow

Editors change content on the page, inside components that keep the layout intact.

A major version upgrade is coming.

An upgrade can cost as much as a new site.

In Webflow

Move once, to a platform without version upgrades.

What moves, what changes

Each part of your Drupal site has a place in Webflow. We map them before the build, so nothing is left behind.

In Drupal

In Webflow

Pages

Pages built from a component library

Articles

A CMS collection your team edits

Content types

CMS collections, one per type

Taxonomy terms

Reference fields, for filters and lists

Theme

A design system, set once for every page

Modules

Native Webflow features, or an integration where needed

URLs

Kept where possible, redirected where not

SEO titles and descriptions

Page settings and CMS fields, carried over or corrected

Media library

Webflow assets, resized and compressed

Forms

Webflow forms, connected to your tools

What you get

An inventory of pages, content, modules and forms, with what moves and what is retired.

The site rebuilt in Webflow, with the current design or a new one.

Nodes and taxonomy terms imported into CMS collections.

Redirects for every old address that changes.

Titles, descriptions and schema carried over or corrected.

A check in Google Search Console after launch.

Included in every project

A design system.

Colors, type and spacing are set once.

A component library.

New pages from sections that already exist.

Structure for search and AI.

Headings, titles and schema at launch.

A handover.

A walkthrough and a guide to editing.

How it works

Step 01

Call.

We look at your Drupal site together and talk about what you want to change.

Step 02

Inventory and proposal.

We list pages, content, modules and forms, and send the scope and price.

Step 03

Build and import.

We build the site in Webflow and import your content into the CMS.

Step 04

Redirects and testing.

We map every old address and test the site on a staging link.

Step 05

Launch.

We switch the domain and check that old links land on the right page.

Step 06

Check after launch.

We review Google Search Console and fix what it reports.

FAQ

Questions

01
Can you move our content automatically?

Most of it. We export nodes and taxonomy terms, map the fields and import them into the Webflow CMS. Complex field types are checked one by one.

02
What happens to our modules?

We list what each module does. Most become native Webflow features or an integration. Custom logic is moved to a service or retired.

03
Will our URLs change?

We keep addresses where possible. Where they change, we set up redirects so old links keep working.

04
Can we keep our current design?

Yes. We can rebuild the current design in Webflow, or design a new one as part of the move.

05
How does our team edit content after the move?

In Webflow, on the page or in the CMS. You get a walkthrough and a guide at launch.

06
Our site has a lot of content. Is that a problem?

Webflow CMS plans have item limits. We count your content first and tell you which plan fits, or what to archive.

Tell us about your Drupal site.