Migration routeIn early access

Migrate from Strapi to Payload

Reloque moves your Strapi content into Payload: posts, pages, media, SEO data and redirects. It maps every field, previews every record and tests a sample on Payload before the real move.

Join early access Free for early-access members: we look at your Strapi site with you before anything moves.

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 Payload

Bodies become Payload rich text, images are uploaded to your upload collection, and categories, tags and authors are created where missing and linked, categories under their parents where your categories have a parent field. Blocks, arrays and groups are filled field by field, and relationships point at the migrated records. Each record keeps its old address in sourceUrl, for redirects, and with the redirects plugin installed each old address redirects to its new one, along with the old site's own redirects. A site in several languages moves into each locale of your localized fields. Members can move too, into a collection with sign-in other than your admins', without their passwords. Menus from another CMS fill a global's list of links, a main menu the header's and a footer the footer's.

A Strapi article, written into Payload

A Strapi article, written into Payload
StrapibecomesPayload
titletitle
content (blocks or Markdown)content, as Lexical rich text
coverfeaturedImage, uploaded
category and tagscategories and tags, linked
authorauthor, linked
publishedAtpublishedAt
slugslug, and a row in redirects.csv
Components and dynamic zonesgroups, arrays and blocks of the same name, with their uploads
Relationsrelationships to the same records, once they are written
Where each part of a Strapi article goes in a typical Payload posts collection. The Map step shows the real fields of both projects, and you confirm each one.

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.
  • Payload: Payload has no front end, so redirects assume pages at /<slug> and posts at /blog/<slug> until you change them to your routes.
  • Payload: Original publish dates are kept when the collection has a publishedAt field.
  • Payload: With GraphQL turned off, fields are learned from your existing documents, so a collection with none yet takes plain values and leaves out what Payload refuses.
  • Payload: Payload's locales are set in its config only, so add each language the old site has to localization, and mark the fields to translate localized, before you migrate.
  • Payload: Payload has no comments of its own, so comments from another CMS are listed in the handover package.
  • Payload: SEO data goes into an SEO group, your own or the SEO plugin's meta group, field by field; what the group has no field for is named in the run report.

Versions checked

  • Strapi: Checked on Strapi 5.58 and 4.26, and 3.6 as a source.
  • Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).

Questions

Can Reloque migrate Strapi to Payload?

Yes. Reloque moves content from Strapi to Payload, for early-access members now. Checked on Strapi 5.58 and 4.26, and 3.6 as a source. Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).

What does a migration from Strapi to Payload 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 Payload where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Payload has a place for them.

Is anything written to Payload before I approve it?

No. You see every record in the Preview first, then a small sample is written to Payload so you can check it on the real site, and undo it. Strapi is only ever read.

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Strapi to Payload. We will look at your site with you before anything moves.

Plan this move with us

Early access is free. Tell us both systems when you reserve.

Free assessment

Moving Strapi to Payload?

Reserve a free assessment and we look at your Strapi site with you: what moves to Payload, what stays, and the price. Nothing is written until you approve it.

Get your free assessment
Early-access members get a free migration assessment.
  1. Connect both sitesReloque reads the source and checks it may write to the destination.
  2. Check the mappingEvery field is matched, and the uncertain ones are yours to decide.
  3. Test a sampleA few records are written to the destination, read back and removed.
  4. Move the restEvery record is written and checked, with redirects for old addresses.