What Reloque reads from Drupal
Reloque reads every content type's nodes through JSON:API, or the bridge file on Drupal 6 to 8.6: articles as posts, basic pages as pages, your own types as types of their own, with their fields, Paragraphs as blocks, Media and files, every vocabulary's terms and each node's author. SEO data comes from Metatag: the tags an editor set for a node, not Metatag's defaults, so it reaches the other CMS's SEO fields. Members come too when you choose them: users who only visit the site, never your editors, with their roles and fields but never their passwords. Menus come too, with each link pointed at the moved page, and comments with their replies, visitors' names and emails, and whether each was approved. Every language comes too: each node with its translations, in their own titles, aliases and fields. So do the Redirect module's redirects, each pointed at its page's new address, and the site's name, slogan, language, logo and icon. Links between nodes point at their aliases.
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.
What to plan for
Better to know now than after the switch. The free scan names anything on your site that cannot move.
- 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.
- 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
Drupal: Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file).
Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
Questions
Can Reloque migrate Drupal to Payload?
Yes. Reloque moves content from Drupal to Payload, for early-access members now. Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file). Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
What does a migration from Drupal 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. Drupal is only ever read.