A newsletter list is not the whole publication
Substack combines publishing with its reader app and network. Ghost gives you a publication website, email newsletters and membership features, with managed Ghost(Pro) hosting or a self-hosted option. The choice is as much about how readers find you and what site you want to own as it is about composing email.
If recommendations and participation inside Substack bring you meaningful readers, leaving can cost more than the visible fee saving. If your domain, site structure and independent brand are central assets, Ghost deserves a close look.
Cost at 10,000 readers depends on how many pay
Substack takes 10% of paid subscription transactions, with payment-processing fees in addition. Free publishing does not create that platform revenue fee. Ghost does not take a platform percentage of membership revenue, but hosting and payment processing still cost money. A Ghost(Pro) plan supporting paid subscriptions and 10,000 members must be priced with the current member selector; the displayed 1,000-member entry price is not that quote.
| 10,000-reader publication | Monthly paid revenue | Substack platform share, excluding payment fees |
|---|---|---|
| Everyone reads free | $0 | $0 |
| 100 readers pay $10/month | $1,000 | $100 |
| 500 readers pay $10/month | $5,000 | $500 |
| 1,000 readers pay $10/month | $10,000 | $1,000 |
For Ghost, compare the full hosting quote with those amounts. A rough break-even is hosting cost divided by 10% when other costs are comparable. It is a fee comparison, not a growth forecast: changing platforms can change acquisition and conversion.
What ownership changes in practice
Ghost is a good fit if you need a website with controlled navigation, themes and a searchable archive on your own domain. Substack reduces publishing setup and places the work inside an existing reading environment. Neither choice removes the need to build an audience or maintain reader trust.
Think beyond a subscriber CSV. Your publication includes article URLs, images, paid access rules, recurring subscriptions and reader expectations. Review which elements export and which require a separate migration step. A list export alone does not transfer the whole business.
A paid-publication migration rehearsal
Start with a content sample: an old free article, an old paid article and a post with embedded media. Check image URLs, publication dates, canonical URLs and what a logged-out visitor can see. Prepare redirects for old links you control rather than assuming the archive will retain every URL.
Then map free, paid, complimentary and cancelled subscribers separately. Confirm payment-provider migration requirements with the destination before changing billing. Do not accidentally create a second subscription for an existing payer. Send a clear transition notice through your existing permission-based channel when you actually schedule the move.
Finally, test a new signup, a paid checkout, a renewal and an unsubscribe. Keep the original exports until reconciliation is complete.
Decide what the publication should own
Owning a publication involves more than exporting email addresses. Consider the website, archive, domain, member records, payment relationships and links readers have already saved. Ghost is a candidate when operating a publication on your own site is a priority. Substack is a candidate when publishing and participating in its reader ecosystem fit the business. Compare the daily work and the assets you expect to control, rather than using ownership as an undefined slogan.
Write down the requirements that would make a future move difficult: custom article URLs, multiple authors, paid archives, existing subscription renewals and the way readers sign in. A list export is only one part of portability. Before choosing either platform, identify which of those assets you can export directly, which require transformation and which depend on a platform-specific reader experience that cannot simply be copied elsewhere.
Model paid revenue separately from reader count
A publication with 10,000 free readers and no paid subscribers has a different economic comparison from one with 1,000 paying members. Build a revenue model using the paid count, subscription price, billing interval and realistic churn. Apply Substack's current platform percentage to paid revenue, and compare Ghost's applicable plan or self-hosting costs plus payment processing. Do not apply a revenue fee to the entire free audience.
For illustration, 500 people paying $10 each month generate $5,000 in gross monthly subscription revenue before refunds, tax handling or payment fees. A 10% platform share would represent $500 of that gross revenue. This is arithmetic, not a guarantee about your final invoice. Confirm the current contractual rates, processing arrangements and Ghost plan limits for your total membership before treating the difference as money you will save.
Compare discovery with a distribution plan
Substack's network can be part of a publication's acquisition strategy, but a recommendation feature is not a promise of new subscribers. Review where your current readers actually come from: search, social referrals, recommendations, partnerships or direct word of mouth. If you move to Ghost, decide which channels you will operate and how the website supports them. If you stay on Substack, measure the value of the platform's discovery contribution rather than assuming it is either essential or irrelevant.
Use a consistent definition of an acquired reader and a paid conversion. A platform may expose engagement within its own reader experience that does not map directly to a website analytics event. Document the differences before comparing conversion reports. Otherwise, a move can make a familiar number disappear or change meaning without necessarily reducing the publication's real audience or revenue.
Rehearse the editor's complete week
Draft an article, add images, preview it on a phone and send a test email. Include a correction after publication and a follow-up to paid members. Ask every regular contributor to perform their part. The right system should fit the people creating and maintaining the publication, including the person covering when the main author is away. A more flexible site is not useful if routine publishing becomes a bottleneck.
For Ghost, distinguish a managed Ghost(Pro) service from operating the software yourself. Self-hosting changes who handles updates, backups and email delivery configuration; it is not simply a cheaper edition of the same operational arrangement. For Substack, assess whether its publication and reader interactions fit the intended format. A long-form editorial publication, a community-driven newsletter and a brand content site can reasonably choose different workflows.
Treat existing subscriptions as a separate migration
Before importing paid members, establish how their current subscriptions will continue. Confirm which payment accounts and subscription identifiers are involved, how access is granted and who handles renewals, cancellations and refunds during the move. Do not assume importing a paid label recreates an active billing relationship. Keep the old and new membership counts reconciled with the payment source of truth.
Test a small representative set: a free reader, a monthly payer, an annual payer and someone who has cancelled but retains access until the end of the term. Verify their login and content access in the new system. Do not ask every existing subscriber to pay again merely to simplify migration. If the supported path requires an action from readers, communicate exactly what changes and why before the cutover.
Preserve the archive and reader expectations
Export the publication content and map the important URLs. Check image availability, embedded media, internal links and any paid-content boundaries after import. Where you control the old domain, plan redirects to the corresponding article rather than sending every historical link to the homepage. Where you do not control redirects, recognize that limitation in the migration plan instead of promising seamless SEO continuity.
Tell readers where future issues will arrive from and how to manage their subscription. A new sending domain, changed login flow and unfamiliar sender name can make a legitimate move look suspicious. Keep the first message clear and useful, and avoid combining the move with a dramatic increase in frequency. Preserve unsubscribes and do not treat an old export as a reason to reactivate readers who opted out later.
Make the choice using the publication's next year
Choose Substack when its publishing workflow and reader ecosystem are central to the product you want to build, and its economics make sense at your expected paid revenue. Choose Ghost when control of the site, membership experience and publication infrastructure justify the plan and operating responsibilities. Neither is automatically the best tool for product onboarding, ecommerce promotions or unrelated application notifications.
Before moving a working publication, calculate the implementation effort and the time required from editors and support. A platform-fee saving can be meaningful, especially as paid revenue grows, but only if the move preserves paying readers and the publication continues to ship. Start with a rehearsal using copies of content and test members, then schedule the real migration around an ordinary publishing cycle with a clear recovery plan.
Write down the publication exit plan early
Before committing to either platform, keep a short inventory of the assets a future move would require: articles, images, member identities, subscription records, domain settings and important public URLs. Confirm the current export and import paths for each. Store the inventory where the publication team can find it, and update it when the membership or website setup changes.
This is valuable even if you never migrate. It clarifies what the business controls and which parts depend on the current publishing service. For a Substack-led publication, that includes reader experiences inside its ecosystem. For a Ghost-led publication, it includes the operating arrangement for the site and email delivery, especially if self-hosted. A deliberate choice can accept platform dependencies or hosting responsibilities. The problem is discovering them only after a decision has already been made and a paying audience is waiting for its next issue.
Recommendation
Choose Substack for its publishing environment and network when those create value. Choose Ghost for an independent membership publication when you can own the migration and site. Sequenzy fits lifecycle campaigns for a software business; it does not replace either publication's reader network or membership website.
Sources and scope
Updated November 3, 2026. We publish Sequenzy and have a commercial interest in this comparison. This is a documentation-based evaluation, not a hands-on benchmark or independent ranking. Prices are USD list prices or explicitly labeled calculations; taxes, promotions and optional services can change the total. Confirm the selected plan before purchase.

