What Reloque reads from Umbraco
Reloque reads documents, media and each editor's values through the Management API (15 and later), the Delivery API (12 to 14) or the bridge template (7 to 13). SEO properties, such as seoTitle, metaDescription and noIndex, are read as the page's SEO data too, so they reach the other CMS's SEO fields, and Umbraco's own redirects from renamed and moved pages come with them (15 and later, or the bridge).
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.
- 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.
- 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
Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).
Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
Questions
Can Reloque migrate Umbraco to Payload?
Yes. Reloque moves content from Umbraco to Payload, for early-access members now. Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against). Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
What does a migration from Umbraco 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. Umbraco is only ever read.