Move a Launch List from Kit Without Paying for Dormant Subscribers

If your list is large but you contact only a focused segment each month, a Kit alternative that prices by emails sent can fit better than subscriber-tier billing. Lumail stores unlimited subscribers on every plan and prices by email volume. The safe migration is not a full export on day one: move one representative launch, prove the audience and delivery workflow, and compare a normal month with a peak month.

This page is published by Lumail. Check both providers' current pricing and product documentation before deciding.

The pricing model is the decision

Kit counts unique active subscribers for its plan tiers. Its free Newsletter plan currently supports up to 10,000 subscribers, while paid Creator starts at $33 per month billed annually for 1,000 subscribers. Kit's official pricing page is the current source for those terms.

Lumail charges for email volume instead of stored subscriber count:

Lumail plan	Included volume	Current base price
Free	3,000 emails per month	$0
Premium	40,000 emails, then $0.60 per 1,000	$20 per month
Business	400,000 emails, then $0.40 per 1,000	$200 per month

Subscribers are unlimited on every Lumail plan. Verify the current terms on the Lumail pricing page.

When send-volume pricing wins

Take a list of 50,000 stored subscribers and one monthly launch sent to a 10,000-person segment.

• Lumail prices the 10,000 delivered emails. The other 40,000 stored records do not change the plan.
• Kit prices the paid plan around the active subscriber tier, so the full active list affects the tier even when most people do not receive that launch.

Now invert the case. A 1,000-person list receiving a weekly newsletter sends roughly 4,500 emails per month. That exceeds Lumail's free allowance, while Kit's free Newsletter plan may cover the use case. Send-volume pricing is not universally cheaper; it favors a list that is large relative to monthly sends.

Model three states before moving:

1. a normal month;
2. the largest launch month from the last year;
3. the list size and send frequency you expect twelve months from now.

The full Lumail versus Kit comparison covers commerce, recommendations, MCP access, workflows, and transactional email alongside price.

Kit now has an MCP too

Do not choose on outdated “AI-native versus no MCP” claims. Kit documents a 65-plus-tool OAuth MCP for paid plans that works with Cursor, Claude, ChatGPT, and other compatible clients. It can read account data, draft broadcasts, manage subscribers, and route consequential actions through confirmation in the Kit app.

Lumail's full catalog currently contains 89 organization-scoped tools. Its Claude Code OAuth plugin exposes read and safe draft-write operations, while the API-token MCP and CLI cover broader operations with confirmation controls.

Choose on the actual work:

Need	Better question
Creator commerce	Do you need Kit's paid products and recommendation network?
Product email	Do newsletters, workflows, and transactional messages need one organization?
Agent access	Which client, tool scope, and confirmation model match the team?
Cost	Is list size or monthly delivered volume the stronger driver?

Migrate one launch before the whole list

1. Export complete consent state

Export active subscribers, unsubscribes, bounced addresses, complaints, tags, custom fields, and the source of consent. A migration that copies only active emails can accidentally make suppressed people contactable again.

2. Import a controlled segment

Start with internal addresses and a small consented segment that represents the real launch audience. Preserve the tags needed to recreate the campaign filter.

3. Authenticate the sending domain

Configure the required DNS records, verify the sender, and leave Kit live while records propagate. Do not move acquisition forms or active automations yet.

4. Rebuild one campaign and one automation

Choose the workflow that matters commercially: the launch campaign, welcome sequence, or buyer follow-up. Recreate its trigger, waits, branches, goal, and exit conditions. Test success, negative, and early-exit paths.

5. Run the same launch preflight

Read back the campaign ID, sender, audience rule, recipient count, links, unsubscribe state, and schedule. Send a test. Confirm delivery only after the rendered result matches the approved offer.

6. Compare operation as well as price

Measure:

• monthly cost in a normal and peak month;
• time from source material to approved draft;
• manual steps between agent, editor, and send;
• deliverability and complaint signals;
• clicks and attributed purchases;
• the time required to answer one subscriber-level support question.

Only then decide whether to move the remaining audience and automations.

What Lumail does not replace

Lumail does not provide Kit's paid newsletter products, digital-product checkout, or recommendation network. If those drive audience growth or revenue, keep them in the stack or choose Kit. A lower email-platform bill is not a win if the migration removes the system that acquires or monetizes the audience.

Use one prompt pack on either side of the migration

The same seven jobs remain: drafting, subject lines, click-based segments, re-engagement, changelog conversion, performance review, and a welcome sequence. Keep the prompts stable while changing the delivery system so the comparison is easier to interpret.

Get the seven prompts that run a newsletter, then use the Claude Code launch playbook or Cursor newsletter playbook for the first representative campaign.