SendBeam

Move-in · from Kit

Moving from Kit to SendBeam

Subscribers, the people who unsubscribed, tags, custom fields and whatever consent evidence Kit kept — moved in the order that keeps you compliant, without asking a single person to confirm again.

Start free and import Have us do it

Weighing it up first? Read SendBeam vs Kit.

Before you start

What you need from Kit.

A Kit API key

Settings → Developer → API Keys → use the v4 key

Kit does not issue a read-only key, so create one for the import and delete it afterwards. SendBeam only ever reads with it: the key stays in your browser tab for the visit, is sent with each request and is never stored, logged or shown again. Nothing on Kit is changed.

Their help page: help.kit.com/en/articles/9902901-kit-api-overview

Or a Kit CSV export

Subscribers → tick the top checkbox → Select all → ⋮ → Export (link arrives by email, valid five days)

Email, first name, state, created date, tags and custom fields. Unsubscribed people are included with their state.

Their help page: help.kit.com/en/articles/2502489-how-to-export-subscribers-in-kit

A workspace for each site

One SendBeam login covers every site you run: a workspace each, one pooled bill. Free is 500 contacts across 2 workspaces, Starter $9 is 2,500 across 5, Pro $29 is 10,000 across as many as you like. Move the sites one at a time if you prefer.

Your DNS, or someone who has it

Each sending domain needs two records — DKIM and an aligned return path — verified before an address is imported. On Cloudflare we can write them for you; anywhere else it is two values to paste.

The order

Five steps, in this order, and you keep sending throughout.

The order matters more than the tool. Opt-outs before subscribers, domain before the first send, and the old account stays open until the sync window closes.

  1. 01 Suppressions firstEveryone who unsubscribed, bounced or complained on Kit goes in before a single subscriber. In SendBeam those rows land on the workspace's suppression list: campaigns never reach them, a later import cannot turn them back into subscribers, and they do not count towards your plan's contact limit.
  2. 02 Sending domainAdd the site's sending domain and verify it before anything is imported, so the first campaign is not waiting on DNS. Delivery is managed by SendBeam — there are no provider keys to set up — and each site gets its own DKIM record and aligned return path.
  3. 03 ImportPaste the Kit key into Contacts → Import → Import from another platform, pick what to bring, and import. Contacts, statuses, tags, custom fields, original opt-in dates and the consent evidence Kit keeps all come across in one pass.
  4. 04 Parallel runKeep sending from Kit while you check this side: rebuild your forms, put the embed on the site, and send one campaign from SendBeam to a small segment before you trust it with the whole list.
  5. 05 Cutover with a 30-day unsubscribe syncSwitch your forms over, send from SendBeam and leave the Kit account open for 30 days. Anyone who unsubscribes there in that window must be unsubscribed here too: Move-in syncs that for you, and on your own it is a weekly export of their opt-outs imported with status set to unsubscribed. Then close the old account.

The same order is written up in the docs: suppression list, sending domain, importing contacts and moving in.

Two routes

Do it yourself, or hand it over.

Route one

Import with your Kit key

In the app, go to Contacts → Import → Import from another platform (/contacts/import/connect), pick Kit, paste the key and press Connect. SendBeam checks the key with one call and shows the account, its lists with subscriber counts and exactly what will and will not come across before anything is written.

  • Opt-outs are written to the suppression list before any contact, so nothing can be mailed by accident.
  • A run handles up to 25,000 contacts and about 45 seconds of work, then offers Continue import from exactly where it stopped. Re-running is always safe.
  • Nothing on Kit is changed, and the import sends no email to anyone.
  • Available in the app on every plan, up to the contacts your plan has room for.

Prefer a file? The CSV importer reads the same columns; the notes below are for a Kit export.

Columns the importer recognises

  • email
  • first_name
  • last_name
  • status
  • tags
  • subscribed_at
  • unsubscribed_at
  • source
  • consent_ip
  • consent_at
  • consent_source

Any other column becomes a custom field keyed by its snake_cased header. Rows with status unsubscribed, bounced or complained go to the suppression list and never count towards your contact limit. Full reference: importing contacts.

Shaping a Kit export

  • The export link is emailed to you and is valid for five days, so start the import the same week.
  • Kit's state column is the status column: rename it to status, and cancelled is read as unsubscribed. A created_at header is already read as subscribed_at; anything else, rename it.
  • There is no opt-in IP and no confirmation timestamp in the file. The sign-up date and the source are the evidence Kit keeps, and both come across.

Route two

Move-in, done for you

You give us a read-only key or a temporary seat that you revoke afterwards. We load the suppressions, set up a sending domain for each site, import every workspace, keep you sending from Kit while you check, switch your forms over and sync unsubscribes from Kit for 30 days after cutover. Two to five business days for the whole account.

  • Included on Pro $29 and Business $79 — every site on the account, one request.
  • Automations rebuilt at US$29 each and templates at US$49 each, quoted before any work starts and waived on Business annual.
  • On Free and Starter you import yourself, and any Setup item can still be bought on its own.
Request a Move-in

What carries over

What arrives with your list.

  • Subscribers with their names, their status and the day they originally joined.
  • The people who unsubscribed, bounced or complained on Kit, as suppression entries with their original dates.
  • Tags — and groups, lists or segments that behave like tags — created here as they are matched.
  • Custom fields, keyed by the lower-cased, snake_cased column or field name, ready for merge tags and segment rules.
  • Consent evidence: Created date and referrer/source per subscriber; no opt-in IP and no confirmation timestamp.

What does not

What no migration carries.

  • Automations. No platform exports them in a form another can run, Kit included. Rebuild them in the SendBeam editor at no cost, or have us do it as a Setup item.
  • Designs. Templates are rebuilt in the SendBeam editor — by you at no cost, or by us as a Setup item.
  • Engagement history. Opens and clicks recorded on the old platform stay there; your stats here start at cutover.
  • People who never confirmed. Rows marked pending, unconfirmed or inactive are counted and left out rather than emailed.

Consent

Changing provider does not require fresh consent, and we do not ask your subscribers to opt in a second time. What matters is that the evidence travels with them. From Kit that evidence is: created date and referrer/source per subscriber; no opt-in IP and no confirmation timestamp. It is stored on each contact as consent_ip, consent_confirmed_at and consent_source, so it shows on the contact and comes back out in an export.

Where a contact has no evidence at all they are left out rather than emailed, and you get the list of who they were so you can decide. If you need an IP and a confirmation timestamp on record, switch double opt-in on for the list here and the next confirmation writes one.

Suppressions go in before anything can send, every access during a Move-in is logged, working copies are deleted after cutover and you can ask for the migration log. The data processing agreement sets this out in full; double opt-in explains what is recorded from here on.

Checklist

Ten things, in order.

  1. 01 Create the Kit API key (Settings → Developer → API Keys → use the v4 key), or export the CSV.
  2. 02 Separate the opt-outs, or check the export carries a status column for them.
  3. 03 Create a SendBeam workspace for the site — one per site, all on one login.
  4. 04 Add the sending domain and wait for it to verify.
  5. 05 Import the opt-outs first, with status set to unsubscribed.
  6. 06 Import the subscribers, keeping subscribed_at and the consent columns.
  7. 07 Read the import summary: imported, updated, suppressed, pending not imported, invalid rows, columns ignored.
  8. 08 Rebuild your forms, swap the embed on your site, and rebuild any automations you rely on.
  9. 09 Send one campaign from SendBeam to a small segment while Kit is still live.
  10. 10 Cut over, then pull Kit's new unsubscribes for 30 days before you close the account.

Bring every site across, not just this one.

One login, a workspace per site and one pooled bill. Start free with 500 contacts, or hand us the keys and keep sending from Kit while we do it.

Start free Request a Move-in

Still comparing? SendBeam vs Kit · price your own sites · plans

Kit is a trademark of its owner and SendBeam is not affiliated with it. The menu paths and export contents above describe Kit as read on their own help pages (help.kit.com/en/articles/2502489-how-to-export-subscribers-in-kit) on 3 September 2026. Platforms move menus; if a path has changed, tell us and we will correct it. Other guides: Move-in and the comparisons.