Kit to beehiiv Migration Checklist: Subscribers & Payments

Last researched October 5, 2026

You can move a newsletter from Kit to beehiiv, but decide how you will handle subscriber data, automated emails, and recurring payments before switching your signup forms. A successful move means a reader can join, receive the right messages, unsubscribe, and access anything they have paid for.

This checklist is for creators who have chosen beehiiv or are checking whether the move is practical. If you are still choosing a platform, start with our beehiiv vs Kit comparison.

Affiliate disclosure: Creator Tool Brief may earn a commission if you sign up through affiliate links on our beehiiv product page, at no extra cost to you. The checklist below is based on official documentation and editorial planning guidance, not a hands-on migration test.

First check whether your paid subscriptions can move

If you charge readers through Kit, check your payment setup before budgeting for the switch.

beehiiv's specific migration guide says Kit subscriptions using Stripe Express cannot transfer directly. It describes re-subscription or temporary complimentary access as alternatives. An external Standard Stripe setup may qualify for paid migration if the required customer and subscription details are available. Official Kit migration guide

Ask support to confirm the route for your actual account. Keep a written record of who is paid through which date, what happens at renewal, and how readers will hear about any change. Do not delete a subscription product or cancel billing while you are still working out that plan.

If you only run a free newsletter, you can set this billing work aside and concentrate on the subscriber and publishing checks below.

1. Define what has to work on launch day

Before exporting anything, make a short inventory:

Every place readers join: website embeds, landing pages, link-in-bio pages, lead magnets, and partner forms
Each automated email journey, including its entry rule, delays, branches, and exit conditions
The tags and custom fields you actually use to choose recipients or personalize emails
Your public archive, important inbound links, and any restricted posts
Your sending address, reply inbox, domains, and connected tools
Paid access and renewal arrangements, if applicable

For each item, add an owner and a pass/fail test. “Website form works” is vague. “A new test signup receives the promised download once and appears in the intended segment” gives you something to verify.

Choose the beehiiv plan around this inventory. The current pricing page lists paid subscriptions and automations under Lite; Pro adds features including branding removal and webhooks. Check your subscriber count and required features before committing to a billing cycle. beehiiv pricing

For the cost decision, use our beehiiv pricing guide. Avoid paying annually just to discover that a critical workflow still needs rebuilding.

2. Export the right people from Kit

Kit's documented route is Subscribers → Status → Confirmed subscriber. Select the list, then use Select all so you export everyone in that view rather than only the current page. Open the three-dot menu and choose Export. Download the CSV from the email or notification promptly: the link expires after five days. Kit's export includes status, tags, custom fields, and other subscriber details. Kit subscriber export instructions

Keep an untouched backup and work on a separate copy. Record the export time and eligible subscriber count. If readers can still subscribe or unsubscribe in Kit during preparation, this first file is a snapshot, not your final sending list.

Preserve your opt-out records and apply changes made after that snapshot before the first production send. Do not turn an unsubscribed contact back into an active reader to make the totals match.

3. Map a small test import before the full list

Start with a small, consented test batch that represents your real data: a subscriber with several tags, one with an empty optional field, and one with the fields used by your most important segment. Use accounts you control where possible.

beehiiv's current import flow runs from upload to field mapping, optional onboarding, then review. Check the preview carefully. For existing contacts, custom-field overwrite is enabled by default when applicable; blank CSV cells can erase existing values. Turn it off when you need to preserve those values. Existing tags are retained and imported tags are added. Current subscriber import guide

Write a mapping sheet with four columns: Kit field, destination field, example value, and verified result. A successful upload count alone will not tell you whether “customer” became an ordinary text field when your email targeting needs it to be a tag.

If signup history matters, beehiiv says it normally uses the import date. Its Kit guide explains how to preserve the original date in a custom field and request a support adjustment. Date handling

4. Keep existing readers out of a duplicate welcome sequence

In beehiiv's import onboarding step, automation enrollment is optional. Only live automations enroll subscribers, and publishing them requires a paid plan. Review those selections before starting the import. The final review also shows whether the batch fits your subscriber allowance; an oversized batch can be held rather than partially imported. Import onboarding and limits

Our recommended default for a migration test is no automatic enrollment until you have decided which readers should receive which emails.

Plan to rebuild Kit workflows in beehiiv rather than treating a subscriber CSV as a workflow export. beehiiv's comparison documentation explicitly describes recreating Kit automation flows in its builder. Automation migration note

Test at least three journeys:

A brand-new reader gets the intended welcome messages once
An existing reader receives the regular newsletter without restarting an old sequence
A buyer or paid member avoids emails asking them to buy something they already have

If any of these fail, pause the switch and fix the trigger or audience rules first.

5. Move the archive and check restricted content separately

beehiiv now documents a Kit content importer under Settings → Content Import, using your Kit newsletter site URL. Set your default post styling beforehand. Its guide says importing paywalled Kit posts requires making them public temporarily and then restoring paywalls individually in beehiiv. Archive migration instructions

Temporary public exposure may be unacceptable for your material. If so, pause and agree on another approach with support before proceeding.

Choose a few representative posts for review: an image-heavy issue, a post with downloads, an older article, and restricted content if you have it. Check layout, links, dates, and access with both a signed-out visitor and the appropriate member account.

Create an old-URL-to-new-URL list for important pages. Test those addresses directly after the switch rather than assuming an archive import preserves all inbound links. beehiiv documents redirect tools for paid plans using its new Website Builder; confirm how the old hostname will be handled too. Website redirect options

6. Verify the sending domain before announcing the move

beehiiv requires DMARC for custom domains. Its domain instructions also distinguish an email domain that is verified from one that is actually in use. Follow the records generated for your account and check that the sending domain is active before a production send. Custom domain setup

Save the existing DNS configuration before changing it. If your main website lives elsewhere, decide deliberately which hostname beehiiv should use; do not accidentally replace the site's hosting records.

Send test messages and inspect the sender name, reply destination, images, links, and unsubscribe flow. A delivered test message is useful evidence, but it does not guarantee inbox placement for the whole audience.

7. Switch entry points and reconcile the final list

Choose a cutover window when you can watch the result. Use this order as a planning checklist, adapting it to your setup:

Finish your test imports, workflow tests, and content review
Record the last newsletter or automated message sent from Kit
Replace forms, integrations, and signup links with their new destinations
Reconcile new subscriptions and opt-outs since the first export
Import the final eligible batch with the intended onboarding settings
Compare expected recipients against accepted, rejected, and updated records
Send your first planned newsletter and review failures and replies

Avoid scheduling the same campaign in both services. Maintain access to Kit while resolving missing records and unexpected emails. Retire the old setup only after the functions you actually use have passed their tests and, where relevant, paid access and billing have been reconciled.

A practical go or no-go checklist

Proceed when you can answer yes to each applicable question:

Can a new reader join from every signup route you intend to keep?
Are tags, custom fields, and opt-outs correct in the destination?
Do imported readers avoid unwanted welcome or sales emails?
Do archive links work, with restricted posts still restricted?
Is your sending domain configured and active?
Do paid readers have the correct access and an agreed renewal path?
Do you have backups and a record of what changed?

If a critical answer is no, keep testing before retiring Kit. Migration work is easier to resolve before the next campaign goes out.

Next step: Review the plan requirements and signup option on our beehiiv product page. If the billing transition or workflow rebuild outweighs the benefit of moving, use the Kit product page and our comparison to reconsider the decision.

Methodology

We checked the official documentation linked above on October 5, 2026. Product-specific steps are documented capabilities; the inventory, testing order, and launch checklist are editorial recommendations. We did not migrate a live account or test deliverability. Interfaces and plan limits can change, so confirm the settings shown in your own account before acting.