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 Webflow
Records go into the site's own collections, matched by name, or into the collections of Webflow's blog template, which Reloque adds when the site has none: Blog Posts, Pages, Categories, Tags and Authors. Bodies stay rich text, with images uploaded as assets and links between records pointing at the new items. Categories, tags and authors become items of their collections, and SEO data goes into the collection's SEO fields. Published records are published, and drafts stay drafts.
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.
- Webflow: Webflow's API cannot create static pages, menus or redirects, so pages moving in become items of a Pages collection, and menus and redirects are left out. Add 301 redirects in the site's settings.
- Webflow: A static page moving out takes its text and images; its layout, styles, interactions and forms stay in Webflow.
- Webflow: Only the site's primary language is written into Webflow for now.
- Webflow: Webflow's CMS has no members or comments, so neither moves into or out of it.
- Webflow: A site on the free Starter plan holds about 50 CMS items, and Webflow allows 60 API requests a minute on Starter and Basic plans, so larger moves need a paid site plan and take longer.
- Webflow: Collections and fields Reloque adds to a site stay after an undo, as other CMSs keep types it adds.
Versions checked
Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.
Webflow: One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).
Questions
Can Reloque migrate Storyblok to Webflow?
Yes. Reloque moves content from Storyblok to Webflow, 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. One hosted service, so there are no versions to choose. Reloque uses Webflow's Data API (v2).
What does a migration from Storyblok to Webflow 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 Webflow where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Webflow has a place for them.
Is anything written to Webflow before I approve it?
No. You see every record in the Preview first, then a small sample is written to Webflow so you can check it on the real site, and undo it. Storyblok is only ever read.