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 Strapi
Bodies are written as Strapi blocks or Markdown, whichever each field is, images go to the Media Library, and cover images, categories, tags and authors are linked, categories under their parents where they have a parent relation. Strapi 5 sets its own publish date, so the original goes into a date field of your own. A site in several languages moves into each locale of a translated type. Members can move too, as Users & Permissions users in the role of their group, without their passwords. With a Redirect type of your own (from and to fields), each old address redirects to its new one; with strapi-plugin-redirects, the handover package has a file to import in its admin page. Menus from another CMS fill a single type's list of links, a main menu the header's and a footer the footer's.
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.
- 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.
Versions checked
Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
Questions
Can Reloque migrate Umbraco to Strapi?
Yes. Reloque moves content from Umbraco to Strapi, 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). Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
What does a migration from Umbraco to Strapi 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 Strapi where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Strapi has a place for them.
Is anything written to Strapi before I approve it?
No. You see every record in the Preview first, then a small sample is written to Strapi so you can check it on the real site, and undo it. Umbraco is only ever read.