Migration routeIn early access

Migrate from Drupal to Storyblok

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

Records go into the space's own content types, matched by name, or into Article and Page types Reloque adds, with categories and authors, when the space has none and your role allows it. Posts go into the folder their type's stories are in, or a Blog folder, and pages to the root. Bodies become rich text, with images uploaded as assets and links between records as links between stories. Categories and authors become stories in folders of their own, and tags Storyblok's own tags. Each language goes into the space's language of the same code, in the fields that are translatable. SEO data goes into the type's SEO fields, menus into a config story's navigation and redirects into redirect stories. Drafts stay drafts, and published records are published.

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.
  • Storyblok: Storyblok has no members or comments, so neither moves into or out of it.
  • Storyblok: Components placed inside rich text are left out; components in block fields move as blocks.
  • Storyblok: Reloque does not add languages: add each under Settings › Internationalization first, or it is left out with a note.
  • Storyblok: Content types Reloque adds to a space stay after an undo, as other CMSs keep types it adds.
  • Storyblok: Site settings and dictionary items have no place in Storyblok, so they are left out.

Versions checked

  • Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
  • Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.

Questions

Can Reloque migrate Drupal to Storyblok?

Yes. Reloque moves content from Drupal to Storyblok, 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. Spaces in every region work, and Reloque finds the region itself.

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

Is anything written to Storyblok before I approve it?

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

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