Ghost to WordPress

WordPress hosting for publications moving off Ghost.

Ghost exports a single JSON document, stores content as structured data rather than HTML, and sends its own newsletters. None of those three assumptions holds in WordPress.

JSON export translatedMembers carried deliberatelyFree migration
Free migrationStructured content convertedMembership planDaily backupsFree SSL24/7 support
Three assumptions to unwind

What a Ghost publication needs on the way out.

The posts are the straightforward part. The audience and the billing behind it are what need planning.

A JSON export, not WordPress XML

Ghost produces one JSON document containing posts, tags and authors. Nothing imports it directly, so it is translated rather than uploaded.

Posts, tags, authorsTranslated on import

Structured content converted to blocks

Ghost stores content as structured data rather than HTML. A naive conversion flattens cards and embeds into plain paragraphs, which is only obvious once it is published.

Paid members and the billing behind them

Members are the part that cannot simply be re-imported. The subscription relationship has to be carried deliberately, and that is planned before anything moves.

Stripe relationship planned first

Flat URLs preserved

Ghost URLs carry no date or category segment, so matching them means choosing a WordPress permalink structure that behaves the same way.

Newsletters rebuilt

Ghost sends email itself; WordPress does not. A publication that emailed every post needs that capability chosen and tested before launch.

Migration

The audience matters more than the archive.

Posts can be re-imported if something goes wrong. A broken billing relationship with paying members cannot, which is why that part is planned first.

  • Membership and billing approach agreed before the move
  • Content converted and reviewed on a temporary domain
  • Cutover at a time you choose
  • Ghost site left live until you confirm
Content
Converted to blocks
412 posts
Members
Migrated with billing intact
1,830
Newsletter
Rebuilt and tested
ready
DNS cutover
Awaiting your go-ahead
scheduled
Performance

Member pages, which cannot be cached.

A paid publication serves most of its value to signed-in readers, and no page cache helps there. What decides it is the object cache and the database.

Free
migration, done by us
Redis
object cache, on by default
14
edge regions
MagicWP135 ms
Untuned membership site820 ms
No object cache400 ms

Illustrative comparison of a signed-in member request after migration. Your numbers depend on membership plugin and article volume.

Configuration

What this move needs that a host migration does not

Ghost is a narrower product than WordPress, so several things it did for you become explicit choices here.

SettingWhat we doWhy
Export formatGhost JSON translated into posts, tags and authorsGhost produces a single JSON document rather than WordPress XML, so no standard importer will take it without translation.
Content formatStructured content converted to blocks rather than pasted as HTMLGhost stores structured data, and a naive conversion silently flattens cards and embeds into plain paragraphs.
Members and subscriptionsMigrated to a membership plugin with the billing relationship planned firstPaid members are the one part of a Ghost site that cannot be re-imported if it goes wrong, because the money is attached to it.
URL structureFlat /slug/ addresses preserved by permalink choiceGhost URLs carry no date or category segment, so keeping them means picking a WordPress structure that does the same rather than redirecting everything.
Newsletter sendingReplaced explicitly and tested before launchGhost sends email as part of the product; WordPress does not, so a publication that emailed its posts loses that capability unless it is rebuilt.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Ghost exports JSON. Can WordPress import that?
Not directly. It is a single JSON document rather than WordPress XML, so it is translated into posts, tags and authors on the way in rather than uploaded to the standard importer.
What happens to my paid members?
They move to a membership plugin, and the billing relationship is planned before anything else. Members are the one part of a Ghost site that cannot simply be re-imported if it goes wrong, because there is money attached.
Will my post formatting survive?
If it is converted rather than pasted. Ghost stores structured content rather than HTML, and a careless conversion flattens cards and embeds into plain paragraphs — which only becomes obvious after publishing.
Can I keep my URLs exactly as they are?
Usually yes, by choosing a matching permalink structure. Ghost URLs have no date or category segment, so the goal is a WordPress structure that behaves the same rather than a redirect for every post.
Ghost sends my newsletter. What replaces it?
Something chosen and tested before launch. Email sending is part of the Ghost product and simply does not exist in WordPress, so it is the capability most often discovered missing the week after a move.

Move off Ghost without risking the paying audience.

Free migration, structured content converted properly, and billing planned before anything switches.