On demand
Before you upgrade to Drupal 11, decide if you still need Drupal.
Steve Lavigne, President & CTO of Craft&Crew, and Mike Wiegand, Product Marketing Manager at Webflow, make the business and technical case for moving from Drupal to Webflow Enterprise: what another Drupal cycle really costs, what Webflow Enterprise replaces, and what happens to a mature Drupal architecture when it moves.
Recorded live October 29 2026 · 45 minutes
The conversation
What we covered
Cost
What does another Drupal cycle really cost?
The three-year cost of Drupal 11 against Webflow Enterprise, including upgrades, hosting, development, maintenance, internal resources and platform costs.
Operating model
What could Webflow Enterprise actually replace?
Where Webflow changes the operating model: managed infrastructure, governance, publishing, permissions, optimization, and the role developers play in day-to-day website operations.
Architecture
What happens to a mature Drupal architecture?
Content types. Paragraphs. Taxonomies. Views. Multilingual. Custom modules. Integrations. What maps over, what gets rethought and what can be left behind.
Search equity
Can you migrate without sacrificing search equity?
The controls needed around URL architecture, redirects, metadata, schema and internal links before, during and after cutover.
Fit
Where does Webflow fit, and where doesn’t it?
A realistic look at the enterprise requirements Webflow handles, where integrations or a different architecture are needed, and where Drupal may still make sense.
Business case
How do you build the business case?
How to compare Drupal 11 and Webflow Enterprise across the concerns of marketing, technology, security and finance.
Your Drupal estate
What would each path cost you?
Every Drupal estate is different.
Spend 30 minutes with Craft&Crew and we’ll look at how your site is set up today. Then we’ll put both paths side by side for your own site, the Drupal 11 upgrade and a move to Webflow Enterprise, each costed over three years.