Who uses Ghost
Independent writers, creators, media start-ups and publications use Ghost to publish and grow an audience. It is common where email newsletters and subscriptions are central.
What Ghost does well
Built for publishing
The editor, themes and defaults all serve writing and reading.
Newsletters and memberships
Email and paid subscriptions are part of the platform.
A focused editor
Cards add images, embeds and other blocks without clutter.
APIs for custom front ends
The Content API and Admin API support headless use.
Ghost migration routes
Reloque moves Ghost content in both directions, and between two Ghost sites. 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. Each route is mapped, previewed on the destination and checked by reading every record back.
Ghost 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. Ghost to WordPress, step by step.
Ghost 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. Ghost to Contentful, step by step.
Ghost 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. Ghost to Sanity, step by step.
Ghost 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. Ghost to Webflow, step by step.
Ghost 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. Ghost to Payload, step by step.
Ghost 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. Ghost to Strapi, step by step.
Ghost 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. Ghost to Drupal, step by step.
Ghost 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. Ghost to Umbraco, step by step.
Ghost 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. Ghost to Storyblok, step by step.
Ghost to Ghost
Between two Ghost sites, Ghost's own editor content moves as it is, so cards such as galleries, buttons, callouts, toggles and HTML cards stay cards, with their images and files copied. Ghost 3 and 4 sources move as HTML. Ghost to Ghost, step by step.
Moving to Ghost
Moving to Ghost suits publications with posts, pages and tags. Check how your current categories map to tags, and how authors will be assigned.
WordPress to Ghost
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 Ghost.
Contentful to Ghost
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 Ghost.
Sanity to Ghost
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 Ghost.
Webflow to Ghost
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 Ghost.
Payload to Ghost
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 Ghost.
Strapi to Ghost
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 Ghost.
Drupal to Ghost
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 Ghost.
Umbraco to Ghost
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 Ghost.
Storyblok to Ghost
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 Ghost.
Planned routes
These connectors are planned. Each guide says what to weigh and plan in the meantime.
What moves from Ghost
Reloque scans your Ghost site first, maps each field to the destination and previews the move on it before the live run.
- Posts and pages
- Images and files
- Feature images
- Tags
- Authors
- Cards, between Ghost sites
A Ghost post, written into WordPress
| Ghost | becomes | WordPress |
|---|---|---|
| Title | Title | |
| Post content and cards | Content, as HTML | |
| Excerpt | Excerpt | |
| Feature image | Featured image, in the Media Library | |
| Tags | Tags | |
| Authors | Author, matched to a user | |
| Slug | Slug, and a row in redirects.csv |
Ways to connect Ghost
Reloque only ever reads from the source, and connects with what your Ghost version allows.
Admin API key
The Admin API key of a custom integration (Settings › Integrations), or an Administrator's staff access token (Ghost 5 and later), which also lets redirects move. Reloque finds which Admin API the site answers and signs for it.
Export file
Ghost's JSON export (Settings › Import/Export), uploaded to Reloque. Images are copied from the live site, so it must still be online.
Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources. The Connect form finds the version at your address and offers the right way in, with a setup guide to download.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave Ghost, or to make it their next home.
- Narrower scopeComplex content models and very large sites need more than Ghost offers.
- Few content typesPosts and pages are the core types, with tags and authors for structure.
- Themes use HandlebarsDesign changes need a developer who knows the theme language.
What does not move yet
Better to know now than after the switch. The scan names anything it finds that cannot move.
- Members move with their labels and newsletter choices, but paid subscriptions stay in Stripe, so paying members arrive free.
- Ghost has no custom fields, so fields without a place stay in the content export.
- Ghost lets only its staff change its settings and navigation, so the site's title, logo and menus are set in its admin after a move. The handover package lists every menu link at its new address.
- Writing needs Ghost 5 or later; Ghost 3 and 4 are sources.
- Ghost has comments on posts only, so comments on pages are listed in the handover package, as are comments by people with no email.
- Ghost has no noindex, nofollow or focus keyword for a post, so those are named in the run report; the SEO title, description, canonical address and sharing fields arrive, with sharing images copied.
Planning a move from Ghost
Ghost sites are usually straightforward to move because the content model is small. The main work is keeping URLs intact and handling subscribers separately.
- Export posts, pages, tags and authors
- Plan how members and subscriptions are handled, separately from content
- Record redirects and custom routes in your theme
- Check images and cards such as embeds and bookmarks
Ghost questions
What is Ghost?
Ghost is an open-source publishing platform focused on writing, newsletters and paid memberships. It has a clean editor and keeps its feature set small on purpose.
Who uses Ghost?
Independent writers, creators, media start-ups and publications use Ghost to publish and grow an audience. It is common where email newsletters and subscriptions are central.
What content can be migrated from Ghost?
Posts and pages with their tags, authors, feature images and the images and files in them. Between two Ghost sites, Ghost's own cards move as cards. Reloque scans the site first and shows what it found before anything moves.
What should I prepare before migrating from Ghost?
Ghost sites are usually straightforward to move because the content model is small. The main work is keeping URLs intact and handling subscribers separately. Four checks help most: (1) export posts, pages, tags and authors; (2) plan how members and subscriptions are handled, separately from content; (3) record redirects and custom routes in your theme; (4) check images and cards such as embeds and bookmarks.
Can I move from Ghost to WordPress?
Yes. Posts, pages, tags, authors and images move into WordPress, with images uploaded to the Media Library. Authors are matched to existing WordPress users, and the handover package lists the redirects from the old Ghost addresses.
What happens to Ghost members and newsletters?
Ghost members, paid subscriptions and newsletters do not move with content. Export members from Ghost's Members screen and import them into your new platform's own tools.
Can Reloque migrate Ghost today?
Yes. Ghost 5 and 6 connect with an Admin API key, as a source and a destination. Ghost 3 and 4 connect the same way as a source, and any version can be read from its export file. Routes run to and from WordPress, Payload, Strapi, Umbraco, Drupal and another Ghost site.