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.
- We lower the TTL ahead of time.
- We point the domain on a call with you.
- We test the redirects, forms and tags.
- 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.







