WordPress → Ghost
Move a WordPress publication into Ghost with explicit content cleanup, post and page routing, taxonomy consolidation, media transfer, URL planning, and staging validation. Plugins, themes, comments, memberships, and application behavior are reviewed separately.
Self-service migration path
Source and target connectors are available. wordpress: Available. ghost: 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 site URL plus an Application Password for the migration user, or approve a compatible Bridge when REST does not expose required post types, fields, media, comments, or plugin-owned data.
Provide the Ghost Admin URL and an Admin API integration key with the required write access. Session authentication is considered only when integration access cannot support approved entities.
Create required staff users, confirm routes and permalink behavior, select the theme and templates, configure membership or newsletter services if in scope, and approve the staging publication before loading.
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 WordPress and connect a prepared staging Ghost destination.
Review detected records, available entities, media, URLs, and anything that needs a decision.
Choose where supported WordPress data belongs in the prepared Ghost 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 WordPress source capability and stable Ghost target capability. Both platforms are public-ready in both directions, but their entity models are not equivalent.
The current source exposes Authors, Categories, Tags, Posts and pages, Comments, Menus, Menu items, Media. Custom types and plugin-owned fields remain project-specific even when the base content entity is available.
The current target exposes Attachment, Author, Content, Member, Newsletter, Offer, Tag, Tier. Posts, pages, tags, media, and metadata have a direct path; staff authors must already exist, while membership entities require separate source data and business rules.
Standard means the current adapters provide a direct structured path. Review means identity, source markup, or destination configuration must be approved. Custom means Ghost has no standard equivalent or the source data belongs to a plugin.
| WordPress source | Ghost target | Status and boundary |
|---|---|---|
| Posts | Ghost posts | Standard: title, HTML body, excerpt, slug, publication state, dates, tags, feature image, and supported metadata are mapped. |
| Pages | Ghost pages | Standard with review: the target adapter writes pages separately, but WordPress templates and page-builder layout are not portable content. |
| Categories and tags | Ghost tags and primary tag | Review: WordPress taxonomies are flattened or consolidated into the approved Ghost tag model. |
| Authors | Existing Ghost staff users | Review: authorship can resolve to approved Ghost IDs, but the current target adapter does not create staff users or migrate passwords. |
| Featured and inline media | Ghost image and file uploads | Standard with validation: assets must remain downloadable, upload successfully, and be rewritten in the final HTML. |
| SEO titles and descriptions | Ghost meta title and meta description | Standard when exposed: recognized source metadata is written through the current target payload and then validated in rendered pages. |
| Comments and menus | Theme, integration, archive, or custom records | Custom/excluded: the current Ghost target does not provide equivalent comment or navigation entities. |
| Users, members, newsletters, and paid access | Ghost members, newsletters, tiers, and offers | Custom/restricted: author records do not prove subscription, consent, price, access, or payment state. |
| Blocks, shortcodes, embeds, and builder data | Ghost HTML, cards, theme code, or custom transformation | Review/custom: unsupported markup must be converted, replaced, rebuilt, or documented as an exception. |
| Themes, plugins, forms, search, and commerce | Ghost theme, integrations, Portal, or external services | Rebuild: application behavior does not transfer as content records. |
The mapping workbook distinguishes portable editorial data from WordPress presentation and plugin behavior before the first Ghost staging run.
| WordPress value | Migration rule | Ghost result |
|---|---|---|
| Post type and source ID | Route post or page and preserve source identity for reruns | Ghost post or page plus migration ID map |
| Title, body, excerpt, date, status | Clean HTML and translate editorial state | Title, HTML, custom excerpt, publication date, and approved status |
| Category and tag terms | Consolidate, normalize, create tags first, and resolve relationships | Ghost tags and approved primary-tag rule |
| Author ID | Match the approved pre-created Ghost staff user | Ghost authorship without password migration |
| Featured image and body assets | Download, validate, upload, and rewrite references | Ghost feature image, images, files, and updated HTML |
| SEO metadata and old URL | Map supported fields and add the path to the redirect contract | Ghost metadata plus tested redirects.yaml rule |
WordPress stores portable editorial content beside shortcodes, blocks, builder structures, plugin fields, and template assumptions that Ghost cannot interpret automatically.
List posts, pages, custom types, statuses, taxonomies, fields, plugins, shortcodes, blocks, embeds, media, and representative complex records.
Define which markup becomes clean HTML, Ghost-compatible content, a replacement embed, a manual task, an archive, or excluded functionality.
Create and approve Ghost staff users before migration, then map WordPress author IDs without attempting to transfer passwords or roles.
Inspect tables, code, galleries, captions, embeds, lists, links, images, downloads, excerpts, metadata, and mobile rendering in Ghost staging.
Ghost can manage members, newsletters, tiers, and offers, but ordinary WordPress users and authors do not contain the subscription context needed to create them safely.
Determine whether subscribers, consent, lists, plans, prices, and access live in WordPress, a membership plugin, WooCommerce, an email platform, or a payment provider.
Transfer only approved member fields and labels through a secure path with documented purpose, destination ownership, retention, and deletion.
Stripe customers, subscriptions, products, prices, discounts, tax, failed payments, and entitlements require a dedicated operational migration plan.
Validate newsletter assignment, email consent, complimentary access, paid access, portal behavior, sender settings, suppression, and unsubscribe journeys when included.
WordPress permalinks and Ghost routes differ. The final route design and redirect contract must be approved before content is loaded.
Combine the WordPress crawl, sitemaps, analytics landing pages, backlinks, feeds, media URLs, campaign paths, and known legacy redirects.
Map each valuable source URL to a relevant Ghost destination and test exact rules, regex rules, status codes, loops, chains, query behavior, and trailing slashes.
Validate titles, descriptions, canonicals, social fields, headings, body links, image references, sitemap entries, feeds, and important templates.
Reconcile records and assets, smoke-test subscriptions and forms if included, monitor errors and analytics, and keep rollback decisions explicit.
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
Review the publication archive, reader access and final handover.
Open guide →Review WordPress source extraction, plugin-owned data, media, users, URLs, and destination planning.
Open guide →Review the reverse direction and the boundaries around Ghost members, newsletters, tiers, and offers.
Open guide →Compare a schema-first headless CMS destination with configurable content-type APIs.
Open guide →Clear answers
Yes. The current adapters expose WordPress content and create Ghost posts or pages separately. Source markup, custom types, private states, and page-builder content still require review.
Authorship can be mapped to approved Ghost staff users, but the current Ghost target adapter does not create staff accounts. Users must be prepared in Ghost and passwords are not migrated.
Ghost uses tags rather than a separate WordPress-style category model. Categories and tags are consolidated according to an approved taxonomy and primary-tag rule.
Not as standard Ghost entities through the current target adapter. They can be archived, remodeled, implemented through another service, or scoped as custom work.
Only after the real subscription source, consent, labels, paid status, destination newsletter, tiers, and access rules are reviewed. WordPress author or user records alone are insufficient.
Not automatically. Each shortcode, block, embed, and builder pattern is converted, replaced, rebuilt, archived, or documented as an accepted exception.
Rankings cannot be guaranteed. Reduce migration risk with URL inventory, Ghost route planning, redirects, metadata transfer, link updates, sitemap checks, analytics, and post-launch monitoring.
Next step
Create an account, connect the systems, and analyze the supported scope before purchasing the full migration.
