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 Sanity
Records go into the dataset's own document types, matched by name, writing the fields their documents have. A dataset with no posts or pages gets documents shaped as Sanity's blog starter (post, page, category, tag and author), which the Studio shows once its schema has those types. Bodies become Portable Text, with images uploaded as assets and links between records as references. Categories, tags and authors become documents of the types the dataset refers to. Each language becomes a document of its own, tied to the others as document internationalisation does. SEO data goes into an SEO object, menus into navigation documents and redirects into redirect documents. Drafts stay drafts, and published records are published.
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.
- Sanity: Sanity has no members or comments, so neither moves into or out of it.
- Sanity: A block of your own in Portable Text, such as a call to action, keeps only a link to what it points at.
- Sanity: Translations kept field by field inside one document (internationalised arrays) are not read yet; translations as documents of their own are.
- Sanity: Documents Reloque writes into types your Studio has no schema for are stored, but the Studio shows them only once its schema has those types.
- Sanity: Site settings and dictionary items have no place in Sanity, so they are left out.
Versions checked
WordPress: Checked on WordPress 7.1 and 6.0, and 5.5 as a source.
Sanity: One hosted service, so there are no versions to choose. Any Studio version works, as Reloque talks to the project's API.
Questions
Can Reloque migrate WordPress to Sanity?
Yes. Reloque moves content from WordPress to Sanity, for early-access members now. Checked on WordPress 7.1 and 6.0, and 5.5 as a source. One hosted service, so there are no versions to choose. Any Studio version works, as Reloque talks to the project's API.
What does a migration from WordPress to Sanity 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 Sanity where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Sanity has a place for them.
Is anything written to Sanity before I approve it?
No. You see every record in the Preview first, then a small sample is written to Sanity so you can check it on the real site, and undo it. WordPress is only ever read.