What Reloque reads from Contentful
Reloque reads the space through its Content Management API, in every status and every locale. Contentful has no built-in posts or pages, so content types are told apart by name and fields: a type for posts, one for pages, your own types as types of their own, authors, and categories and tags, with Contentful's own tags too. Assets come as media. Rich Text keeps its headings, lists, links, formatting and images, and links between entries point at the moved records. SEO fields, or an SEO entry an entry links to, reach the other CMS's SEO fields, and menu and redirect entries come as menus and 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.
- Contentful: Contentful has no members or comments, so neither moves into or out of it.
- Contentful: An entry embedded in Rich Text, rather than linked, keeps only its title, as a link.
- Contentful: Reloque does not add locales: add each language under Settings › Locales first, or it is left out with a note.
- Contentful: Contentful sets its own publish date, so the original date goes into a date field of the type where it has one.
- Contentful: Site settings and dictionary items have no place in Contentful, 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
Contentful: One hosted service, so there are no versions to choose. Both regions, main and EU, work.
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 Contentful to Umbraco?
Yes. Reloque moves content from Contentful to Umbraco, for early-access members now. One hosted service, so there are no versions to choose. Both regions, main and EU, work. 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 Contentful 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. Contentful is only ever read.