Migration routeIn early access

Migrate from Drupal to Strapi

Reloque moves your Drupal content into Strapi: posts, pages, media, SEO data and redirects. It maps every field, previews every record and tests a sample on Strapi 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 Strapi

Bodies are written as Strapi blocks or Markdown, whichever each field is, images go to the Media Library, and cover images, categories, tags and authors are linked, categories under their parents where they have a parent relation. Strapi 5 sets its own publish date, so the original goes into a date field of your own. A site in several languages moves into each locale of a translated type. Members can move too, as Users & Permissions users in the role of their group, without their passwords. With a Redirect type of your own (from and to fields), each old address redirects to its new one; with strapi-plugin-redirects, the handover package has a file to import in its admin page. Menus from another CMS fill a single type's list of links, a main menu the header's and a footer the footer's.

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.
  • Strapi: Components and dynamic zones move as blocks between Strapi, Payload and Umbraco; WordPress and Ghost get their content as HTML.
  • Strapi: Writing needs Strapi 4 or later; Strapi 3 is a source.
  • Strapi: Strapi adds locales in its admin only, so add each language the old site has under Settings › Internationalization before you migrate.
  • Strapi: Strapi has no page routes, so check the redirects against your front end.
  • Strapi: Strapi has no comments of its own, so comments from another CMS are listed in the handover package.
  • Strapi: SEO data goes into an SEO component, such as shared.seo, field by field; what the component has no field for is named in the run report.

Versions checked

  • Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
  • Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.

Questions

Can Reloque migrate Drupal to Strapi?

Yes. Reloque moves content from Drupal to Strapi, for early-access members now. Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file). Checked on Strapi 5.58 and 4.26, and 3.6 as a source.

What does a migration from Drupal to Strapi 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 Strapi where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Strapi has a place for them.

Is anything written to Strapi before I approve it?

No. You see every record in the Preview first, then a small sample is written to Strapi 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 Strapi. 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 Strapi?

Reserve a free assessment and we look at your Drupal site with you: what moves to Strapi, 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.