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 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.
- 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.
- 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
Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
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 Strapi to Storyblok?
Yes. Reloque moves content from Strapi to Storyblok, for early-access members now. Checked on Strapi 5.58 and 4.26, and 3.6 as a source. 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 Strapi 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. Strapi is only ever read.