Ghost migration

See your archive on Pyre before you move.

Export. Import. Private preview. Domain last. The live site stays put until the result is verified.

The sequence

  1. Fresh Ghost export

    JSON from Ghost Admin or a copy of the SQLite database. The original stays untouched.

  2. Import into a separate publication

    Publication data, authors, tags, content, status, and relationships in one transaction. Repeat runs skip existing slugs.

  3. Private preview

    Counts compared. Important URLs crawled. Representative posts inspected. You get a staging URL.

  4. Reversible cutover

    Domain moves only after approval. Mail records stay a separate safety boundary. Prior site remains rollback until verification.

What the importer carries

  • Posts and pages — title, slug, body, excerpt, dates, publish state.
  • Tags and relationships — archive taxonomy stays connected.
  • Publication basics and authorship — clean seed for the new publication.
  • Scheduled content — dates preserved for review.

Members, third-party integrations, custom theme behavior, and email sending are reviewed separately. Migration is a verified project — not a one-click parity claim.

From the operator's desk

Replacing Ghost with Pyre

The Solo Stack documents the real migration — what broke, what held, and the rebuild lesson that now guards cutover.

Private beta

Request a migration review.

One email. We review fit for the concierge beta. No account is created. Nothing is provisioned until we talk.

Used only for this beta request and essential Pyre updates.Privacy. No spam. No list sales.