Gemin
Start a project

Drupal to Webflow

Migrate from Drupal to Webflow

Drupal is powerful, but many marketing sites no longer need that much machinery. I preserve the useful structure and retire the parts that make every change expensive.

Start a project

A migration like this usually takes 4–5 weeks

Why people move

What changes when you move from Drupal to Webflow.

What is being compared Drupal Webflow
Content modeling Drupal As deep as you like, and often deeper than needed Webflow Collections and references, with real limits Drupal wins this outright. If your model genuinely needs it, that is a reason to stay.
Permissions and workflow Drupal Granular roles, editorial workflow, moderation states Webflow Editor access, scoped per collection Also Drupal's. A site with a five-stage approval chain is not a Webflow site.
Who maintains it Drupal You: core, modules, PHP, security advisories Webflow Webflow
Design changes Drupal A developer and a theme layer Webflow Anyone on the marketing team
Publishing a landing page Drupal A ticket Webflow An afternoon

Once you have decided

What actually migrates.

What you have What happens Why
Pages Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Twig templates and the theme layer do not transfer.
Content types and nodes Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Exportable with effort, usually through Views or a migration module, and they move after the Webflow model they are moving into has been decided.
Taxonomy Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. A simple vocabulary becomes a field or a collection. A deep or heavily reused one gets remodeled around the relationships the new templates actually render, which is a deliberate simplification rather than a flattening.
Media Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Files are rehosted and the references inside body fields rewritten to match.
Users, workflow and permissions Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. These do not become ordinary Webflow CMS features. Anything load-bearing is scoped as its own piece of work, or it is the reason to stay.
Modules and custom behavior Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. Each one becomes an integration, an external service, a custom implementation or a deliberate removal. That review is its own line in the quote.

Before you budget it

Where this migration gets complicated.

  1. 01

    Drupal models relationships more deeply than a marketing site renders

    Drupal can model deeply connected entities that do not map cleanly into a simpler marketing CMS. Some relationships become references, others get flattened or intentionally duplicated around what the Webflow templates actually need to render.

  2. 02

    Taxonomy terms are usually doing more than tagging

    On a mature Drupal site terms drive menus, access and generated pages as well as categorisation. Mapping them to a Webflow reference field carries the label and drops every behavior attached to it.

How it runs

How the migration works.

  1. 01

    Plan

    What Drupal will actually hand over, what has to be rebuilt, and what each thing becomes: a page, a collection, a field, or nothing.

  2. 02

    Build

    Templates built in the Designer, against the model rather than against the old pages.

  3. 03

    Migrate

    Content in, assets rehosted and checked against the source, and every address that changes given a rule pointing straight at its replacement.

  4. 04

    Launch

    Forms at the record, every template at three widths and every old address requested, all before anything is switched. Then typically 4–5 weeks from start to live, and a week of watching what the old addresses return.

What you are buying

What is included.

  • Design rebuild

    Rebuilt directly against the existing site.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • Redirects

    Changed URLs mapped directly to replacements.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.