Gemin
Start a project

Ghost to Webflow

Migrate from Ghost to Webflow

Ghost is a strong publishing tool and a limited website platform. Teams usually move when the company has outgrown the blog: more pages, more campaigns, more design needs and more people editing the site.

Start a project

A migration like this usually takes 2–3 weeks

Why people move

What changes when you move from Ghost to Webflow.

What is being compared Ghost Webflow
What it is for Ghost Publishing, and it is very good at it Webflow A site that also publishes If all you do is publish, Ghost is a reasonable place to stay.
Editor Ghost Excellent for writing Webflow Good for content, not a writing tool
Memberships and paid posts Ghost Built in Webflow A separate service Ghost wins this clearly.
Design control Ghost Handlebars themes Webflow Layout built directly
Marketing pages Ghost Publishing-first templates, and pages within them Webflow Pages built from a reusable design system
Export quality Ghost Clean JSON, genuinely portable Webflow Not applicable One of the easiest sources to move.

Once you have decided

What actually migrates.

What you have What happens Why
Posts Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Ghost's JSON export is clean and complete. This is the good case.
Pages Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Same export, same mapping.
Tags and authors Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Map to collections or fields.
Images Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. The ordinary content export is JSON and does not bundle the media library. On Ghost Pro a full archive including the files can be requested, and it has to be requested while the account is still open, which makes it the first thing on the audit rather than a detail near the end.
Members and subscriptions Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. The records export as CSV, down to the Stripe customer ids. What does not export is the system around them: sign-in, paid access, the subscription itself and the sending. Those stay in Ghost or move to a service chosen for them, and that is a decision rather than a transfer.
URLs and redirects Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. Ghost's slugs usually carry, which makes the map shorter than most.

Before you budget it

Where this migration gets complicated.

  1. 01

    Paid access has to be preserved across the cutover

    Member records come out as CSV. What does not come out is the thing enforcing them: the subscription state, the payment relationship and the gate on the content. Whatever replaces Ghost has to be live and populated before the old one goes, or somebody who paid cannot read what they paid for. That makes the order of the cutover a constraint rather than a preference.

  2. 02

    The writing experience is a real part of the trade

    Ghost's editor is built for long-form and Webflow's is not aimed at it. Whether that matters depends on who writes and how often, and it is worth weighing before the move rather than after, because for some publications it is the argument against moving at all.

How it runs

How the migration works.

  1. 01

    Plan

    The content export, the members file, the existing redirects and route configuration, the assets, and which publishing features need a destination.

  2. 02

    Build

    Templates built in the Designer, against the model rather than against the old pages.

  3. 03

    Migrate

    Content in, assets rehosted and checked against the source, and every address that changes given a rule pointing straight at its replacement.

  4. 04

    Launch

    Forms at the record, every template at three widths and every old address requested, all before anything is switched. Then typically 2–3 weeks from start to live, and a week of watching what the old addresses return.

What you are buying

What is included.

  • Design rebuild

    Rebuilt directly against the existing site.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • Redirects

    Changed URLs mapped directly to replacements.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.