Migration guide

How to migrate from ConvertKit (Kit) to self-hosted email

Q: Do my ConvertKit sequences and automations transfer?

Not automatically — you rebuild them in Broadcast's drip automations. The logic maps over directly (triggers, delays, conditions), and most creators only need to recreate the few sequences that actually perform.

Leaving ConvertKit—now Kit—means moving your subscribers cleanly and rebuilding your sequences and forms. This guide covers the whole path to self-hosted Broadcast: export, import, templates, automations, warm-up, and your first send, with no downtime.

Buy Broadcast — $250 Calculate your savings

Why creators leave ConvertKit/Kit: pricing scales with your subscriber count, so a growing list means a growing bill every month—and your audience and reputation live on Kit’s servers. Broadcast is self-hosted software you buy once: your server, your data, unlimited subscribers, no recurring fee.

What transfers—and what you rebuild

Setting expectations up front so there are no surprises.

Moves cleanly

• Subscribers (via CSV)
• Tags
• Custom fields
• Subscribe/unsubscribe status

Rebuild or replace

• Sequences & visual automations
• Forms (rebuild in Broadcast)
• Landing pages (host on your own site)
• Creator commerce (paid products, tips)

Honest note: Kit’s landing pages and creator-commerce features (paid newsletters, products, tips) are platform-specific and don’t carry over. If selling through Kit is central to your business, weigh that before switching.

The migration, step by step

1

Export your subscribers from ConvertKit/Kit

In Kit, go to Subscribers, filter if needed, and use Export to download a CSV. It includes email addresses, state, tags, and custom fields.
2

Set up Broadcast

Buy a license, deploy on your server, and connect your email provider. The installation guide covers setup, and SES vs Postmark vs Mailgun helps you pick a relay.
3

Import your list

Upload the CSV and map columns to fields and tags; unsubscribed contacts stay unsubscribed. See managing subscribers for the import flow.
4

Recreate templates and forms

Rebuild your email template in Broadcast’s editor and recreate your signup forms, embedding them on your own site so new subscribers flow straight in.
5

Rebuild your sequences

Recreate your welcome sequence and nurture flows with Broadcast’s drip automations and conditional logic. Migration is a good moment to prune sequences you no longer use.
6

Warm up and test

Ramp volume gradually and verify authentication first. Follow the deliverability guide and domain warm-up, and run a spam check before the first big send.
7

Send your first broadcast

Switch your forms to Broadcast, send to an engaged segment, and you’re off Kit—owning your audience and your costs.

Zero-downtime tip

Keep Kit active until your first Broadcast sends land well. Run both in parallel for a week, route new signups to Broadcast first, then cancel Kit once you’re confident.

What it costs after you switch

Instead of a Kit plan that grows with every new subscriber, you pay a one-time $250 license, low hosting (~$5–20/mo), and your provider’s per-send rate (Amazon SES is about $0.10 per 1,000 emails). The larger your list, the more a one-time purchase beats per-subscriber pricing.

Calculate your exact savings →

Frequently Asked Questions

No. You export your subscribers as CSV and import them into Broadcast, including tags, custom fields, and subscribe status. You’re moving the same audience to infrastructure you own.

Not automatically—you rebuild them in Broadcast’s drip automations. The logic maps over directly (triggers, delays, conditions), and most creators find they only need to recreate the few sequences that actually perform.

Rebuild forms in Broadcast and embed them on your own site. Kit’s hosted landing pages and creator-commerce features are platform-specific; if you rely on selling through Kit, weigh that before switching.

Not if you warm up gradually and set up SPF, DKIM, and DMARC first—see the deliverability guide. Keep Kit running in parallel for about a week so there’s zero downtime: move new signups first, then cancel once Broadcast is sending well.