CMS guideOpen-source headless CMS

Strapi migration: versions, content types and every route in and out

Strapi is an open-source headless CMS built on Node.js. Editors work in an admin panel while developers model content types and consume them through REST or GraphQL APIs.

Strapi at a glance

Type
Open-source headless CMS
Built with
Node.js, REST and GraphQL, SQL databases
Hosting
Self-hosted, or Strapi Cloud
Best for
JavaScript teams that need a flexible content API
Reloque
Checked on Strapi 5.58 and 4.26, and 3.6 as a source

Ways to connect Strapi

Reloque only ever reads from the source, and connects with what your Strapi version allows.

API token

Strapi 4 and 5Source and destination

A token from Settings › API Tokens, with full access or access to the content types and uploads to move.

Users & Permissions user

Strapi 3Source

Strapi 3 has no API tokens, so Reloque signs in as a user whose role can find, findone and count posts, pages and uploads.

Checked on Strapi 5.58 and 4.26, and 3.6 as a source. The Connect form finds the version at your address and offers the right way in, with a setup guide to download.

How Strapi works

Strapi lets you build content types in an admin panel or in code, and it creates REST and GraphQL APIs for them. Entries can use reusable components and dynamic zones for flexible layouts. It runs on Node.js with a SQL database.

Strapi migration routes

Reloque moves Strapi content in both directions, and between two Strapi sites. 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. Each route is mapped, previewed on the destination and checked by reading every record back.

Strapi to WordPress

Posts follow the site's permalink setting, and with the Redirection plugin installed each old address redirects to its new one, along with the old site's own redirects. Media lands in the Media Library with its alt text, featured images, categories and tags are linked, with categories under their parents, and authors are matched to existing users. Every category and tag comes over, including those no post uses, and so does every term of your own taxonomies. Members can move too, as subscribers, without their passwords. The site's title, tagline, logo and timezone are set where the new site has none yet. Menus arrive as WordPress menus, at the theme location they had, with each link pointed at the moved page. Comments arrive with their replies, under each commenter's own name and email, at their own dates, approved or waiting for a moderator as they were. SEO data goes to Yoast SEO or Rank Math, whichever the new site runs, its social images copied to the Media Library. The WordPress guide covers the other side. Strapi to WordPress, step by step.

Strapi 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. Strapi to Contentful, step by step.

Strapi 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. Strapi to Sanity, step by step.

Strapi 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. Strapi to Webflow, step by step.

Strapi 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. Strapi to Payload, step by step.

Strapi 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. Strapi to Ghost, step by step.

Strapi 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. Strapi to Drupal, step by step.

Strapi 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. Strapi to Umbraco, step by step.

Strapi 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. Strapi to Storyblok, step by step.

Strapi to Strapi

Moving Strapi 3 or 4 content into Strapi 5 is a route like any other: entries, media and relations move, rich text is rewritten to fit each field, and drafts stay drafts. Strapi to Strapi, step by step.

Moving to Strapi

Moving to Strapi starts with building content types that match your content. Use components for repeated structures, and plan how existing relationships become Strapi relations.

WordPress to Strapi

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. More on WordPress to Strapi.

Contentful to Strapi

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 Strapi.

Sanity to Strapi

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 Strapi.

Webflow to Strapi

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 Strapi.

Payload to Strapi

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 Strapi.

Ghost to Strapi

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 Strapi.

Drupal to Strapi

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 Strapi.

Umbraco to Strapi

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 Strapi.

Storyblok to Strapi

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 Strapi.

Planned routes

These connectors are planned. Each guide says what to weigh and plan in the meantime.

A WordPress post, written into Strapi

WordPress Strapi
A WordPress post, written into Strapi
WordPressbecomesStrapi
Titletitle
Contentcontent, as blocks or Markdown
Excerptexcerpt
Featured imagecover, uploaded to the Media Library
Categories and tagscategory and tags, linked
Your own taxonomiesa relation to a collection of terms, created where missing
Publish datepublishedAt, or a date field on Strapi 5
Slugslug, simplified to Strapi's characters
Components and dynamic zonesthe component of the same name, with its files
Relationsthe same records, once they are written
Where each part of a WordPress post goes in a typical Strapi article type. The Map step shows the real fields of both sites, and you confirm each one.

What does not move yet

Better to know now than after the switch. The scan names anything it finds that cannot move.

  • Components and dynamic zones move as blocks between Strapi, Payload and Umbraco; WordPress and Ghost get their content as HTML.
  • Writing needs Strapi 4 or later; Strapi 3 is a source.
  • Strapi adds locales in its admin only, so add each language the old site has under Settings › Internationalization before you migrate.
  • Strapi has no page routes, so check the redirects against your front end.
  • Strapi has no comments of its own, so comments from another CMS are listed in the handover package.
  • SEO data goes into an SEO component, such as shared.seo, field by field; what the component has no field for is named in the run report.

What Strapi does well

Content-type builder

Model content visually, then refine it in code.

REST and GraphQL

Content is available through both API styles.

Self-host or cloud

Run it on your own servers or use Strapi Cloud.

Roles and permissions

Control who can read, edit and publish each content type.

What to weigh before you move

No CMS fits every team. These are the points that come up most when people plan to leave Strapi, or to make it their next home.

  • You maintain the serverSelf-hosting means owning updates, scaling and backups.
  • Upgrades need planningMajor versions should be tested against your content types and plugins.
  • Customisation takes codeBeyond the admin panel, changes need a developer.

Planning a move from Strapi

A Strapi project moves cleanly when its content types and components are documented first.

  • List content types, components and dynamic zones
  • Map relations and decide how they translate
  • Check media library usage and the storage provider
  • Note locales and which entries are translated

Strapi questions

What is Strapi?

Strapi is an open-source headless CMS built on Node.js. Editors work in an admin panel while developers model content types and consume them through REST or GraphQL APIs.

Who uses Strapi?

JavaScript and TypeScript teams, start-ups and agencies use Strapi for websites and apps that need a customisable backend. Its visual content-type builder keeps modelling approachable for mixed teams.

What content can be migrated from Strapi?

Your content types and their entries, the media library, cover images, relations to categories, tags and authors, and rich text in blocks or Markdown, drafts included. Reloque scans the project first and shows what it found before anything moves.

What should I prepare before migrating from Strapi?

A Strapi project moves cleanly when its content types and components are documented first. Four checks help most: (1) list content types, components and dynamic zones; (2) map relations and decide how they translate; (3) check media library usage and the storage provider; (4) note locales and which entries are translated.

Can Reloque move Strapi 3 or 4 content into Strapi 5?

Yes. Strapi 3 and 4 are read as sources and Strapi 5 is written as a destination, so moving to a current Strapi is one of the routes. Rich text is rewritten as blocks or Markdown to fit each field, and drafts stay drafts.

Are Strapi components and dynamic zones migrated?

Not yet. Content types, entries, media and relations to categories, tags and authors move today. Components and dynamic zones are on the list, and the scan names any it finds so nothing is dropped silently.

Can Reloque migrate Strapi today?

Yes. Strapi 4 and 5 connect with an API token, as a source and a destination, and Strapi 3 connects as a source with a Users & Permissions user. Routes run to and from WordPress, Payload, Ghost, Umbraco, Drupal and another Strapi project. Start with a free assessment to see what Reloque finds first.

Free assessment

Moving Strapi content?

Reserve a free assessment and we look at your Strapi site with you: every field mapped and the move previewed before anything is written.

Get your free assessment
Early-access members get a free migration assessment.
  1. Connect both sitesReloque reads the source and checks it may write to the destination.
  2. Check the mappingEvery field is matched, and the uncertain ones are yours to decide.
  3. Test a sampleA few records are written to the destination, read back and removed.
  4. Move the restEvery record is written and checked, with redirects for old addresses.

More CMS guides

All guides