What Reloque reads from Strapi
Reloque reads your content types, media and relations with an API token, or as a Users & Permissions user on Strapi 3. Rich text in blocks or Markdown is read as formatting, not as raw text. A translated type is read in every locale, each published or a draft as it is. Single types, such as the site's settings, go to the new site's single types or globals of the same name, and their lists of links become menus on WordPress. Redirects come too, from a Redirect type of your own or strapi-plugin-redirects on Strapi 4.
How it lands in Ghost
Bodies are sent as HTML, which Ghost turns into its own editor format. Categories become tags, posts keep their slugs at /<slug>/, and the redirects are added to Ghost's own when you connect with a staff access token (Ghost 5 and later); otherwise the handover package includes a redirects.yaml ready to upload. Comments arrive on their posts at their own dates, each by the member with the commenter's email: you choose on the Map step whether to add a free member for each commenter who is not one, signed up to no newsletter and sent no email.
What to plan for
Better to know now than after the switch. The free scan names anything on your site that cannot move.
- 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.
- 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.
Versions checked
Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
Ghost: Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources.
Questions
Can Reloque migrate Strapi to Ghost?
Yes. Reloque moves content from Strapi to Ghost, for early-access members now. Checked on Strapi 5.58 and 4.26, and 3.6 as a source. Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources.
What does a migration from Strapi to Ghost 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 Ghost where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Ghost has a place for them.
Is anything written to Ghost before I approve it?
No. You see every record in the Preview first, then a small sample is written to Ghost so you can check it on the real site, and undo it. Strapi is only ever read.