Migrate from the Obsidian Ghost plugin to Specter

If you publish from Obsidian using the Ghost Publish (or “Send to Ghost”) plugin, you already have a working pipeline. This guide is for the moment that pipeline starts to pinch — when you want to edit posts you’ve already published, sync changes both directions, or run AI across your whole archive. That’s where an Obsidian Ghost Publish alternative like Specter comes in, and the move is almost frictionless because there’s nothing to install — you connect Ghost in the browser. Subscribe now and your workspace opens with 500 free credits.

What the plugin does well

Credit where it’s due: the Obsidian plugins are free, cross-platform, and dead simple. You write a note in your vault, hit publish, and it lands in Ghost. If you only ever draft new posts inside Obsidian and never touch them again outside the Ghost editor, the plugin is genuinely a good fit. There’s no reason to change for change’s sake.

When it’s time to switch

The plugins are one-way — they push a note from Obsidian to Ghost and stop there. Consider an Obsidian Ghost plugin migration when:

You want two-way sync. Edits in Ghost should flow back to you, not just the other direction.
You need to edit already-published posts. The plugin can’t pull your existing Ghost archive in. Specter brings every post into one workspace as clean, editable content.
You want to run AI across the whole archive. Specter runs AI recipes over your entire blog at once — refresh stale posts, generate missing meta descriptions, enforce a style guide — and shows every change as a diff before it ships.
You want conflict safety. If a post changed in both the Ghost editor and your workspace, Specter prompts you instead of silently overwriting, with a review diff and a snapshot behind every publish.

Step-by-step migration

You don’t have to dismantle anything. Here’s the path.

Open your workspace. Subscribe now; when your workspace opens it starts with 500 free credits. There’s nothing to download.
Connect Specter to Ghost. Follow connect Specter to your Ghost blog: paste your site URL and your Ghost Admin API key, then test the connection. This is the same kind of credential the Obsidian plugin uses, so nothing new to learn.
Run a first pull. On the first sync, Specter pulls your existing Ghost posts into your workspace as clean content with their metadata — including everything you published through the plugin. This is the piece the plugin never gave you: your live archive, now editable. Browsing it is free.
Edit and sync both ways. From here, change a post in Ghost or in your workspace, and Specter reconciles the two — run a recipe across the whole archive, review the diff, and publish back. Only AI runs spend credits.

Nothing gets lost

This is the part people worry about, so let’s be clear: there’s no export-import dance. Specter connects directly to your Ghost site and brings your posts in as they are — titles, slugs, tags, and content the same fields they always were. Because Ghost stores posts in its Lexical format, what you edit is a faithful projection of each post, not a lossy export (how Specter handles Ghost cards covers exactly what survives). No proprietary lock-in on either side.

The practical difference is what you can do once your whole blog is in one workspace: run AI across the entire archive, batch-edit metadata, enforce a style guide, then review and publish it all back. The plugin gave you a publish button. Specter gives you the whole library, both directions, with a diff in front of every change.

If you want the detailed feature-by-feature breakdown before you commit, read the full Specter vs Obsidian Ghost Publish comparison.

Still want your posts inside your Obsidian vault as plain .md files on disk? That’s exactly what the desktop and open-source edition does — point its sync folder at your vault and the two coexist, running entirely on your Mac.