Case Study 

# How QED42 moved its website onto a Drupal platform it fully owns and controls

 

 

 



 ![Lines of code on a dark screen, layered over a building and blurred streaks of orange and white light.](/sites/default/files/2026-11/qed42-website-drupal-platform-cover.png)

Industry

Digital experience services

 

Location

Pune, India

 

Engagement

3 weeks

 

 

 

 

 



 ![QED42 Logo ](/sites/default/files/2026-11/logo-01.png) 

Focus

Open-source software like Drupal costs less to own and frees companies from vendor lock-in. X to Drupal moves websites from a closed builder like Webflow to Drupal, so you own your content and your platform. That’s what we did for our own website, qed42.com.&amp;nbsp;

 

Services

AI-assisted migration

Drupal engineering

Content architecture

AI integration

 

 

 

QED42 is a digital experience company. It has designed and engineered digital experiences for enterprises and global organizations for 17+ years.

Its website, qed42.com, is where the company publishes its thinking, shows its work and markets its services, across 646 public pages of articles, case studies, service pages and campaign landing pages. The marketing team runs the site day to day. The engineers and designers who did the work write many of its 569 articles.

The site ran on Webflow, which kept the design tight and let a small team ship quickly. As it grew, the people publishing into it needed more control over how its content was organized. QED42 also wanted to own the platform itself: who can publish what, which AI services touch its content, and where its data lives. Using X to Drupal, its own [AI-assisted replatforming harness](https://x-to-drupal.qed42.com/blogs/fourteen-generations-of-a-website-to-drupal-system), QED42 rebuilt the whole site on Drupal 11 in about four days, and qed42.com became the first production site the harness moved.

Visit the live site at [qed42.com](https://www.qed42.com/), or see the Webflow and Drupal versions side by side at [x-to-drupal.qed42.com](https://x-to-drupal.qed42.com/#proof).



 [Visit QED42](https://www.qed42.com) 

 

 

 



## Challenges

Editors wanted listings that update themselves, campaign pages built from shared components and an insights library they could filter, and all three ran up against how the site was built. Its structure lived inside the page builder, so changing how content was organized meant changing pages.

A replatform usually arrives as two projects at once: rebuild the technology and redesign the experience, recreating the design and the content model by hand, page by page and field by field. The design was already doing its job for visitors, so QED42 kept it and put the work into the system behind it. That meant a content model editors could work in, on a platform QED42 controls. Open-source software like [Drupal](https://www.qed42.com/services/drupal) costs less to own and frees companies from vendor lock-in.

The early harness runs showed why that system needed the work. Content exported from Webflow carried builder-specific markup that had to become clean Drupal content. The category buttons above the homepage’s article list looked like editorial copy and were in fact part of a filtering mechanism. Copied across as text, they would have left editors with labels they could never change.

## Solution

### Rebuilding the website from what already existed

A replatform usually starts by recreating every page by hand. X to Drupal, built over 14 generations between 11 May and 24 July 2026 and stress-tested on 25 to 30 sites, took on that work by reading the live website as a system: its reusable components, page layouts, design patterns and the relationships between content across all 646 public pages. The 17 page templates it found became the basis of the Drupal theme and content model. The run took about four days, and the team then compared the rendered Drupal pages against the Webflow originals at 1440, 768 and 375 pixels.

### Designing for the people who manage the site

Moving the structure out of the page builder helps only if editors can work in what replaces it. An early generation produced pages that matched the design exactly and passed every visual check, while each component stored its content as a single JSON payload.

In generation 6, the team rebuilt the content model around Drupal Paragraphs, giving every component its own fields for text, images, links and repeatable content. Editors now build campaign pages from the same shared components the rest of the site uses, and change any part of a page through standard field widgets. A dedicated pass turned Webflow’s builder markup into clean Drupal content, so article bodies, bylines, captions and media arrived as structured content editors can edit.

### Content governance built into the architecture

Listings that update themselves need content that knows what it is. Article categories, filtered listings and related-content sections now run on two Drupal taxonomies and 29 Views, so an editor tags an insight once and every listing that should show it does. The homepage category buttons became a taxonomy filter, so readers can filter the insights library and editors manage categories in one place. A content editor role, revisions on every content type and a draft-and-publish workflow on landing pages and products keep publishing controlled, and QED42 can extend that workflow through configuration alone.

### An open platform for AI

QED42 wanted the AI connected to its site to be its own choice. It connected Anthropic and OpenAI through Drupal’s provider-based AI integrations, on its own credentials. On qed42.com, AI writes missing image alt text when an editor asks for it, an AI SEO analysis reviews the AI solution pages, and the site logs each AI call by model, task and time, without recording prompt content.

Because the providers sit behind Drupal’s own integration layer, QED42 can change models, providers or hosting as its data-handling requirements change, independent of any CMS vendor’s roadmap.

### Making content available beyond the website

Search engines and AI assistants read a website differently from people. qed42.com now gives them versions of its content made for machines: structured details about each page that search engines read, a guide to the site written for AI assistants, and a plain-text copy of every content page. Each one draws on the same content editors already manage, so every edit reaches them automatically. QED42 also sets rules for each of 22 named AI and search crawlers, and can change them whenever it wants.

Under the hood, these are JSON-LD structured data, an [llms.txt](https://www.qed42.com/llms.txt) file, Markdown page versions and a read-only [JSON:API](https://www.qed42.com/jsonapi).

## Outcome

The people who publish on qed42.com now work in a system built around their content. A marketer putting together a campaign page assembles it from the same components the rest of the site uses. An engineer publishing an insight tags it once, and it shows up in the right listings, related-content blocks and category filter on its own. The 569 articles and 2,007 images that moved across arrived as content editors can work in, field by field.

The structure that once lived inside the page builder now belongs to QED42. X to Drupal delivered the site as a Drupal Recipe with zero custom modules, so any Drupal team can run it. QED42 sets its own publishing workflow, chooses the AI providers connected to the site and decides how crawlers read it. It has since added two small modules of its own, for analytics and MCP sign-in.

Keeping the design kept the move to a single project. Visitors still see the site they knew, and a redesign can now happen on structured content, as its own piece of work, whenever QED42 chooses to start one.

The next shift is already wired in. Through an MCP connection, which links AI assistants to the site, the marketing team can describe a change in plain language and receive it in Drupal as a draft for an editor to review.

Two limits stay visible. Animation-heavy sections come across closest to their resting state, and plain-English help text for every field is still being written.

qed42.com is now the first production reference for X to Drupal, and the site any prospect can open to see what the move looks like.

## Living with a website on a platform you have outgrown?

Share your site with us. We’ll read it the way the harness does and show you what a move to Drupal involves, page by page.

[Start the conversation](https://x-to-drupal.qed42.com/#contact) · [Visit qed42.com](https://www.qed42.com/) · [See X to Drupal](https://x-to-drupal.qed42.com/)