MIGRATION
Switch from Kit to MailerLite: tags become groups, sequences get rebuilt
Subscribers move cleanly; the work is in structure. Kit organises everything by tags, MailerLite by groups and segments, so your tag logic has to be translated rather than copied. Kit sequences do not export as automations, so plan to rebuild them. Import active subscribers plus unsubscribes and bounces, map tags to groups, then rebuild and test each sequence before cutover.
KitTry Kit 
MailerLiteTry MailerLite What actually transfers
Export your Kit subscribers with tags, subscription status and creation date, then import active ones into a MailerLite group. Bring cold, unsubscribed and bounced addresses across as suppressions, not active subscribers, so you carry your reputation cleanly into the new account. Kit's free tier is generous on subscriber count, so your list may be large; verify the active total against your export before trusting the import. Custom fields map to MailerLite fields by type. What a subscriber export never contains is your sequence logic and your tag automations, so book those as separate rebuilds from the start. The migration checklist lists the counts to confirm.
Tags become groups and segments
Kit runs on tags: one flat system where a tag can mean a topic, a purchase, a source or an automation state. MailerLite splits that into groups and segments. Write down what each tag actually means before importing. Static, identity-style tags, buyer, source, topic, become MailerLite groups. Behavioural or state tags, opened X, in sequence Y, become segment rules or fields you recreate. Do not import hundreds of tags one-to-one; consolidate first, because half of a mature Kit account's tags are usually dead or duplicated. Map each surviving tag to exactly one MailerLite object and note the ones with no clean home.
Sequences are rebuilds
Kit sequences, the timed email series that do most of the work, do not travel as automations. You can copy the email content, but the trigger, timing and tag-based entry and exit have to be rebuilt in MailerLite's automation builder. Inventory each sequence first: what starts it, the delays, what tag or action ends it, and who is currently inside. Contacts mid-sequence in Kit will simply stop when you move them, so decide whether to let those finish in Kit or re-enrol them cleanly in MailerLite. Rebuild the highest-value sequence first, welcome or onboarding, and prove it before the rest.
Test before you cut over
Import into one test group and check it against your inventory: subscriber total, suppressions applied, groups populated, fields intact. Rebuild a sequence, send a seed campaign, and run a real signup through the form to confirm the subscriber lands in the right group and enters the right automation. Only then switch forms and integrations to MailerLite and keep Kit read-only for a billing cycle as rollback. Both bill by subscribers, so price the same list on each first: free plan, paid from $39/mo against free plan, paid from $12/mo. For a fuller feature contrast, read Kit versus MailerLite.
Questions people also ask
Can I keep my Kit sequences?
You keep the email content but not the automation. The trigger, delays and tag-based entry and exit have to be rebuilt in MailerLite. Inventory each sequence, then recreate the highest-value one first and test it before moving the rest.
How do Kit tags fit into MailerLite?
They split in two. Static, identity-style tags become MailerLite groups; behavioural or state tags become segment rules or fields. Consolidate first, because most mature Kit accounts carry many dead or duplicated tags you should not migrate.