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 Drupal
Each post and page becomes a node at its old address, as an article, a basic page or the content type you choose, with its fields in each field type's format. Categories and tags go into their vocabularies, nested where they were, images into the Media Library, and authors are matched to the site's users. SEO data from another CMS goes into Metatag's field, with sharing images copied. Menus are added to Main navigation, Footer or a menu of the same name, as JSON:API cannot create menus. Comments arrive with their replies, each by the site's user with the commenter's email or as a visitor. Members become users with no password, who set their own with Drupal's password reset page, and get a role only where it cannot edit the site. JSON:API cannot create Paragraphs, so blocks from another CMS are added to the body. A site in several languages comes in its default language, or each language as a node of its own, as JSON:API cannot add a translation; you choose on the Map step. With the Redirect module installed, each page's old address redirects to its new one, and the old site's own redirects come too. Drupal's JSON:API cannot change site settings, so the run report lists the site name, slogan and time zone to set in Drupal's admin.
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.
- Drupal: Drupal's JSON:API cannot add a translation to a node, so each language goes into Drupal as a node of its own, not linked to the others.
- Drupal: Drupal's JSON:API cannot read or change site settings, so on Drupal 8.7 and later they are read from the public site (not the time zone), and into Drupal they are set by hand from the run report.
- Drupal: Drupal's JSON:API can only block a user it removes, so a sample test adds no members, and undoing a migration blocks the members it added rather than deleting them.
- Drupal: Drupal's JSON:API cannot create a menu, so a menu goes into one the site has; add a missing one under Structure › Menus.
- Drupal: Drupal's JSON:API cannot create Paragraphs, so blocks written into Drupal are added to the body.
- Drupal: Drupal 6, 7 and 8.0 to 8.6 are sources, through the bridge file, as they have no JSON:API in core.
- Drupal: SEO data is written into Metatag 2; Metatag 1, which JSON:API cannot write, leaves it out with a note. Drupal 6's Nodewords is not read.
Versions checked
Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
Questions
Can Reloque migrate Payload to Drupal?
Yes. Reloque moves content from Payload to Drupal, for early-access members now. Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB). Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
What does a migration from Payload to Drupal 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 Drupal where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Drupal has a place for them.
Is anything written to Drupal before I approve it?
No. You see every record in the Preview first, then a small sample is written to Drupal so you can check it on the real site, and undo it. Payload is only ever read.