What Reloque reads from Storyblok
Reloque reads the space's content types from its components, and every story with its content, drafts and every language included. Posts, pages, your own content types, authors and categories are told apart by name and fields, and Storyblok's own tags come too. Components inside stories move as blocks, assets come as media, and rich text keeps its headings, lists, links, formatting and images, with links between stories pointing at the moved records. SEO fields reach the other CMS's SEO fields, a config story's navigation comes as menus, and redirect stories as redirects.
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.
- 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.
- 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
Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.
Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
Questions
Can Reloque migrate Storyblok to Drupal?
Yes. Reloque moves content from Storyblok to Drupal, for early-access members now. One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself. Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
What does a migration from Storyblok 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. Storyblok is only ever read.