Migration routeIn early access

Migrate from Strapi to Drupal

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

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

What Reloque reads from Strapi

Reloque reads your content types, media and relations with an API token, or as a Users & Permissions user on Strapi 3. Rich text in blocks or Markdown is read as formatting, not as raw text. A translated type is read in every locale, each published or a draft as it is. Single types, such as the site's settings, go to the new site's single types or globals of the same name, and their lists of links become menus on WordPress. Redirects come too, from a Redirect type of your own or strapi-plugin-redirects on Strapi 4.

How it lands in Drupal

Each post and page becomes a node at its old address, as an article, a basic page or the content type you choose, with its fields in each field type's format. Categories and tags go into their vocabularies, nested where they were, images into the Media Library, and authors are matched to the site's users. SEO data from another CMS goes into Metatag's field, with sharing images copied. Menus are added to Main navigation, Footer or a menu of the same name, as JSON:API cannot create menus. Comments arrive with their replies, each by the site's user with the commenter's email or as a visitor. Members become users with no password, who set their own with Drupal's password reset page, and get a role only where it cannot edit the site. JSON:API cannot create Paragraphs, so blocks from another CMS are added to the body. A site in several languages comes in its default language, or each language as a node of its own, as JSON:API cannot add a translation; you choose on the Map step. With the Redirect module installed, each page's old address redirects to its new one, and the old site's own redirects come too. Drupal's JSON:API cannot change site settings, so the run report lists the site name, slogan and time zone to set in Drupal's admin.

What to plan for

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

  • 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.
  • 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.

Versions checked

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

Questions

Can Reloque migrate Strapi to Drupal?

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

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

Is anything written to Drupal before I approve it?

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

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Strapi to Drupal. 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 Strapi to Drupal?

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