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 Umbraco
Each post and page becomes a document, under a document type Reloque creates with the shared fields when yours does not exist. Umbraco sets its own publish date, so the original goes into a Publish date field. A site in several languages moves in every language, and a language the new site lacks is added. Dictionary items, the labels your templates show, move in every language too, and each document keeps its domains and hostnames. SEO data from another CMS fills the document type's SEO properties, such as seoTitle, metaDescription, noIndex and ogImage, with sharing images copied, and what the type has no property for is named in the run report.
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.
- Umbraco: Members move between every CMS here, and never with their passwords.
- Umbraco: Umbraco's navigation is its page tree, so menus from another CMS are listed in the handover package to set up by hand.
- Umbraco: Umbraco has no comments of its own, so comments from another CMS are listed in the handover package.
- Umbraco: SEO properties are known by their names, such as seoTitle, metaDescription and noIndex; one named otherwise is matched on the Map step as a field of its own.
- Umbraco: Umbraco 7 to 14 are sources; writing needs Umbraco 15 or later.
Versions checked
Storyblok: One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself.
Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
Questions
Can Reloque migrate Storyblok to Umbraco?
Yes. Reloque moves content from Storyblok to Umbraco, 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 Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
What does a migration from Storyblok to Umbraco 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 Umbraco where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Umbraco has a place for them.
Is anything written to Umbraco before I approve it?
No. You see every record in the Preview first, then a small sample is written to Umbraco so you can check it on the real site, and undo it. Storyblok is only ever read.