Migration routeIn early access

Migrate from Payload to Sanity

Reloque moves your Payload content into Sanity: posts, pages, media, SEO data and redirects. It maps every field, previews every record and tests a sample on Sanity 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 Sanity

Records go into the dataset's own document types, matched by name, writing the fields their documents have. A dataset with no posts or pages gets documents shaped as Sanity's blog starter (post, page, category, tag and author), which the Studio shows once its schema has those types. Bodies become Portable Text, with images uploaded as assets and links between records as references. Categories, tags and authors become documents of the types the dataset refers to. Each language becomes a document of its own, tied to the others as document internationalisation does. SEO data goes into an SEO object, menus into navigation documents and redirects into redirect documents. Drafts stay drafts, and published records are published.

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.
  • Sanity: Sanity has no members or comments, so neither moves into or out of it.
  • Sanity: A block of your own in Portable Text, such as a call to action, keeps only a link to what it points at.
  • Sanity: Translations kept field by field inside one document (internationalised arrays) are not read yet; translations as documents of their own are.
  • Sanity: Documents Reloque writes into types your Studio has no schema for are stored, but the Studio shows them only once its schema has those types.
  • Sanity: Site settings and dictionary items have no place in Sanity, so they are left out.

Versions checked

  • Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
  • Sanity: One hosted service, so there are no versions to choose. Any Studio version works, as Reloque talks to the project's API.

Questions

Can Reloque migrate Payload to Sanity?

Yes. Reloque moves content from Payload to Sanity, for early-access members now. Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB). One hosted service, so there are no versions to choose. Any Studio version works, as Reloque talks to the project's API.

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

Is anything written to Sanity before I approve it?

No. You see every record in the Preview first, then a small sample is written to Sanity 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 Sanity. 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 Sanity?

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