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 Umbraco
Each post and page becomes a document, under a document type Reloque creates with the shared fields when yours does not exist. Umbraco sets its own publish date, so the original goes into a Publish date field. A site in several languages moves in every language, and a language the new site lacks is added. Dictionary items, the labels your templates show, move in every language too, and each document keeps its domains and hostnames. SEO data from another CMS fills the document type's SEO properties, such as seoTitle, metaDescription, noIndex and ogImage, with sharing images copied, and what the type has no property for is named in the run report.
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.
- Umbraco: Members move between every CMS here, and never with their passwords.
- Umbraco: Umbraco's navigation is its page tree, so menus from another CMS are listed in the handover package to set up by hand.
- Umbraco: Umbraco has no comments of its own, so comments from another CMS are listed in the handover package.
- Umbraco: SEO properties are known by their names, such as seoTitle, metaDescription and noIndex; one named otherwise is matched on the Map step as a field of its own.
- Umbraco: Umbraco 7 to 14 are sources; writing needs Umbraco 15 or later.
Versions checked
Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
Questions
Can Reloque migrate Payload to Umbraco?
Yes. Reloque moves content from Payload to Umbraco, for early-access members now. Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB). Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
What does a migration from Payload to Umbraco 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 Umbraco where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Umbraco has a place for them.
Is anything written to Umbraco before I approve it?
No. You see every record in the Preview first, then a small sample is written to Umbraco so you can check it on the real site, and undo it. Payload is only ever read.