Migration routeIn early access

Migrate from Payload to Ghost

Reloque moves your Payload content into Ghost: posts, pages, media, SEO data and redirects. It maps every field, previews every record and tests a sample on Ghost before the real move.

Join early access Free for early-access members: we look at your Payload site with you before anything moves.

What Reloque reads from Payload

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.

How it lands in 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.

What to plan for

Better to know now than after the switch. The free scan names anything on your site that cannot move.

  • Payload: Payload has no front end, so redirects assume pages at /<slug> and posts at /blog/<slug> until you change them to your routes.
  • Payload: Original publish dates are kept when the collection has a publishedAt field.
  • Payload: With GraphQL turned off, fields are learned from your existing documents, so a collection with none yet takes plain values and leaves out what Payload refuses.
  • Payload: Payload's locales are set in its config only, so add each language the old site has to localization, and mark the fields to translate localized, before you migrate.
  • Payload: Payload has no comments of its own, so comments from another CMS are listed in the handover package.
  • Payload: SEO data goes into an SEO group, your own or the SEO plugin's meta group, field by field; what the group has no field for is named in the run report.
  • Ghost: Members move with their labels and newsletter choices, but paid subscriptions stay in Stripe, so paying members arrive free.
  • Ghost: Ghost has no custom fields, so fields without a place stay in the content export.
  • Ghost: 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.
  • Ghost: Writing needs Ghost 5 or later; Ghost 3 and 4 are sources.
  • Ghost: 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: 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.

Versions checked

  • Payload: Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB).
  • Ghost: Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources.

Questions

Can Reloque migrate Payload to Ghost?

Yes. Reloque moves content from Payload to Ghost, for early-access members now. Checked on Payload 3.92 (Postgres), 2.32 and 1.15 (MongoDB). Checked on Ghost 6.73 and 5.130, and 4.48 and 3.42 as sources.

What does a migration from Payload to Ghost cost?

The assessment is free and gives your exact price: you pay for the records a migration writes, and media files do not count. Packages start at £99, and records are shared across any number of migrations for 12 months.

Will my addresses and SEO survive the move?

Every address that changes gets a redirect, written to Ghost where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Ghost has a place for them.

Is anything written to Ghost before I approve it?

No. You see every record in the Preview first, then a small sample is written to Ghost so you can check it on the real site, and undo it. Payload is only ever read.

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Payload to Ghost. We will look at your site with you before anything moves.

Plan this move with us

Early access is free. Tell us both systems when you reserve.

Free assessment

Moving Payload to Ghost?

Reserve a free assessment and we look at your Payload site with you: what moves to Ghost, what stays, and the price. Nothing is written until you approve it.

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.