Leaving Substack is a migration decision, not just a feature comparison. Your subscriber records, public archive, paid access, billing setup, and existing links may not move in the same way. Identify what must continue working, then compare each destination against that list.
Quick verdict
- Choose beehiiv if you want its dedicated Substack import flow and can plan separately for free subscribers, posts, and paid subscriptions.
- Choose Kit if creator email workflows are the priority. Paid subscriber records can be imported, but Kit says active paid subscriptions and their payment details do not have a convenient direct migration method, so readers may need to subscribe again.
- Choose Ghost if you want to move publication content and members into a Ghost publication and are prepared to set up Stripe and review existing Substack fees.
- Stay on Substack if the current setup meets your needs and migration work, reader disruption, or paid-billing risk outweighs a specific benefit you can name.
For a paid publication, verify your subscription types, payment setup, archive URLs, and cutover plan with the destination platform before announcing a move.
Explore beehiiv’s official Substack migration guide if its workflow is on your shortlist.
Review beehiiv’s current migration options: beehiiv
Compare migration paths, not generic feature lists
| Migration factor | beehiiv | Kit | Ghost | Stay on Substack |
|---|---|---|---|---|
| Content migration | Its guide describes importing free posts from a Substack publication URL. For paid posts, it uses a Substack export file and the Content Import flow; imported paywall placement and copy need review. | Its guide describes recreating prior newsletters as Broadcasts, publishing them to the web, and setting their original dates. This is not the same URL-based import described by beehiiv. | Ghost Admin has a Substack migrator that imports publication content from a Substack export. | No platform migration is required. Keep the current archive and review whether its limits are the reason to move. |
| Free subscribers | Export a Substack subscriber CSV, upload it, map fields, and review import results. | Export a CSV from Substack and import it into Kit. The guide also describes separate handling for paid subscribers. | The migrator provides a free-subscriber export and import step. | Subscriber records remain in the current system; confirm your own export and backup process. |
| Paid subscribers | The official flow includes Stripe customer transfer, matching paid tiers, and recreating subscriptions. Comped, gifted, and iOS subscriptions have separate handling. | Kit documents importing a separate CSV of paid subscriber records, which can be tagged. It says active paid subscriptions and their payment details have no convenient direct migration method; its workaround is to cancel the Substack subscriptions and ask readers to subscribe again. | The migrator has a paid-subscriber step. Ghost says to set up Stripe using the same Stripe account connected to Substack. | A move is unnecessary if current paid access and billing meet your needs. Reconsider if a specific limitation justifies the transition. |
| Billing and Stripe | Set up the destination Stripe account and paid tiers before importing paywalled content or mapping paid subscribers. After a paid cutover, its guide says to pause or cancel Substack subscriptions to prevent double billing. | Create a new paid newsletter product and arrange a reader re-subscription; notify paid readers in advance and plan for questions or refund requests. | Ghost’s guide states that Substack continues taking its 10% fee on existing paid subscriptions after migration; it directs publishers to contact Ghost for help getting those fees removed. | No migration cutover. Review current billing and any planned changes directly in your account before deciding. |
| Migration work | Several documented import flows and field/tier mapping steps; paid migration includes an additional Stripe process. | Rebuild the public profile and past web archive, import subscriber CSVs, then rebuild the paid product and coordinate re-subscription. | Use the Admin migrator, export/import content and member files, then review Stripe and URL requirements. | Lowest immediate migration workload; the tradeoff is keeping the current setup and its known constraints. |
| Who should shortlist it | Operators who value a dedicated Substack import workflow and can validate its separate free, content, and paid steps. | Creators who prioritize Kit’s email workflows and accept a more involved paid-subscriber transition. | Publishers who want Ghost’s publication migrator and can manage Stripe and domain/redirect details. | Publishers without a clear migration benefit or whose reader and billing disruption would be disproportionate. |
| Main tradeoff | Imported content and paywalls require review; paid subscriptions are a distinct operational cutover. | Paid subscriber records can be imported, but paid readers may need to re-subscribe; past web newsletters are recreated as Broadcasts. | Substack’s documented fee applies to existing paid subscriptions; custom-domain redirects need planning. | Staying avoids cutover work but does not resolve the reason you considered leaving. |
These rows describe documented migration paths, not a guarantee that every account, post, subscriber, or subscription is eligible. Ask each provider to confirm edge cases for your account before you commit.
What to verify before choosing
- Export your records. Substack provides a subscriber-list CSV export and a Posts export. Download and securely retain the files before you begin.
- Separate subscriber groups. Record free, paid, comped, gifted, trial, and app-store subscribers separately where they apply. Reconcile counts and identify which groups use Stripe.
- Inventory paid tiers and billing. Record current tier names, legacy prices, renewal dates, entitlements, failed-payment handling, refund obligations, and who controls the connected Stripe account.
- Map content and URLs. List high-value posts, paywall positions, images, links, custom-domain settings, and pages that receive search traffic or backlinks. Confirm how each destination handles them.
- Check field mapping and consent. Ask how status, tags, signup source, unsubscribe/suppression data, and other fields map. Import only contacts you are permitted to email, and inspect rejected or unmatched records.
- Rebuild a representative sample. Test a free post, a paywalled post if relevant, signup, welcome sequence, archive page, and key subscriber segments. Confirm rendering and links by hand.
- Plan domain and redirects. If URLs or domains change, prepare a URL map and verify redirect behavior before the old route is retired. Do not assume old links will resolve automatically.
- Agree on the paid cutover. Document when subscriptions are created, paused, or cancelled; who communicates with readers; how double charges and access gaps are prevented; and what happens if the import fails.
- Keep rollback records. Retain exports, settings, URL maps, and a dated subscriber/tier reconciliation until the new setup is stable.
If your move also changes the publication’s paid business model, compare paid newsletter platforms before migrating separately from the migration mechanics.
Choose beehiiv when its import path fits your publication
beehiiv documents a Substack-specific flow for free posts using the publication URL, plus a separate export/import process for free and paid content. Free subscribers are imported from CSV with field mapping. Paid migration is more involved: paid tiers need to be prepared, Stripe customer data is transferred between Stripe accounts, subscriptions are recreated, and the publisher must coordinate the Substack billing pause or cancellation to avoid charging readers twice.
That makes beehiiv a candidate when its documented import workflow matches your content and audience. Before moving, inspect imported paywall placement, default paywall copy, legacy tiers, comped or app-store subscribers, and the effect on important post URLs. The official guide notes that exact paywall placement is not carried over automatically.
Do not infer a no-work cutover from the presence of an import tool. Confirm your subscription products and payment transfer details with beehiiv and Stripe, then reconcile the migration preview before starting the paid import.
Choose Kit when creator email workflows outweigh paid billing continuity
Kit’s Substack migration guide describes recreating the profile as a Kit Newsletter Site, recreating past newsletters as Broadcasts that are published to the web, and importing subscriber CSVs. It describes importing paid subscribers with a tag, then creating a new paid newsletter product.
Separate the subscriber list from the payment relationship. Kit documents importing the paid-subscriber CSV and tagging those records. It says there is no convenient way to migrate active paid subscriptions with payment details; its workaround is to cancel Substack subscriptions and ask those readers to subscribe again to the new Kit paid newsletter. If your paid audience is central to the business, plan reader communications, timing, access, and possible refund questions before choosing this route. Ask Kit’s migrations team about your specific case if the documented process does not fit.
Kit is a stronger shortlist option when its creator email workflows are the reason for moving and your plan can absorb the extra steps for paid readers. Do not assume its content process is equivalent to a one-click archive import: the documented path recreates posts as web-published Broadcasts.
Choose Ghost when publication ownership and its migrator fit
Ghost’s Substack migrator runs from Ghost Admin and imports content and members from a Substack export. Its guide has separate steps for free and paid subscriber files. For paid memberships, Ghost says to set up Stripe first and use the same Stripe account connected to Substack.
Check the fee detail before you decide: Ghost’s migration documentation states that Substack continues to take its 10% fee on existing paid subscriptions after migration and directs publishers to contact Ghost for help getting those fees removed. This statement is scoped to existing subscriptions as described in the guide; it does not establish that new subscriptions carry this Substack fee. Confirm how the documentation applies to your account directly with Ghost.
If you use a custom domain, Ghost also documents redirects for Substack post URLs. Its guide explains that Substack and Ghost use different URL patterns, so test important old links and preview routes before cutover. Ghost can suit a publisher prioritizing its publication site and a built-in migration path, provided the billing and URL work is acceptable.
Stay on Substack when the move does not solve a material problem
Staying is a valid decision. If your publication, audience, and paid operations are working and you cannot identify a concrete outcome that a move would improve, postponing migration avoids immediate reader, billing, and archive disruption. Revisit the decision when a specific constraint becomes costly enough to justify the work.
Even if you stay, keep a current export and know where to find your subscriber and post data. Substack documents subscriber-list CSV exports and a Posts export flow under publication settings. A tested backup plan gives you options without forcing an unnecessary platform change.
Migration risks that need account-specific checks
- Subscriber data: CSV columns and statuses may need mapping. Compare source and destination counts, unsubscribes, suppression records, and consent basis before sending.
- Paid access: Free, Stripe-paid, comped, gifted, and app-store subscribers can follow different paths. Confirm who retains access and when before changing billing.
- Billing continuity: Establish the sequence for creating destination subscriptions and pausing or cancelling old ones. Avoid a period of double billing or accidental access loss.
- Content and formatting: Imported or recreated posts may not preserve paywall placement, styling, images, embedded media, or links exactly. Review a representative sample.
- Search and links: Verify canonical URLs, redirects, metadata, and high-value archive paths. Do not assume a destination recreates Substack URLs.
- Sending and deliverability: Confirm domain authentication, sender identity, suppression handling, and a gradual first-send plan with the provider. Results depend on your list and sending practices.
- Analytics history: Preserve available exports and campaign records; verify which historic metrics can actually be imported rather than assuming they will appear in the destination.
Make the final decision
- Free newsletter, growth-focused, wants a dedicated import flow: evaluate beehiiv’s content and subscriber steps, then separately validate any paid requirements.
- Creator-led publication centered on email workflows: evaluate Kit, accounting for manual archive recreation and paid-reader re-subscription.
- Publication-site control with a built-in content/member migrator: evaluate Ghost, including Stripe setup, existing-subscription fee treatment, and URL redirects.
- Already satisfied and no urgent constraint: stay on Substack, keep exports current, and revisit when expected benefit outweighs switching cost.
Before a paid move, ask your chosen provider to validate your plan against your actual subscriber groups, content, and payment setup.
There is no universal winner here. Choose the destination whose documented migration path fits your audience and operating constraints, or stay put when the expected gain does not justify the disruption.