Migration guide

Moving from MailerLite to Kit

Kit publishes a MailerLite-specific migration article, including a clear warning about paid subscribers. Export from MailerLite first, then follow Kit’s importer. Official docs win if anything here drifts.

More guides: Under 2,500 · MailerLite free alternatives · Beehiiv vs Substack vs Kit · Deliverability · Beehiiv → Kit · MailerLite → Kit

1. Export subscribers from MailerLite

MailerLite’s official article “How to export subscribers” is the starting point. Export active subscribers and, separately, unsubscribed and bounced addresses so you can suppress them in Kit. Keep a local copy before you change plans or close the account.

Source: How to export subscribers.

2. Follow Kit’s MailerLite migration guide

Kit’s official article “Migrating from MailerLite to Kit” describes the supported import path (including API-based migration where Kit documents it). Read the current page for prerequisites, such as which MailerLite plan or API access you need.

Kit’s same guide states that there is no convenient way to migrate payment details for paid MailerLite subscribers. The practical path it describes is to cancel on MailerLite and have those readers subscribe again through Kit. Budget time and a clear email sequence for that. Do not promise readers that their card will “just move.”

If you need a manual fallback, use How to import a subscriber list with a CSV that includes status fields.

Sources: Migrating from MailerLite to Kit; Kit list import.

3. Forms, automations, and DNS

• Rebuild signup forms and automations in Kit; they do not arrive as a turnkey copy of MailerLite’s editor.
• Update website embeds and checkout links at the same time you cut over paid billing.
• Authenticate the sending domain on Kit (SPF, DKIM, DMARC) and run the deliverability checklist before a full send.

4. Suggested order

1. Open Kit, authenticate the domain, and test a small send to yourself.
2. Export from MailerLite (actives, unsubscribes, bounces).
3. Run Kit’s official MailerLite importer and reconcile counts.
4. Set up the new paid offer. Tell paying subscribers, with dates, that they will need to re-subscribe.
5. Move forms and turn off MailerLite embeds so new signups do not split across tools.
6. Keep MailerLite available until Kit sends have been clean for a cycle or two.

If you would rather move to Beehiiv than Kit, start from the same MailerLite export, then use Beehiiv’s current official import documentation (not summarized here, so we do not guess at steps). The paid-billing warning still applies: card-on-file rarely follows you to a new processor.