Ghost → WordPress
Analyze and move supported Ghost publication content into a prepared WordPress site through explicit post, page, author, tag, media, URL, and editorial-state mapping, a representative dry run, reconciliation, and controlled cutover. The live APP direction is stable, while members, newsletters, tiers, offers, payments, protected content, and custom routes require separate destination, privacy, and validation decisions.
Self-service migration path
Source and target connectors are available. ghost: Available. wordpress: Available. Review system status and directions. Available migration objects and capabilities depend on the selected source and target systems.
Create an account, connect a staging destination, and let the app analyze the supported scope for this direction.
No credit card required to analyze the migration and run a free sample.
Scope
The app confirms available entities after connection. Final coverage depends on source access, downloadable assets, and the destination model you prepare.
Before you connect
Use a staging destination and the least-privilege access supported by each platform. Do not send credentials through a public form.
Provide the Ghost Admin URL, API version, and a Custom Integration Admin API key. This is the recommended server-side source path for common publication records.
User or session authentication may be required for records not available to an integration. Two-factor verification and least-privilege handling are planned before access is accepted.
Provide a prepared staging site and an Application Password. Confirm destination post types, taxonomies, users, SEO fields, media rules, and membership boundaries.
How it works
You control each stage in the app. Optional expert assistance is available for custom data or destination requirements.
Start in the app and select the real source and target.
Authorize read access to Ghost and connect a prepared staging WordPress destination.
Review detected records, available entities, media, URLs, and anything that needs a decision.
Choose where supported Ghost data belongs in the prepared WordPress model.
Move a small set of real records to staging and inspect the result before purchasing the full migration.
Review counts, records, media, links, warnings, and exceptions, then purchase and start the full migration when ready.
Technical detail
Open only the detail you need for planning, mapping, or validation.
This page is synchronized with the stable Ghost capability and WordPress destination snapshot. Ghost supports both directions and exposes a broader publication model than standard WordPress content entities.
The current catalog exposes Attachment, Author, Content, Member, Newsletter, Offer, Tag, Tier. Posts and pages share the content entity, while members, newsletters, tiers, and offers remain distinct records.
The standard destination covers authors, categories, tags, posts and pages, comments, media, menus, menu items, metadata, and redirects. It does not create a Ghost-equivalent membership business model automatically.
Standard means the current adapters expose a direct structured path. Review means destination semantics or access must be approved. Custom means WordPress has no equivalent standard entity or the feature belongs to a separate application workstream.
| Ghost source | WordPress target | Status and boundary |
|---|---|---|
| Posts | WordPress posts or a custom post type | Standard: title, HTML, excerpt, dates, status, authors, tags, and supported attachments are mapped. |
| Pages | WordPress pages | Standard: Ghost pages are read through their own endpoint and routed by content type. |
| Staff authors | WordPress authors | Review: content identity can map; Ghost roles, passwords, sessions, and ownership rules do not transfer automatically. |
| Tags and internal tags | Tags, categories, or custom taxonomies | Review: public and internal taxonomy semantics need an explicit destination rule. |
| Feature and inline media | WordPress Media Library | Standard with validation: files must be downloadable, accepted, uploaded, and referenced from destination content. |
| Published, draft, scheduled, and sent state | WordPress editorial state | Review: status translation and scheduled publication behavior are tested in the destination workflow. |
| Members and labels | CRM, membership plugin, users, or custom records | Custom/restricted: identity, consent, subscription state, and account activation require a separate model. |
| Newsletters | Email service or WordPress newsletter plugin | Custom: sender settings, audience, templates, delivery, and subscriptions are application behavior. |
| Tiers and offers | Membership or commerce records | Custom: pricing, benefits, currencies, Stripe relationships, and access rules need a dedicated implementation. |
| Ghost comments | WordPress comments | Custom: Comment is not a configured Ghost entity in the current app catalog. |
| Theme, routes, code injection, and integrations | Theme, templates, plugins, redirects, and custom code | Rebuild: site presentation and application configuration do not transfer as content records. |
The mapping contract separates editorial content from membership and newsletter operations, preserving source identity and recording every destination decision.
| Ghost value | Migration rule | WordPress result |
|---|---|---|
| Content ID and type | Preserve source identity and route `post` or `page` into the approved destination type | Stable WordPress post/page ID for reruns |
| Title, HTML, excerpt, dates | Normalize supported HTML and translate publication state | WordPress title, content, excerpt, dates, and status |
| Author relation | Load authors first and resolve the destination identity | WordPress author assignment without Ghost credentials |
| Tag names and slugs | Apply public/internal taxonomy rules and resolve term IDs | WordPress taxonomy relationships |
| Attachment path | Download, validate, upload, and rewrite references | Media Library item and destination URL |
| Member, newsletter, tier, or offer | Route to approved CRM/plugin/custom scope or exclude explicitly | Documented operational outcome, not a silent user import |
Ghost combines publishing, newsletters, memberships, access tiers, and offers. WordPress can represent those functions only after plugins, services, consent, and account workflows are selected.
Map posts, pages, authors, tags, status, dates, HTML, and assets into the prepared editorial model independently from paid access.
Decide whether members belong in a CRM, email platform, membership plugin, WordPress users, or a separate system before moving personal data.
Preserve opt-in, newsletter assignment, tier, and account state only through a reviewed model that can enforce the same business meaning.
Stripe customers, subscriptions, prices, offers, access rules, billing notices, and failed-payment behavior require dedicated migration and testing.
Ghost posts, pages, tag archives, author pages, custom routes, and WordPress permalinks can produce different public URL sets even when the content body is unchanged.
Crawl posts, pages, tags, authors, pagination, custom routes, feeds, member pages, and priority inbound URLs.
Map every valuable source URL to a relevant destination and separate content redirects from removed membership or application routes.
Validate titles, descriptions, canonicals, social metadata, headings, internal links, media paths, structured data, and sitemap entries.
Track errors, redirects, canonical selection, indexed URLs, landing-page traffic, forms, and conversions after technical delivery.
The project is accepted only when content records reconcile and every membership, newsletter, payment, or route boundary has an explicit owner and outcome.
Compare posts, pages, authors, tags, attachments, status groups, loaded, skipped, failed, and unresolved totals.
Review cards, embeds, code blocks, galleries, feature images, internal links, protected content, and representative long posts.
Verify rendering, authors, taxonomies, media, schedules, permalinks, redirects, sitemap, analytics, and priority conversion paths.
Document the destination or exclusion for members, labels, newsletters, tiers, offers, payments, comments, and integrations.
Before purchase
The free sample migration creates a limited set of records in staging. Check fields, relationships, media, URLs, rendering, and reported exceptions before paying for the full run.
Pricing
Package fit depends on supported record volume and complexity. Analyze the source first, then review the fixed package or dynamic estimate shown for the migration.
Compare migration packagesPlan the move
Separate archive content from member access and subscription work.
Open guide →Review the prepared WordPress model, authors, taxonomies, media, SEO, and custom fields.
Open guide →Review pages, assets, comments, special blocks, profile boundaries, and website-builder reconstruction.
Open guide →Compare a public blog migration focused on posts, comments, labels, media, feeds, and permalink continuity.
Open guide →Clear answers
Yes. The current Ghost content adapter reads posts and pages separately, identifies their type, and maps supported editorial fields into a prepared WordPress post or page model.
Yes with approved identity and taxonomy rules. Ghost credentials, roles, sessions, and internal-tag behavior do not become equivalent WordPress accounts or taxonomies automatically.
Not as a default one-to-one import. Members contain subscription and privacy context, while WordPress users alone do not reproduce Ghost membership, consent, email, tier, or access behavior.
They require custom scope and a selected destination service or plugin. Sender settings, subscriptions, prices, benefits, payments, and access rules must be implemented and tested separately.
No. Ghost themes, routes, code injection, templates, components, and integrations require WordPress-native design and development.
Supported fields and URLs can be mapped, but WordPress permalinks and SEO storage must be approved. Redirects, canonicals, links, sitemap entries, and priority pages are validated at launch.
No. Search systems, email delivery, payment services, and subscriber behavior are externally controlled. The project reduces risk through explicit mapping, testing, monitoring, and rollback decisions.
Next step
Create an account, select Ghost and WordPress, and analyze publication content, memberships, routes, destination readiness, and validation requirements.
