Migrate from Kit
Moving from Kit to SendRaven.
Kit exports subscribers from the Subscribers page, filtered by status, as a CSV it emails you. Export once per status you need: confirmed subscribers to import, and unsubscribed, bounced and complained subscribers to suppress.
Kit charges for confirmed subscribers; SendRaven charges for emails sent and nothing for the list. Broadcasts and sequence emails come across as HTML; visual automations are rebuilt.
Export steps checked 16 November 2026 against help.kit.com and developers.kit.com.
- Subscribers. Set the Status filter to Confirmed, tick the checkbox at the top of the list, then Select all, the ⋮ menu and Export.
- Kit emails a link to the CSV (it also shows in the notifications panel). The link lasts five days.
- Repeat with the Status filter set to Unsubscribed, then Bounced, then Complained, so each comes as its own file.
- Leave out Unconfirmed: those people signed up through a double opt-in form and never confirmed.
Let your AI do it
One prompt moves everything from Kit.
Paste it into Claude, ChatGPT, Cursor or any assistant with SendRaven connected. It gets your data out of Kit, shows you the plan with counts, and waits for your OK before it writes anything.
- Contacts, opt-outs, preferences, templates and automations, in the order that keeps your domain safe.
- Sends nothing, activates nothing and deletes nothing. The first campaign is left as a draft.
- Needs SendRaven connected first: one guide per assistant.
Move my email from Kit to SendRaven, using the SendRaven MCP tools. If you don't have them, stop and tell me to connect SendRaven first: https://sendraven.ai/mcp
Getting my Kit data:
- If you can reach Kit's API (a connector, its MCP server, or code you can run), ask me for an API key and read everything from there.
- If not, tell me exactly what to export and ask me to upload the files here: Subscribers → set the Status filter → tick the top checkbox → Select all → ⋮ → Export, once for Confirmed and once each for Unsubscribed, Bounced and Complained (Kit emails each CSV); and each broadcast's and sequence email's HTML.
Before you write anything, show me what you found and your plan, with counts, and wait for my OK. Then bring over everything SendRaven can hold, in this order:
1. Sending domain: check list_sending_domains. If the domain I send from is not there, add_sending_domain, show me the DNS records to publish, and run verify_sending_domain once I say they are live.
2. List: use mine from list_audiences, or create_audience "Kit import".
3. Opt-outs before anyone else, so nobody who left is mailed again: Unsubscribed subscribers (status unsubscribed), Bounced (bounced) and Complained (complained); the API calls unsubscribed cancelled. Import them with import_contacts and that status, source "Kit". Never import an opted-out person as subscribed.
4. Subscribers: import_contacts in batches of up to 5,000, with first and last name, tags, and custom fields as attributes. Leave out anyone who never confirmed. Do not trigger automations. For a list of more than a few thousand, ask whether I would rather upload that CSV in SendRaven (Contacts → Import) while you do the rest.
5. Templates: broadcasts and sequence emails (their content field on Kit's API), with Liquid tags like {{ subscriber.first_name }}. Save each with save_template, merge tags rewritten as SendRaven {{variables}} ({{first_name}}, {{email}}), and their unsubscribe links and footers removed: SendRaven adds its own to every marketing email.
6. Automations: Visual automations and sequences do not export. From what you can read, or what I describe, rebuild each with create_automation and leave it as a draft.
7. First campaign: tag confirmed subscribers Kit does not mark as Cold as engaged, create_segment on that tag, then draft one campaign to it with create_broadcast and check it with preview_broadcast. A new domain warms up, so it starts with engaged readers.
Rules: send nothing, activate nothing, and delete nothing, in Kit or in SendRaven. Finish with a table of what came over (contacts imported and updated, suppressed, topics, templates, automations) next to Kit's own numbers, and list anything you could not move.What moves
What comes across, and what you rebuild.
- In Kit
Subscribers
In SendRavenEmail address and first name are matched automatically; Kit has no last name field.
- In Kit
Tags
In SendRavenThe tags column imports as tags.
- In Kit
Custom fields
In SendRavenEach becomes a custom property, typed from its values.
- In Kit
Unsubscribed, bounced, complained
In SendRavenExported separately with Kit's Status filter and imported with that status, or with the import's status column.
- In Kit
Unconfirmed
In SendRavenLeft out. They never confirmed a double opt-in, and Kit cannot email them either.
- In Kit
Broadcasts and sequence emails
In SendRavenTheir HTML comes from Kit's API (broadcast content, sequence email content) into SendRaven templates.
- In Kit
Visual automations
In SendRavenRebuilt as SendRaven automations; Kit has no export for them.
The file
What the export looks like, and how the import reads it.
Kit's help center lists what the export carries: first name, email address, when the subscriber was created, status, tags, location, attribution, and one column per custom field. It does not publish the exact header names, so check the mapping step: the address and first name are matched for you, tags go to tags, and each custom field becomes a property.
The status column reads the same as the filter you exported with. If it is missing, choose the status for the whole file in the import, as for any one-status export.
The part that matters
Bring the opt-outs.
Kit keeps the people you must not mail as statuses, not as a separate list: Unsubscribed, Bounced (hard bounces only) and Complained (marked as spam, which Kit also unsubscribes). Export each with the Status filter and import it with the matching status: unsubscribed suppresses marketing only; bounced and complained suppress everything.
Do it before the first campaign. A subscriber export filtered to Confirmed contains none of them, so a migration that imports only that file has no record that they left.
Templates and sending
The copy and the code.
Kit's email content is HTML with Liquid tags. A broadcast's HTML is the content field of GET /v4/broadcasts/{id} on Kit's API, and a sequence email's is GET /v4/sequence-emails/{id}. Save each as a SendRaven template and rewrite the Liquid: {{ subscriber.first_name }} becomes {{first_name}}. Drop Kit's unsubscribe link and footer; SendRaven adds its own to every marketing email.
Kit's Cold status is still Confirmed: people who have not opened or clicked for a while. They import as subscribed. Leave them out of the first campaigns from the new domain; tag the rest as engaged and start there.
What it costs
Estimate the bill by emails sent, not contacts.
- Emails a month
- 200,000
- SendRaven, Standard plan
- $85.00 a month
- For the 50,000 contacts
- $0
On a new sending domain, the first campaign to all 50,000 goes out over 8 days: the warm-up pauses it at each day's ceiling and resumes it at midnight UTC. The ceiling keeps rising for 14 days from the first send, then comes off. Published plan prices, before tax. Transactional mail, if you move it too, counts on the same meter; replies are never metered.
Then, in order
The steps every migration shares.
Verify your domain first
Add the domain under Domains and publish the DNS records it gives you. Use a subdomain you have not sent from before if you can (mail.yourdomain.com for transactional, news.yourdomain.com for campaigns), so the two reputations stay separate. Nothing sends until this is green, and it can take a while for DNS to settle, so start it before the export.
Import the subscribers
Contacts → Import a CSV. Pick or create the list, upload the export, and check the column mapping: address, names, tags, and which columns become custom properties. Re-running the same file is safe: existing contacts are updated, not duplicated.
Import the opt-outs
Then the unsubscribed, bounced and complained lists, with the matching status. Each one is flagged and suppressed before your first send: unsubscribes for marketing only, bounces and complaints for everything. An import never resubscribes someone who has opted out here.
Check the counts
The audience page shows how many were imported, updated and suppressed. Compare the suppressed count to what the old provider reported. If it is far off, the status column was read differently from how you meant. The mapping step shows what each value became.
Switch the API key
For transactional mail, point the code at POST /v1/emails with a SendRaven key. The request shape is from, to, subject, html or text, and an Idempotency-Key header. Keep the old key alive for a day in case something still points at it.
Send the first campaign to the engaged part of the list
A new domain has no history, and mailbox providers judge it on the first few thousand messages. Opens and clicks start from your first SendRaven send, so use the old provider's engagement: tag the recently engaged people on import, send the first campaign to a segment on that tag, then widen. A new sending domain also warms up, so a large first campaign spreads over several days on its own. The reputation gate refuses a campaign once the bounce or complaint rate is already high; it cannot refuse the one that gets you there.
Questions
Asked by people leaving Kit.
What happens to subscribers marked Cold?
They are confirmed subscribers who have stopped opening and clicking, so they import as subscribed. Do not send them the new domain's first campaigns: a run of messages nobody opens is what mailbox providers judge a new domain on. Send to the engaged part first and bring the cold part in once the domain has a history.
Can an AI agent read my Kit account directly?
Yes, if it can reach Kit's API or Kit's own MCP server. Kit's API takes an API key from Settings → Developer, and the migration prompt above asks for one when the assistant can use it. Without that, the prompt walks you through the exports instead.
Do Kit sequences keep running for people already in them?
No sequence state carries across. Let the Kit sequence finish for people already in it, and enrol only new signups in the SendRaven automation. Run both for the length of the sequence, then turn Kit off.

Start with the domain.
3,000 emails a month, inbound included, and no charge until you switch paid sending on. Verify the domain today and import the list once the DNS has settled. The other guides are on the migrate page.

