Migrate from MailerLite
Moving from MailerLite to SendRaven.
MailerLite exports subscribers one status at a time: pick the status, choose the columns, export a CSV. Export Active to import, and Unsubscribed, Bounced and Junk to suppress.
Only the columns visible in the list are exported, so set the columns first: groups and custom fields are off unless you add them.
Export steps checked 16 November 2026 against mailerlite.com/help and developers.mailerlite.com.
- Subscribers. In the status dropdown (it reads Active subscribers), keep Active.
- Set columns, and add Groups and every custom field you want to keep. Only visible columns are exported.
- Select everyone with the arrow next to the Subscriber column, then Actions → Export as CSV.
- Repeat for Unsubscribed, Bounced and Junk, each as its own file. Leave Unconfirmed out.
Let your AI do it
One prompt moves everything from MailerLite.
Paste it into Claude, ChatGPT, Cursor or any assistant with SendRaven connected. It gets your data out of MailerLite, shows you the plan with counts, and waits for your OK before it writes anything.
- Contacts, opt-outs, preferences, templates and automations, in the order that keeps your domain safe.
- Sends nothing, activates nothing and deletes nothing. The first campaign is left as a draft.
- Needs SendRaven connected first: one guide per assistant.
Move my email from MailerLite to SendRaven, using the SendRaven MCP tools. If you don't have them, stop and tell me to connect SendRaven first: https://sendraven.ai/mcp
Getting my MailerLite data:
- If you can reach MailerLite's API (a connector, its MCP server, or code you can run), ask me for an API key and read everything from there.
- If not, tell me exactly what to export and ask me to upload the files here: Subscribers → pick the status → Set columns (add Groups and every custom field) → select all → Actions → Export CSV, once each for Active, Unsubscribed, Bounced and Junk.
Before you write anything, show me what you found and your plan, with counts, and wait for my OK. Then bring over everything SendRaven can hold, in this order:
1. Sending domain: check list_sending_domains. If the domain I send from is not there, add_sending_domain, show me the DNS records to publish, and run verify_sending_domain once I say they are live.
2. List: use mine from list_audiences, or create_audience "MailerLite import".
3. Opt-outs before anyone else, so nobody who left is mailed again: Unsubscribed (status unsubscribed), Bounced (bounced) and Junk, which are spam complaints (complained). Import them with import_contacts and that status, source "MailerLite". Never import an opted-out person as subscribed.
4. Subscribers: import_contacts in batches of up to 5,000, with first and last name, tags, and custom fields as attributes. Leave out anyone who never confirmed. Do not trigger automations. For a list of more than a few thousand, ask whether I would rather upload that CSV in SendRaven (Contacts → Import) while you do the rest.
5. Preferences: groups people joined themselves to choose what they get. Make each a topic with save_topic, then record who is in and out with import_topic_preferences.
6. Templates: campaigns and automation emails (their HTML from MailerLite's API), with merge tags like {$name}. Save each with save_template, merge tags rewritten as SendRaven {{variables}} ({{first_name}}, {{email}}), and their unsubscribe links and footers removed: SendRaven adds its own to every marketing email.
7. Automations: automations do not export. From what you can read, or what I describe, rebuild each with create_automation and leave it as a draft.
8. First campaign: tag subscribers who opened or clicked a recent campaign (each campaign's report → Subscriber activity) as engaged, create_segment on that tag, then draft one campaign to it with create_broadcast and check it with preview_broadcast. A new domain warms up, so it starts with engaged readers.
Rules: send nothing, activate nothing, and delete nothing, in MailerLite or in SendRaven. Finish with a table of what came over (contacts imported and updated, suppressed, topics, templates, automations) next to MailerLite's own numbers, and list anything you could not move.What moves
What comes across, and what you rebuild.
- In MailerLite
Subscribers
In SendRavenEmail and name are matched automatically.
- In MailerLite
Custom fields
In SendRavenAdd them under Set columns before exporting; each becomes a custom property.
- In MailerLite
Groups
In SendRavenAdd Groups under Set columns. Import them as tags, or, where people joined a group themselves to choose a kind of email, as a topic.
- In MailerLite
Unsubscribed, bounced, junk
In SendRavenOne export each, imported with that status. Junk is MailerLite's name for a spam complaint.
- In MailerLite
Unconfirmed
In SendRavenLeft out. They never confirmed, and MailerLite does not email them either.
- In MailerLite
Campaigns and automation emails
In SendRavenTheir HTML comes from MailerLite's API into SendRaven templates.
- In MailerLite
Automations
In SendRavenRebuilt as SendRaven automations; MailerLite has no export for them.
The file
What the export looks like, and how the import reads it.
The file has the columns you chose under Set columns, with a few MailerLite always includes, the email address among them. The mapping step matches the address and name, turns each custom field into a property, and Groups into tags.
Each file holds one status. Where it has no status column, choose that status for the whole file in the import: everyone in it is unsubscribed, bounced, or, for Junk, complained.
The part that matters
Bring the opt-outs.
MailerLite's statuses are the record: Unsubscribed, Bounced (a hard bounce, or three soft bounces in a row) and Junk (marked as spam). Export each one and import it with the matching status: unsubscribed suppresses marketing only; bounced and junk, imported as complained, suppress everything.
Do it before the first campaign. An export of Active subscribers contains none of them.
Templates and sending
The copy and the code.
A campaign's HTML comes from MailerLite's API: the campaign's emails list their ids, and GET /api/emails/{id}/html returns the HTML. An automation email's is GET /api/automations/{id}/emails/{email}/content. Save each as a SendRaven template, replace merge tags such as {$name} with {{first_name}}, and drop {$unsubscribe} and the footer; SendRaven adds its own to every marketing email.
What it costs
Estimate the bill by emails sent, not contacts.
- Emails a month
- 200,000
- SendRaven, Standard plan
- $85.00 a month
- For the 50,000 contacts
- $0
On a new sending domain, the first campaign to all 50,000 goes out over 8 days: the warm-up pauses it at each day's ceiling and resumes it at midnight UTC. The ceiling keeps rising for 14 days from the first send, then comes off. Published plan prices, before tax. Transactional mail, if you move it too, counts on the same meter; replies are never metered.
Then, in order
The steps every migration shares.
Verify your domain first
Add the domain under Domains and publish the DNS records it gives you. Use a subdomain you have not sent from before if you can (mail.yourdomain.com for transactional, news.yourdomain.com for campaigns), so the two reputations stay separate. Nothing sends until this is green, and it can take a while for DNS to settle, so start it before the export.
Import the subscribers
Contacts → Import a CSV. Pick or create the list, upload the export, and check the column mapping: address, names, tags, and which columns become custom properties. Re-running the same file is safe: existing contacts are updated, not duplicated.
Import the opt-outs
Then the unsubscribed, bounced and complained lists, with the matching status. Each one is flagged and suppressed before your first send: unsubscribes for marketing only, bounces and complaints for everything. An import never resubscribes someone who has opted out here.
Check the counts
The audience page shows how many were imported, updated and suppressed. Compare the suppressed count to what the old provider reported. If it is far off, the status column was read differently from how you meant. The mapping step shows what each value became.
Switch the API key
For transactional mail, point the code at POST /v1/emails with a SendRaven key. The request shape is from, to, subject, html or text, and an Idempotency-Key header. Keep the old key alive for a day in case something still points at it.
Send the first campaign to the engaged part of the list
A new domain has no history, and mailbox providers judge it on the first few thousand messages. Opens and clicks start from your first SendRaven send, so use the old provider's engagement: tag the recently engaged people on import, send the first campaign to a segment on that tag, then widen. A new sending domain also warms up, so a large first campaign spreads over several days on its own. The reputation gate refuses a campaign once the bounce or complaint rate is already high; it cannot refuse the one that gets you there.
Questions
Asked by people leaving MailerLite.
Why is my export missing groups or custom fields?
MailerLite exports only the columns shown in the list. Add Groups and each custom field under Set columns, then export again.
Should groups become tags or topics?
A group you put people in (customers, webinar 2026) is a tag. A group people joined themselves to choose what they get (product news, weekly tips) is a topic, so they can leave that one and keep the rest.
Can an AI agent read my MailerLite account directly?
Yes, through MailerLite's API with a token from Integrations → MailerLite API, or MailerLite's own MCP server. The migration prompt above uses either when the assistant can reach it, and otherwise walks you through the exports.

Start with the domain.
3,000 emails a month, inbound included, and no charge until you switch paid sending on. Verify the domain today and import the list once the DNS has settled. The other guides are on the migrate page.

