Migration routeIn early access

Migrate from Payload to Strapi

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

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

What Reloque reads from Payload

Reloque reads your collections, uploads and relationships with a user's API key, from Payload 1, 2 or 3, with blocks, arrays and groups read as structured content, not flattened. A localized site is read in every locale, and its globals (site settings, header, footer) go to the new site's globals or single types of the same name. A header's or footer's links become menus on WordPress, and the redirects plugin's redirects move too, each to its page's new address. Payload has no front end, so you can give the public site's address when connecting, and links to it in the content are pointed at the migrated records.

How it lands in Strapi

Bodies are written as Strapi blocks or Markdown, whichever each field is, images go to the Media Library, and cover images, categories, tags and authors are linked, categories under their parents where they have a parent relation. Strapi 5 sets its own publish date, so the original goes into a date field of your own. A site in several languages moves into each locale of a translated type. Members can move too, as Users & Permissions users in the role of their group, without their passwords. With a Redirect type of your own (from and to fields), each old address redirects to its new one; with strapi-plugin-redirects, the handover package has a file to import in its admin page. Menus from another CMS fill a single type's list of links, a main menu the header's and a footer the footer's.

What to plan for

Better to know now than after the switch. The free scan names anything on your site that cannot move.

  • 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.
  • 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.

Versions checked

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

Questions

Can Reloque migrate Payload to Strapi?

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

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

Is anything written to Strapi before I approve it?

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

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Payload to Strapi. 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 Payload to Strapi?

Reserve a free assessment and we look at your Payload site with you: what moves to Strapi, 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.