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 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.
- 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.
- 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
Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.
Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
Questions
Can Reloque migrate Storyblok to Strapi?
Yes. Reloque moves content from Storyblok to Strapi, 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 Strapi 5.58 and 4.26, and 3.6 as a source.
What does a migration from Storyblok 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. Storyblok is only ever read.