What Reloque reads from Ghost
Reloque reads posts, pages, tags, authors, images and each one's SEO and sharing fields through the Admin API, from Ghost 3 to 6, or from an export file. The navigation and secondary navigation come too, from Ghost 5 and later or an export file, with their links pointed at the moved pages, and so do comments, with their replies, from Ghost 5 and later. Connected with a staff access token, the site's redirects come too.
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.
- Ghost: Members move with their labels and newsletter choices, but paid subscriptions stay in Stripe, so paying members arrive free.
- Ghost: Ghost has no custom fields, so fields without a place stay in the content export.
- Ghost: Ghost lets only its staff change its settings and navigation, so the site's title, logo and menus are set in its admin after a move. The handover package lists every menu link at its new address.
- Ghost: Writing needs Ghost 5 or later; Ghost 3 and 4 are sources.
- Ghost: Ghost has comments on posts only, so comments on pages are listed in the handover package, as are comments by people with no email.
- Ghost: Ghost has no noindex, nofollow or focus keyword for a post, so those are named in the run report; the SEO title, description, canonical address and sharing fields arrive, with sharing images copied.
- 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
Ghost: Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources.
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 Ghost to Umbraco?
Yes. Reloque moves content from Ghost to Umbraco, for early-access members now. Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources. 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 Ghost 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. Ghost is only ever read.