CMS guideOpen-source CMS

Drupal migration: what moves, and how to plan it

Drupal is an open-source CMS known for flexible content modelling, fine-grained permissions and multilingual support. It runs everything from small sites to large institutional platforms.

Drupal at a glance

Type
Open-source CMS
Built with
PHP
Hosting
Self-hosted or managed hosting
Best for
Complex, multilingual, permission-heavy sites
Reloque
Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file)

Ways to connect Drupal

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

JSON:API

Drupal 8.7 to 11Source and destination

JSON:API and HTTP Basic Authentication, both part of core, turned on in Extend, and a user's name and password. A destination also needs JSON:API to accept writes.

Bridge file

Drupal 6 to 8.6Source

A read-only PHP file put in the site's root, beside index.php. It answers only requests signed with its key, and stops after 30 days.

Checked on Drupal 11, 10, 9 and 8.9, and 8.6, 7 and 6 as sources (bridge file). The Connect form finds the version at your address and offers the right way in, with a setup guide to download.

Drupal migration routes

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

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

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

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

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

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

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

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

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

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

Drupal to Drupal

Between two Drupal sites, such as Drupal 10 onto 11, nodes keep their addresses, fields, terms, Media and authors. Paragraphs are added to the body, as JSON:API cannot create them. Drupal to Drupal, step by step.

Moving to Drupal

Moving to Drupal means designing content types, fields and vocabularies up front. Plan roles and permissions at the same time, since they are central to how Drupal works.

WordPress to Drupal

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

Contentful to Drupal

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

Sanity to Drupal

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

Webflow to Drupal

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

Payload to Drupal

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

Strapi to Drupal

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

Ghost to Drupal

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

Umbraco to Drupal

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

Storyblok to Drupal

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

Planned routes

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

A Drupal article, written into WordPress

Drupal WordPress
A Drupal article, written into WordPress
DrupalbecomesWordPress
Body and summaryContent and excerpt
Image fieldFeatured image
Tags and Categories vocabulariesTags and categories
Another vocabulary (Region)A taxonomy of its own
field_pricelisting_price_gbp
ParagraphsBlocks in the content
Media itemsMedia Library
Where each part of a Drupal article lands in WordPress. Fields are matched by name, without Drupal's field_ prefix.

What moves from Drupal

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

Drupal logoContent inventoryRead by the connector
  • Nodes and content types
  • Fields
  • Taxonomy terms
  • Media entities
  • Users and authors
  • Translations
The scan lists what your site holds before anything moves, with anything it cannot carry named.

Who uses Drupal

Governments, universities, large non-profits and enterprises use Drupal when they need structured content, editorial workflows and detailed access control. Teams usually have in-house or agency developers.

What Drupal does well

Content modelling

Content types and fields can describe almost any structure.

Granular permissions

Roles control exactly who can do what.

Multilingual by design

Translation is built into content, fields and the interface.

Taxonomy and structure

Vocabularies and terms organise large content libraries.

What to weigh before you move

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

  • A steeper learning curveIts flexibility takes time to learn.
  • Upgrades take planningMoving between major versions can be a sizeable project.
  • Developer timeComplex sites usually rely on skilled developers.

What does not move yet

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

  • Drupal's JSON:API cannot add a translation to a node, so each language goes into Drupal as a node of its own, not linked to the others.
  • Drupal's JSON:API cannot read or change site settings, so on Drupal 8.7 and later they are read from the public site (not the time zone), and into Drupal they are set by hand from the run report.
  • Drupal's JSON:API can only block a user it removes, so a sample test adds no members, and undoing a migration blocks the members it added rather than deleting them.
  • Drupal's JSON:API cannot create a menu, so a menu goes into one the site has; add a missing one under Structure › Menus.
  • Drupal's JSON:API cannot create Paragraphs, so blocks written into Drupal are added to the body.
  • Drupal 6, 7 and 8.0 to 8.6 are sources, through the bridge file, as they have no JSON:API in core.
  • SEO data is written into Metatag 2; Metatag 1, which JSON:API cannot write, leaves it out with a note. Drupal 6's Nodewords is not read.

Planning a move from Drupal

Drupal sites tend to be large and structured, so the inventory is the most important step.

  • List content types and the fields on each
  • Review taxonomy vocabularies and how content uses them
  • Check translations and which content is multilingual
  • Note modules that add fields or paragraph-style structures

Drupal questions

What is Drupal?

Drupal is an open-source CMS known for flexible content modelling, fine-grained permissions and multilingual support. It runs everything from small sites to large institutional platforms.

Who uses Drupal?

Governments, universities, large non-profits and enterprises use Drupal when they need structured content, editorial workflows and detailed access control. Teams usually have in-house or agency developers.

What content can be migrated from Drupal?

A migration from Drupal typically covers nodes and content types, fields, taxonomy terms, media entities, users and authors and translations. Reloque inspects your content first and shows what it found before anything moves.

What should I prepare before migrating from Drupal?

Drupal sites tend to be large and structured, so the inventory is the most important step. Four checks help most: (1) list content types and the fields on each; (2) review taxonomy vocabularies and how content uses them; (3) check translations and which content is multilingual; (4) note modules that add fields or paragraph-style structures.

Can Reloque migrate Drupal today?

Yes. Drupal 8.7 to 11 connect through JSON:API, which is part of core, with a user's name and password, as a source and a destination. Routes run to and from WordPress, Payload, Strapi, Ghost, Umbraco and another Drupal site, so moving Drupal 10 onto 11 is a route too. Drupal 6, 7 and 8.0 to 8.6 connect as sources with the Reloque bridge file, a PHP file put in the site's root.

Free assessment

Moving Drupal content?

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