CMS guideHeadless CMS with visual editor

Storyblok migration: what moves, and how to plan it

Storyblok is a headless CMS built around reusable components. Editors assemble pages in a visual editor while developers render the same components in any front end.

Storyblok at a glance

Type
Headless CMS with a visual editor
Built with
API-first, component-based content
Hosting
Managed by Storyblok
Best for
Marketing teams working with developers
Reloque
One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself

Storyblok migration routes

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

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

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

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

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

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

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

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

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

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

Storyblok to Storyblok

Between two spaces, stories keep their content types, components, folders, assets, tags and languages, and rich text stays rich text. Storyblok to Storyblok, step by step.

Moving to Storyblok

Moving to Storyblok begins with designing the component library. Decide which parts of a page become components, and how folders and slugs map to your existing URLs.

WordPress to Storyblok

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

Contentful to Storyblok

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

Sanity to Storyblok

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

Webflow to Storyblok

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

Payload to Storyblok

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

Strapi to Storyblok

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

Ghost to Storyblok

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

Drupal to Storyblok

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

Umbraco to Storyblok

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

Planned routes

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

Ways to connect Storyblok

Reloque only ever reads from the source, and connects with a token you can revoke in Storyblok at any time.

Personal access token

Every space, in any regionSource and destination

A space ID (Settings › Space) and a personal access token from My account › Personal access tokens. The token acts as your user, so a destination needs the Editor role, or Admin to add content types the space is missing.

One hosted service, so there are no versions to choose. Spaces in every region work, and Reloque finds the region itself. The Connect form finds your content and checks what the token may do, with a setup guide to download.

A Storyblok article, written into WordPress

Storyblok WordPress
A Storyblok article, written into WordPress
StoryblokbecomesWordPress
Title and slugTitle and slug
Rich text bodyContent, with images in the Media Library
ExcerptExcerpt
Image assetFeatured image
Category storiesCategories, under their parents
Storyblok tagsTags
Author storyAuthor
seo_title and seo_descriptionYoast SEO or Rank Math
Where each part of a Storyblok story lands in WordPress. Fields are matched by name, and references by the stories they point at.

What moves from Storyblok

Reloque scans your Storyblok site first, maps each field to the destination and previews the move on it before the live run.

Storyblok logoContent inventoryRead by the connector
  • Stories of every content type
  • Components (blocks)
  • Assets
  • Rich text
  • Languages
  • Links between stories
  • Categories, tags and authors
  • SEO fields
  • Menus and redirects
The scan lists what your site holds before anything moves, with anything it cannot carry named.

How Storyblok works

Storyblok stores content as stories built from components, sometimes called bloks. Editors arrange components in a visual editor, and developers render them in the front end. Stories sit in folders, and assets are managed in a library.

Who uses Storyblok

Marketing teams, e-commerce brands and agencies use Storyblok when editors want to preview and arrange pages themselves without giving up a developer-built front end.

What Storyblok does well

Visual editor

Editors see changes in context as they work.

Component-based content

Reusable blocks keep pages consistent and flexible.

Multi-language support

Content can be managed in several languages.

API-first delivery

Content reaches any front end through APIs.

What to weigh before you move

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

  • Components need design up frontThe component library is a design decision that is hard to reverse.
  • Needs a front endDevelopers build and maintain the website itself.
  • Plan limitsCheck seats, spaces and traffic limits against your needs.

What does not move yet

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

  • Storyblok has no members or comments, so neither moves into or out of it.
  • Components placed inside rich text are left out; components in block fields move as blocks.
  • Reloque does not add languages: add each under Settings › Internationalization first, or it is left out with a note.
  • Content types Reloque adds to a space stay after an undo, as other CMSs keep types it adds.
  • Site settings and dictionary items have no place in Storyblok, so they are left out.

Planning a move from Storyblok

Storyblok content is nested inside components, so the plan should cover how those nested structures translate.

  • List components and where each one is used
  • Note nested and reusable components inside stories
  • Review the folder structure and slugs
  • Check datasources and language variants

Storyblok questions

What is Storyblok?

Storyblok is a headless CMS built around reusable components. Editors assemble pages in a visual editor while developers render the same components in any front end.

Who uses Storyblok?

Marketing teams, e-commerce brands and agencies use Storyblok when editors want to preview and arrange pages themselves without giving up a developer-built front end.

What content can be migrated from Storyblok?

Reloque moves stories of every content type with their components, assets, rich text, every language of the space, links between stories, categories, Storyblok tags, authors, SEO fields, menus and redirects. It inspects the space first and shows what it found before anything moves.

What should I prepare before migrating from Storyblok?

Storyblok content is nested inside components, so the plan should cover how those nested structures translate. Four checks help most: (1) list components and where each one is used; (2) note nested and reusable components inside stories; (3) review the folder structure and slugs; (4) check datasources and language variants.

Can Reloque migrate Storyblok today?

Yes. Storyblok connects through its Management API with a space ID and a personal access token, as a source and a destination, in every region. Routes run to and from WordPress, Payload, Strapi, Ghost, Umbraco, Drupal, Contentful, Sanity and Webflow, and between two Storyblok spaces.

Free assessment

Moving Storyblok content?

Reserve a free assessment and we look at your Storyblok 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