How to Migrate from WordPress to Ghost

WordPress powers a huge share of the web, but its plugin-heavy stack can feel bloated for a business whose real goal is publishing content, running a newsletter, and loading fast. Ghost takes the opposite approach: a lean, publication-focused CMS with built-in membership, email newsletters, and SEO baked in, without the constant plugin updates and security patches. That is why more publishers, SaaS blogs, and creator businesses are moving off WordPress.

But a CMS migration is never just an export and an import. Your URLs, your on-page SEO, your theme, your forms, and every plugin-driven feature have to be re-created or replaced on the new platform, and search engines have to be told exactly where everything moved. Done carelessly, a WordPress-to-Ghost move can wipe out years of accumulated rankings overnight.

This guide walks through the full process the way we run it at eSEOspace: what changes, what breaks, the exact migration steps, and how to keep your organic traffic intact with a proper 301 redirect map. If you would rather hand the whole thing off, our website migration services cover it end to end.

Why businesses move from WordPress to Ghost

The motivation almost always comes down to speed, simplicity, and owning your audience. Ghost is a purpose-built publishing platform, so the things that require three or four plugins on WordPress ship as native features.

• Native newsletters and memberships: Ghost has built-in email newsletters (via Mailgun) and paid subscriptions with Stripe, replacing plugins like Mailchimp for WP, MemberPress, or Substack-style workarounds.
• Performance out of the box: Ghost runs on Node.js and serves lightweight pages without the plugin bloat, page builders, and heavy themes that slow many WordPress sites. Better Core Web Vitals often follow.
• Lower maintenance and better security: No sprawling plugin ecosystem means fewer update cycles and a much smaller attack surface. Ghost(Pro) hosting handles updates and backups for you.
• Clean, modern editing: The Ghost editor with cards and Markdown is faster for writers than the Gutenberg block editor for most content teams.

Ghost is a deliberately focused tool. If your site depends heavily on WooCommerce, complex membership tiers, LMS functionality, or hundreds of custom fields, weigh that carefully before committing, because those are exactly the areas where WordPress still wins.

What changes and what breaks

Understanding the gaps before you start is what separates a clean migration from a painful one. Here is what typically needs attention when moving from WordPress to Ghost.

• Content: Posts, pages, images, tags, and authors migrate well through the official importer. Custom post types, custom fields (ACF), and shortcodes do not have a direct equivalent and must be rebuilt as Ghost cards, pages, or code injection.
• URLs: Ghost defaults to a flat /post-slug/ structure and uses /tag/ and /author/ archives. WordPress permalinks with /category/, dates, or /blog/ prefixes will change, which is the single biggest SEO risk.
• Plugins and apps: There is no plugin marketplace. Contact forms, SEO plugins (Yoast/RankMath), redirects, and analytics are replaced by native Ghost features, integrations, code injection, or third-party tools like a forms service.
• Design: WordPress themes and page builders (Elementor, Divi) do not transfer. You choose or build a Ghost theme using its Handlebars templating, so custom layouts need to be rebuilt.
• SEO metadata: Ghost has native meta titles, descriptions, canonical URLs, and Open Graph fields, but they are stored differently, so Yoast/RankMath data has to be mapped over during import.

Step 1: Audit and export your WordPress content

Before touching anything, crawl the existing site and inventory every URL, its title, meta description, and current traffic. This inventory becomes your redirect map and your QA checklist later, so do not skip it. Our website migration SEO checklist lays out exactly what to capture.

• Install the free Ghost WordPress migration plugin on your WordPress site and use it to generate a Ghost-compatible export ZIP that includes posts, images, tags, and authors.
• Also run the standard Tools → Export in WordPress to keep a native XML backup as a fallback.
• Export your images and uploads folder separately so nothing is lost if the automated image transfer misses files.
• Document your top-performing pages by organic traffic and backlinks so you prioritize preserving those URLs and their metadata.

Step 2: Set up Ghost and rebuild the design

Decide where Ghost will live. Ghost(Pro) is the managed hosting from the Ghost team and is the simplest option; self-hosting on a VPS (DigitalOcean, for example) is cheaper but you own updates, SSL, and backups. Set up a staging install first so you never test on the live domain.

• Choose a theme from the Ghost marketplace or commission a custom one that matches your current brand. Ghost themes use Handlebars, so replicating a bespoke WordPress design is a development task, not a settings toggle.
• Configure core settings: site title, timezone, meta defaults, social accounts, and the publication URL.
• Connect Mailgun if you plan to send newsletters, and Stripe if you will run paid memberships.
• Recreate navigation menus, footer, and any global elements that were controlled by your WordPress theme or a page builder.

Step 3: Import content and recreate what does not transfer

With staging ready, import the Ghost ZIP under Settings → Import content. Then do the manual work the importer cannot.

• Spot-check a sample of posts for broken formatting, missing images, and mangled embeds. Shortcode-driven elements (galleries, buttons, CTAs) usually break and need rebuilding as Ghost cards or HTML cards.
• Re-enter or verify meta titles and descriptions that lived in Yoast/RankMath, because these do not always carry over cleanly.
• Rebuild contact forms with a Ghost-compatible form tool or embed, since WordPress form plugins do not migrate. For anything involving lead capture into a CRM, plan a proper CRM integration rather than a fragile workaround.
• Re-add structured data, custom scripts, and analytics tags through Ghost's code injection (site-wide header/footer) or per-post injection.

Step 4: Map and implement 301 redirects

This is the step that makes or breaks your SEO. Because Ghost's URL structure differs from most WordPress permalinks, nearly every URL may change, and every changed URL needs a 301 (permanent) redirect from the old path to the new one. A 301 passes the vast majority of link equity, so search engines transfer your rankings to the new URLs instead of dropping them.

• Build a one-to-one redirect map from your Step 1 URL inventory: old WordPress URL → new Ghost URL. Never bulk-redirect everything to the homepage, which Google treats as a soft 404 and which loses the ranking.
• Ghost handles redirects with a redirects.yaml (or JSON) file uploaded under Settings → Advanced. Format each entry with the source pattern and destination.
• Preserve or redirect your category and tag archive URLs, RSS feed, and any deep-linked landing pages.
• Follow a disciplined process; our guide on building a 301 redirect map for a website migration covers the mapping logic in detail.

Step 5: Test, launch, and monitor

Do a full QA pass on staging before you flip DNS, then keep watching after launch, because migration issues often surface days later in the index.

• Pre-launch: click through top pages, test forms and newsletter signup, validate that every redirect in the map resolves, and confirm meta tags, canonical URLs, and Open Graph images render correctly.
• Launch: point your DNS to the Ghost host, confirm SSL is active, and remove any staging noindex so the live site can be crawled.
• Post-launch: submit a fresh XML sitemap in Google Search Console, monitor the Coverage and Redirects reports, and watch for spikes in 404s or crawl errors.
• Track organic traffic and rankings for two to four weeks. A small temporary dip is normal; a sustained drop signals a redirect or indexing problem to fix immediately.

Realistic timeline and cost

A straightforward blog with a few hundred posts and a stock Ghost theme can move in roughly one to three weeks. A larger site with thousands of posts, a custom-built theme, membership tiers, and a complex redirect map typically runs four to eight weeks, most of that spent on design rebuild, redirect mapping, and QA rather than the import itself.

• Hosting: Ghost(Pro) starts around $9-$25/month for small sites and scales with member count; self-hosting on a VPS runs a few dollars a month plus your maintenance time.
• Theme: free or marketplace themes cost $0-$150; a custom-designed Ghost theme is a development project.
• Professional migration: at eSEOspace's $80/hr, a small guided migration is a modest fixed engagement, while custom design plus a large redirect map scales with scope.

The cheapest version is doing the import yourself and living with a stock theme; the risk is doing the redirect mapping poorly and losing rankings that take months to recover. If organic traffic is a meaningful part of your business, the redirect and SEO-preservation work is where professional help pays for itself.