Migration routeIn early access

Migrate from Drupal to Webflow

Reloque moves your Drupal content into Webflow: posts, pages, media, SEO data and redirects. It maps every field, previews every record and tests a sample on Webflow before the real move.

Join early access Free for early-access members: we look at your Drupal site with you before anything moves.

What Reloque reads from Drupal

Reloque reads every content type's nodes through JSON:API, or the bridge file on Drupal 6 to 8.6: articles as posts, basic pages as pages, your own types as types of their own, with their fields, Paragraphs as blocks, Media and files, every vocabulary's terms and each node's author. SEO data comes from Metatag: the tags an editor set for a node, not Metatag's defaults, so it reaches the other CMS's SEO fields. Members come too when you choose them: users who only visit the site, never your editors, with their roles and fields but never their passwords. Menus come too, with each link pointed at the moved page, and comments with their replies, visitors' names and emails, and whether each was approved. Every language comes too: each node with its translations, in their own titles, aliases and fields. So do the Redirect module's redirects, each pointed at its page's new address, and the site's name, slogan, language, logo and icon. Links between nodes point at their aliases.

How it lands in Webflow

Records go into the site's own collections, matched by name, or into the collections of Webflow's blog template, which Reloque adds when the site has none: Blog Posts, Pages, Categories, Tags and Authors. Bodies stay rich text, with images uploaded as assets and links between records pointing at the new items. Categories, tags and authors become items of their collections, and SEO data goes into the collection's SEO fields. Published records are published, and drafts stay drafts.

What to plan for

Better to know now than after the switch. The free scan names anything on your site that cannot move.

  • Drupal: Drupal's JSON:API cannot add a translation to a node, so each language goes into Drupal as a node of its own, not linked to the others.
  • Drupal: Drupal's JSON:API cannot read or change site settings, so on Drupal 8.7 and later they are read from the public site (not the time zone), and into Drupal they are set by hand from the run report.
  • Drupal: Drupal's JSON:API can only block a user it removes, so a sample test adds no members, and undoing a migration blocks the members it added rather than deleting them.
  • Drupal: Drupal's JSON:API cannot create a menu, so a menu goes into one the site has; add a missing one under Structure › Menus.
  • Drupal: Drupal's JSON:API cannot create Paragraphs, so blocks written into Drupal are added to the body.
  • Drupal: Drupal 6, 7 and 8.0 to 8.6 are sources, through the bridge file, as they have no JSON:API in core.
  • Drupal: SEO data is written into Metatag 2; Metatag 1, which JSON:API cannot write, leaves it out with a note. Drupal 6's Nodewords is not read.
  • Webflow: Webflow's API cannot create static pages, menus or redirects, so pages moving in become items of a Pages collection, and menus and redirects are left out. Add 301 redirects in the site's settings.
  • Webflow: A static page moving out takes its text and images; its layout, styles, interactions and forms stay in Webflow.
  • Webflow: Only the site's primary language is written into Webflow for now.
  • Webflow: Webflow's CMS has no members or comments, so neither moves into or out of it.
  • Webflow: A site on the free Starter plan holds about 50 CMS items, and Webflow allows 60 API requests a minute on Starter and Basic plans, so larger moves need a paid site plan and take longer.
  • Webflow: Collections and fields Reloque adds to a site stay after an undo, as other CMSs keep types it adds.

Versions checked

  • Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
  • Webflow: One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).

Questions

Can Reloque migrate Drupal to Webflow?

Yes. Reloque moves content from Drupal to Webflow, for early-access members now. Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file). One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).

What does a migration from Drupal to Webflow cost?

The assessment is free and gives your exact price: you pay for the records a migration writes, and media files do not count. Packages start at £99, and records are shared across any number of migrations for 12 months.

Will my addresses and SEO survive the move?

Every address that changes gets a redirect, written to Webflow where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Webflow has a place for them.

Is anything written to Webflow before I approve it?

No. You see every record in the Preview first, then a small sample is written to Webflow so you can check it on the real site, and undo it. Drupal is only ever read.

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Drupal to Webflow. We will look at your site with you before anything moves.

Plan this move with us

Early access is free. Tell us both systems when you reserve.

Free assessment

Moving Drupal to Webflow?

Reserve a free assessment and we look at your Drupal site with you: what moves to Webflow, what stays, and the price. Nothing is written until you approve it.

Get your free assessment
Early-access members get a free migration assessment.
  1. Connect both sitesReloque reads the source and checks it may write to the destination.
  2. Check the mappingEvery field is matched, and the uncertain ones are yours to decide.
  3. Test a sampleA few records are written to the destination, read back and removed.
  4. Move the restEvery record is written and checked, with redirects for old addresses.