Substack makes starting a newsletter almost frictionless, which is exactly why so many writers outgrow it. Once you want a properly branded landing page, automated onboarding, or segmentation based on what someone actually did rather than just whether they subscribed, Substack's simplicity starts to feel like a ceiling. Kit was built for creators who want that control — your own domain, your own design, and an automation builder that goes well beyond Substack's linear subscribe-and-receive model.
The move is as much a mindset shift as a technical one. On Substack, the platform handles onboarding by default — a new subscriber just starts receiving posts. On Kit, you decide what a new subscriber sees first, in what order, and how they get tagged along the way. That's a genuine upgrade for anyone monetising beyond straight subscriptions, but it means building an onboarding sequence you never had to think about before.
This guide walks through exporting your Substack list, handling paid subscribers without a billing mess, rebuilding your archive somewhere you control, and setting up the tagging and sequences that make Kit worth the switch in the first place.
How long this takes
3–5 hours
Most of that time goes into rebuilding automations and repointing forms, not the import itself.
Why switch from Substack to Kit?
Switch if…
- You want full design and domain control instead of Substack’s fixed templates and subdomain structure.
- You want real automation — tag-based sequences and conditional logic — rather than a flat subscribe-and-receive model.
- You want to sell more than a subscription: courses, one-off products, or paid communities through Kit Commerce.
- You want to build your own website and treat email as one channel rather than the entire product.
- You want granular tagging by source and behaviour to target specific segments over time.
Stay put if…
- A meaningful share of your subscribers come through Substack’s app and recommendation network, which won’t follow you.
- You want a public, SEO-friendly post archive out of the box — Kit’s archive and site tools are less publication-oriented than Substack’s or beehiiv’s.
- You’re not planning to build automation or products beyond a simple paid subscription, so the extra complexity may not pay off.
Substack vs Kit: the key differences
| What changes | Substack | Kit |
|---|---|---|
| Design control | Fixed templates, Substack subdomain option | Full custom domain and page design |
| Automation | None beyond subscribe/unsubscribe | Tag-based sequences and visual automations |
| Monetisation | Paid subscriptions with a platform fee | Kit Commerce for products, subscriptions, and digital sales |
| Post archive | Built-in public archive by default | Requires your own site or Kit’s simpler hosted pages |
| Discovery | Substack app and recommendation network | None built in — relies on your own channels |
| Segmentation | Free vs paid only | Tags and segments by source, behaviour, and purchase |
| Landing pages | Substack-hosted signup page | Customisable Kit landing pages and forms |
Before you switch, have this ready
- Admin access to your Substack publication and connected Stripe payments.
- A full export of free and paid subscribers from Substack.
- A domain you control, if you plan to build your own site for the archive.
- A written plan for how new subscribers should be tagged and onboarded.
- A list of external links pointing at your current Substack address.
- A decision on how paid content will work going forward — Kit Commerce, a separate membership tool, or simple paid broadcasts.
Step-by-step: Substack to Kit
Step 1: Export subscribers from Substack
In Substack, go to Subscribers and export the full list as CSV. This gives you email addresses and subscription status, though for paid subscriber detail you’ll want to cross-reference your Stripe dashboard directly.
Note where subscribers originally came from if you’ve tracked that at all — referral links, specific posts, or social campaigns — since this is valuable tagging data you won’t easily recover once it’s in a flat CSV.
Separate out anyone who unsubscribed or had payment issues recently so you don’t reimport them as active.
Screenshot
Substack Subscribers export screen
Step 2: Set up tags and forms in Kit
In Kit, go to Subscribers → Tags and set up tags for the segments that matter — paid subscriber, free subscriber, and any source tags you want to preserve from Substack.
Build a Kit landing page or embeddable form to replace your Substack signup page, matching your branding rather than a generic template, since this is one of the main reasons you’re making the move.
Decide whether you want a single list or multiple forms feeding different tags — for most single-newsletter writers, one list with tag-based segmentation is simpler to manage than several separate lists.
Screenshot
Kit Landing Pages & Forms builder
Step 3: Import your subscriber list
Go to Subscribers → Import in Kit and upload your Substack export, applying a base tag such as "migrated-from-substack" to everyone so you can track this cohort separately if issues come up later.
Apply your paid-subscriber tag to anyone confirmed as paying, cross-checked against Stripe rather than the Substack export alone, since paid status in the CSV isn’t always reliable.
Run a small test import first if your list is large, confirming tags and fields land correctly before importing everyone at once.
Screenshot
Kit subscriber import screen with tag assignment
Step 4: Handle paid subscribers and commerce
Decide whether paid content will run through Kit Commerce or a separate tool connected via Stripe. Kit Commerce works well if you’re selling access to paid posts or a simple membership; a dedicated membership tool may suit more complex gated content.
Time the cutover to each subscriber’s Substack renewal date where possible, rather than cancelling Substack billing and starting Kit billing the same day, which is the most common cause of double charges.
Message paid subscribers directly about the change, including what happens to their billing and access, and verify a handful of accounts have correct access before rolling it out fully.
Screenshot
Kit Commerce product and payment setup screen
Step 5: Rebuild your archive on your own site
If you don’t already have a website, this is the point to set one up — even a simple one — since Kit is built to integrate with a site rather than replace the need for one entirely.
Export your Substack posts and republish the ones still worth surfacing, prioritising anything ranking in search or that you regularly link back to.
Link your Kit signup form prominently from the new archive pages so old content keeps converting new subscribers the way it did on Substack.
Screenshot
Website blog page with an embedded Kit signup form
Step 6: Set up onboarding sequences
In Kit, go to Automations and build a welcome sequence triggered on subscription — something Substack never gave you the tools to do. Introduce yourself, link to your best posts, and set expectations for what they’ll receive.
If you have paid content, add a branch or follow-up sequence encouraging free subscribers toward the paid tier at a sensible point after they’ve had a chance to see your regular content.
Test the sequence with your own subscription before switching it on for everyone, checking timing and that tags apply correctly at each stage.
Screenshot
Kit visual automation builder showing a welcome sequence
Step 7: Redirect traffic and wind down Substack
Post a final announcement on Substack explaining the move, linking directly to your new Kit signup page, and explaining what happens to any paid subscription.
Update your social bios, guest post links, and anywhere else you control that currently points at your Substack address.
Keep the Substack publication accessible for a few weeks rather than deleting it outright — old links and search traffic will still land there for a while, and a clear redirect note catches stragglers.
Screenshot
Substack final post with a link to the new Kit signup page
Integrations you need to update
Every one of these is a place contacts or data currently flow into Substack. Work through the list before you stop watching the old account — a missed form is invisible until someone complains they never got your email.
| Integration | What to do |
|---|---|
| Stripe | Connect directly or through Kit Commerce, timing the cutover to avoid double-billing paid subscribers. |
| Website / CMS | Embed Kit forms across your site and connect your archive pages to the signup flow. |
| Custom domain | Set up your Kit-hosted landing pages on a domain or subdomain you control. |
| Zapier / Make | Rebuild any subscriber-triggered automation using the Kit connector. |
| Social bios and link-in-bio tools | Update every link currently pointing at your Substack address. |
| Kit Commerce | Set up product or membership pricing if you’re moving paid content off Substack. |
| Google Search Console | Monitor indexing of your new archive pages after republishing content. |
| Podcast or video descriptions | Update show notes linking to your Substack with your new Kit signup link. |
Troubleshooting: common post-migration problems
Paid subscribers charged on both platforms
Refund the duplicate through Stripe and align future billing cutovers to each subscriber’s existing renewal date rather than a single fixed switch day.
Tags didn’t apply correctly on import
Re-check your CSV column mapping during import — Kit applies tags based on exact column matching, and a mislabelled column silently skips the tag rather than erroring.
New subscribers aren’t entering the welcome sequence
Confirm the automation trigger is set to the correct form or tag, not the default list — a common mistake when forms and tags are set up separately.
Search traffic dropped after leaving Substack
Substack subdomains can’t be redirected. Update every external link you control and make sure your new archive pages are properly indexed by search engines.
Growth slowed noticeably post-migration
This is usually the loss of Substack’s discovery network. Invest in your own promotion channels and consider Kit’s Creator Network as a partial replacement.
Imported posts look broken on the new site
Substack export formatting rarely survives a direct paste. Rebuild affected posts manually rather than patching the imported HTML.
Should you make the switch?
The migration itself is rarely the hard part — it is the automations you rebuild and the forms you forget. If the reasons in the "switch if" list above describe your situation, Kit is worth the afternoon. If you are only moving because you are frustrated with an interface, fix the emails first and keep the platform.
Read both sides before you commit: our Substack review covers what you would be giving up, and our Kit review covers what you are buying, including current pricing and where it falls short. Every switch we document is listed on the migration guides hub.