What Reloque reads from Umbraco
Reloque reads documents, media and each editor's values through the Management API (15 and later), the Delivery API (12 to 14) or the bridge template (7 to 13). SEO properties, such as seoTitle, metaDescription and noIndex, are read as the page's SEO data too, so they reach the other CMS's SEO fields, and Umbraco's own redirects from renamed and moved pages come with them (15 and later, or the bridge).
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.
- 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.
- 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
Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
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 Umbraco to Storyblok?
Yes. Reloque moves content from Umbraco to Storyblok, for early-access members now. Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against). 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 Umbraco 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. Umbraco is only ever read.