What Reloque reads from WordPress
Reloque reads posts, pages, your own post types, media, categories, tags, your own taxonomies, authors, menus, comments, SEO data, the Redirection plugin's redirects and custom fields through the REST API, an export file or the bridge file. The REST API shows only the fields a plugin registers, such as ACF's; the export file and the bridge read every one. SEO data comes from Yoast SEO or Rank Math: the SEO title and description you set, the focus keyword, the canonical address, noindex and nofollow, and the social title, description and image, but not what the plugin makes from its templates.
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.
- WordPress: Rank Math's REST API does not show its SEO data, so connect a Rank Math site with its export file or the bridge file to move it. Yoast's REST API takes SEO data on posts only, and of it only the SEO title, description and focus keyword (older Yoast, such as 19.6, takes none); what a WordPress destination with Yoast cannot take is named in the run report.
- WordPress: Page-builder layouts move as the HTML they render, not as builder settings.
- 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
WordPress: Checked on WordPress 7.1 and 6.0, and 5.5 as a source.
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 WordPress to Umbraco?
Yes. Reloque moves content from WordPress to Umbraco, for early-access members now. Checked on WordPress 7.1 and 6.0, and 5.5 as a source. 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 WordPress 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. WordPress is only ever read.