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 WordPress
Posts follow the site's permalink setting, and with the Redirection plugin installed each old address redirects to its new one, along with the old site's own redirects. Media lands in the Media Library with its alt text, featured images, categories and tags are linked, with categories under their parents, and authors are matched to existing users. Every category and tag comes over, including those no post uses, and so does every term of your own taxonomies. Members can move too, as subscribers, without their passwords. The site's title, tagline, logo and timezone are set where the new site has none yet. Menus arrive as WordPress menus, at the theme location they had, with each link pointed at the moved page. Comments arrive with their replies, under each commenter's own name and email, at their own dates, approved or waiting for a moderator as they were. SEO data goes to Yoast SEO or Rank Math, whichever the new site runs, its social images copied to the Media Library.
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.
- WordPress: Rank Math's REST API does not show its SEO data, so connect a Rank Math site with its export file or the bridge file to move it. Yoast's REST API takes SEO data on posts only, and of it only the SEO title, description and focus keyword (older Yoast, such as 19.6, takes none); what a WordPress destination with Yoast cannot take is named in the run report.
- WordPress: Page-builder layouts move as the HTML they render, not as builder settings.
Versions checked
Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
WordPress: Checked on WordPress 7.1 and 6.0, and 5.5 as a source.
Questions
Can Reloque migrate Strapi to WordPress?
Yes. Reloque moves content from Strapi to WordPress, for early-access members now. Checked on Strapi 5.58 and 4.26, and 3.6 as a source. Checked on WordPress 7.1 and 6.0, and 5.5 as a source.
What does a migration from Strapi to WordPress 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 WordPress where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where WordPress has a place for them.
Is anything written to WordPress before I approve it?
No. You see every record in the Preview first, then a small sample is written to WordPress so you can check it on the real site, and undo it. Strapi is only ever read.