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 Sanity
Records go into the dataset's own document types, matched by name, writing the fields their documents have. A dataset with no posts or pages gets documents shaped as Sanity's blog starter (post, page, category, tag and author), which the Studio shows once its schema has those types. Bodies become Portable Text, with images uploaded as assets and links between records as references. Categories, tags and authors become documents of the types the dataset refers to. Each language becomes a document of its own, tied to the others as document internationalisation does. SEO data goes into an SEO object, menus into navigation documents and redirects into redirect documents. 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.
- 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.
- Sanity: Sanity has no members or comments, so neither moves into or out of it.
- Sanity: A block of your own in Portable Text, such as a call to action, keeps only a link to what it points at.
- Sanity: Translations kept field by field inside one document (internationalised arrays) are not read yet; translations as documents of their own are.
- Sanity: Documents Reloque writes into types your Studio has no schema for are stored, but the Studio shows them only once its schema has those types.
- Sanity: Site settings and dictionary items have no place in Sanity, so they are left out.
Versions checked
Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.
Sanity: One hosted service, so there are no versions to choose. Any Studio version works, as Reloque talks to the project's API.
Questions
Can Reloque migrate Storyblok to Sanity?
Yes. Reloque moves content from Storyblok to Sanity, 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. Any Studio version works, as Reloque talks to the project's API.
What does a migration from Storyblok to Sanity 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 Sanity where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Sanity has a place for them.
Is anything written to Sanity before I approve it?
No. You see every record in the Preview first, then a small sample is written to Sanity so you can check it on the real site, and undo it. Storyblok is only ever read.