WordPress at a glance
- Type
- Open-source CMS
- Built with
- PHP and MySQL or MariaDB
- Hosting
- Self-hosted or managed
- Best for
- Content sites, blogs and WooCommerce stores
- Reloque
- Checked on WordPress 7.1 and 6.0, and 5.5 as a source
WordPress migration routes
Reloque moves WordPress content in both directions, and between two WordPress sites. 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. Each route is mapped, previewed on the destination and checked by reading every record back.
WordPress to Contentful
Records go into the space's own content types, matched by name, or into Blog post and Page types Reloque adds when the space has none and your role allows it. Bodies become Rich Text, with images uploaded as assets and links between records as links between entries. Categories, tags and authors become entries of the types the space links to, or Contentful tags. Each language goes into the locale of the same language, in the fields that are localized. SEO data goes into the type's SEO fields or an SEO entry, menus into menu and menu item entries and redirects into redirect entries, with types added for them where the space has none. Published records are published. The Contentful guide covers the other side. WordPress to Contentful, step by step.
WordPress to 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. The Sanity guide covers the other side. WordPress to Sanity, step by step.
WordPress to Webflow
Records go into the site's own collections, matched by name, or into the collections of Webflow's blog template, which Reloque adds when the site has none: Blog Posts, Pages, Categories, Tags and Authors. Bodies stay rich text, with images uploaded as assets and links between records pointing at the new items. Categories, tags and authors become items of their collections, and SEO data goes into the collection's SEO fields. Published records are published, and drafts stay drafts. The Webflow guide covers the other side. WordPress to Webflow, step by step.
WordPress to 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. The Payload guide covers the other side. WordPress to Payload, step by step.
WordPress to Strapi
Bodies are written as Strapi blocks or Markdown, whichever each field is, images go to the Media Library, and cover images, categories, tags and authors are linked, categories under their parents where they have a parent relation. Strapi 5 sets its own publish date, so the original goes into a date field of your own. A site in several languages moves into each locale of a translated type. Members can move too, as Users & Permissions users in the role of their group, without their passwords. With a Redirect type of your own (from and to fields), each old address redirects to its new one; with strapi-plugin-redirects, the handover package has a file to import in its admin page. Menus from another CMS fill a single type's list of links, a main menu the header's and a footer the footer's. The Strapi guide covers the other side. WordPress to Strapi, step by step.
WordPress to Ghost
Bodies are sent as HTML, which Ghost turns into its own editor format. Categories become tags, posts keep their slugs at /<slug>/, and the redirects are added to Ghost's own when you connect with a staff access token (Ghost 5 and later); otherwise the handover package includes a redirects.yaml ready to upload. Comments arrive on their posts at their own dates, each by the member with the commenter's email: you choose on the Map step whether to add a free member for each commenter who is not one, signed up to no newsletter and sent no email. The Ghost guide covers the other side. WordPress to Ghost, step by step.
WordPress to Drupal
Each post and page becomes a node at its old address, as an article, a basic page or the content type you choose, with its fields in each field type's format. Categories and tags go into their vocabularies, nested where they were, images into the Media Library, and authors are matched to the site's users. SEO data from another CMS goes into Metatag's field, with sharing images copied. Menus are added to Main navigation, Footer or a menu of the same name, as JSON:API cannot create menus. Comments arrive with their replies, each by the site's user with the commenter's email or as a visitor. Members become users with no password, who set their own with Drupal's password reset page, and get a role only where it cannot edit the site. JSON:API cannot create Paragraphs, so blocks from another CMS are added to the body. A site in several languages comes in its default language, or each language as a node of its own, as JSON:API cannot add a translation; you choose on the Map step. With the Redirect module installed, each page's old address redirects to its new one, and the old site's own redirects come too. Drupal's JSON:API cannot change site settings, so the run report lists the site name, slogan and time zone to set in Drupal's admin. The Drupal guide covers the other side. WordPress to Drupal, step by step.
WordPress to 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. The Umbraco guide covers the other side. WordPress to Umbraco, step by step.
WordPress to Storyblok
Records go into the space's own content types, matched by name, or into Article and Page types Reloque adds, with categories and authors, when the space has none and your role allows it. Posts go into the folder their type's stories are in, or a Blog folder, and pages to the root. Bodies become rich text, with images uploaded as assets and links between records as links between stories. Categories and authors become stories in folders of their own, and tags Storyblok's own tags. Each language goes into the space's language of the same code, in the fields that are translatable. SEO data goes into the type's SEO fields, menus into a config story's navigation and redirects into redirect stories. Drafts stay drafts, and published records are published. The Storyblok guide covers the other side. WordPress to Storyblok, step by step.
WordPress to WordPress
Between two WordPress sites the editor's own blocks and shortcodes are kept as they are, and media they name by id, such as galleries and file blocks, is copied and renumbered. With the same SEO plugin on both, its titles and descriptions keep their template variables. WordPress to WordPress, step by step.
Moving to WordPress
Moving to WordPress means mapping your content into posts, pages and custom post types. Decide early which fields need a custom-fields plugin, and how your existing URLs map to WordPress permalinks.
Contentful to WordPress
Reloque reads the space through its Content Management API, in every status and every locale. Contentful has no built-in posts or pages, so content types are told apart by name and fields: a type for posts, one for pages, your own types as types of their own, authors, and categories and tags, with Contentful's own tags too. Assets come as media. Rich Text keeps its headings, lists, links, formatting and images, and links between entries point at the moved records. SEO fields, or an SEO entry an entry links to, reach the other CMS's SEO fields, and menu and redirect entries come as menus and redirects. More on Contentful to WordPress.
Sanity to WordPress
Reloque reads the dataset through Sanity's API, drafts included. Sanity keeps its schema in the Studio's code, so document types and their fields are read from the documents themselves, and told apart by name and fields: a type for posts, one for pages, your own types as types of their own, authors, and categories and tags. Images and files come as media. Portable Text keeps its headings, lists, links, formatting and images, and references between documents point at the moved records. Translations made with document internationalisation come as each record's languages, an SEO object reaches the other CMS's SEO fields, and menu and redirect documents come as menus and redirects. More on Sanity to WordPress.
Webflow to WordPress
Reloque reads the site's collections with their fields, and every item, drafts included. Posts, your own collections, authors and categories are told apart by name and fields, references come with what they point at, and categories keep their parents. Images and files come as media, rich text keeps its headings, lists, links, formatting and images, and links between items point at the moved records. SEO fields reach the other CMS's SEO fields, and static pages come as pages with their text, images and SEO settings. More on Webflow to WordPress.
Payload to WordPress
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. More on Payload to WordPress.
Strapi to WordPress
Reloque reads your content types, media and relations with an API token, or as a Users & Permissions user on Strapi 3. Rich text in blocks or Markdown is read as formatting, not as raw text. A translated type is read in every locale, each published or a draft as it is. Single types, such as the site's settings, go to the new site's single types or globals of the same name, and their lists of links become menus on WordPress. Redirects come too, from a Redirect type of your own or strapi-plugin-redirects on Strapi 4. More on Strapi to WordPress.
Ghost to WordPress
Reloque reads posts, pages, tags, authors, images and each one's SEO and sharing fields through the Admin API, from Ghost 3 to 6, or from an export file. The navigation and secondary navigation come too, from Ghost 5 and later or an export file, with their links pointed at the moved pages, and so do comments, with their replies, from Ghost 5 and later. Connected with a staff access token, the site's redirects come too. More on Ghost to WordPress.
Drupal to WordPress
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. More on Drupal to WordPress.
Umbraco to WordPress
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). More on Umbraco to WordPress.
Storyblok to WordPress
Reloque reads the space's content types from its components, and every story with its content, drafts and every language included. Posts, pages, your own content types, authors and categories are told apart by name and fields, and Storyblok's own tags come too. Components inside stories move as blocks, assets come as media, and rich text keeps its headings, lists, links, formatting and images, with links between stories pointing at the moved records. SEO fields reach the other CMS's SEO fields, a config story's navigation comes as menus, and redirect stories as redirects. More on Storyblok to WordPress.
Planned routes
These connectors are planned. Each guide says what to weigh and plan in the meantime.
A WordPress post, written into Payload
| WordPress | becomes | Payload |
|---|---|---|
| Title | title | |
| Content (blocks or classic) | content, as Lexical rich text | |
| Excerpt | excerpt | |
| Featured image | featuredImage, uploaded to Media | |
| Categories and tags | categories and tags, linked | |
| Your own taxonomies | a relationship to a collection of terms, created where missing | |
| Author | author, linked | |
| Slug and permalink | slug, and a row in redirects.csv |
Ways to connect WordPress
Reloque only ever reads from the source, and connects with what your WordPress version allows.
Application password
A user's username and an application password from their profile. The site needs HTTPS, or application passwords switched on.
Export file
WordPress's own export (Tools › Export › All content), uploaded to Reloque. Media is copied from the live site, so it must still be online.
Bridge file
One read-only PHP file with its own key, dropped into wp-content/mu-plugins. It answers only Reloque's signed requests and stops after 30 days.
Checked on WordPress 7.1 and 6.0, and 5.5 as a source. The Connect form finds the version at your address and offers the right way in, with a setup guide to download.
What moves from WordPress
Reloque scans your WordPress site first, maps each field to the destination and previews the move on it before the live run.
- Posts and pages
- Your own post types
- Media library and featured images
- Categories and tags
- Authors
- Drafts, pending and private posts
- Page parents and excerpts
- Images and files in the content
Who uses WordPress
Bloggers, publishers, small businesses, agencies and marketing teams use WordPress because editors can publish without a developer. Online shops often add WooCommerce, and many agencies run a whole portfolio of client sites on it.
What WordPress does well
Large ecosystem
Thousands of themes and plugins cover most common needs without custom code.
Familiar editing
Editors get a visual block editor, a media library and roles that many already know.
Hosting choice
Run it yourself, on managed hosting or on WordPress.com.
Community and talent
Documentation, agencies and freelancers are easy to find.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave WordPress, or to make it their next home.
- Plugin upkeepPlugins and themes need regular updates, and each one adds something to maintain.
- Layout stored in contentPage builders and blocks can store layout inside content, which needs cleaning up when you move.
- Performance depends on setupSpeed relies on hosting, theme and caching choices.
Planning a move from WordPress
A WordPress site often holds years of content, so a good plan starts with an honest inventory of what is worth moving.
- List your custom post types and the plugins that add fields to them
- Decide what to do with page-builder layouts, which are often stored inside the content
- Note permalinks and redirects so URLs keep working after the move
- Check how many media files are in use and where they are stored
What does not move yet
Better to know now than after the switch. The scan names anything it finds that cannot move.
- 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.
- Page-builder layouts move as the HTML they render, not as builder settings.
WordPress questions
What is WordPress?
WordPress is an open-source content management system, first built for blogging and now used for everything from personal sites to large publishers. Content lives in a database and is managed through a browser-based editor and a large plugin and theme system.
Who uses WordPress?
Bloggers, publishers, small businesses, agencies and marketing teams use WordPress because editors can publish without a developer. Online shops often add WooCommerce, and many agencies run a whole portfolio of client sites on it.
What content can be migrated from WordPress?
Posts, pages and your own post types, in every status, with their media library, featured images, categories, tags, authors, excerpts and page parents. Images and files inside the content are copied too, so nothing keeps loading from the old site. Reloque scans the site first and shows what it found before anything moves.
What should I prepare before migrating from WordPress?
A WordPress site often holds years of content, so a good plan starts with an honest inventory of what is worth moving. Four checks help most: (1) list your custom post types and the plugins that add fields to them; (2) decide what to do with page-builder layouts, which are often stored inside the content; (3) note permalinks and redirects so URLs keep working after the move; (4) check how many media files are in use and where they are stored.
Can I migrate WordPress to Payload?
Yes. Reloque reads posts, pages, media, categories, tags and authors from WordPress and writes them into your Payload collections: bodies become Lexical rich text, images are uploaded to Media and relationships are linked. The handover package lists every old address and its new one for your redirects.
Which WordPress versions can Reloque read?
WordPress 5.6 and later connects through its REST API with an application password, and is checked on 6.0 and 7.1. Older sites, or sites with application passwords switched off, connect with their export file or the Reloque bridge file. Writing to WordPress needs 5.6 or later.
Can Reloque migrate WordPress today?
Yes. WordPress 5.6 and later connects with an application password, and any version with its export file or the Reloque bridge file. It works as a source and a destination: to and from Payload, Strapi, Ghost, Umbraco, Drupal and another WordPress site. Start with a free assessment: Reloque scans the site and shows what it found before anything moves.