Skip to content

MailerLite → AcelleMail Migration — Visual Walkthrough

Export subscribers from MailerLite, import into AcelleMail in 6 clicks. Visual walkthrough on both sides with API-driven option for large lists.

Before you start

You'll need:

  • A MailerLite account with subscriber-export permission
  • An AcelleMail installation up and running
  • ~30 minutes for <100k subscribers

Export from MailerLite

In MailerLite's left sidebar, click Subscribers → choose the group/list to export → Export in the toolbar.

MailerLite asks for format (CSV) and which fields to include — select all custom fields you've defined. The file prepares in the background; check Subscribers → Imports / Exports for the download link (usually <2 minutes).

Exported CSV includes: email, name, all custom fields, signup date, opt-in source, segments memberships.

Import into AcelleMail (the same 6 clicks for every source)

Once you have the CSV exported from your previous platform, the import flow in AcelleMail is identical regardless of where the data came from.

1. Open your destination list

In AcelleMail's sidebar, click Audience → choose the list that will receive the migrated subscribers (or create a new one — New list button top-right).

Lists index

You'll see a per-list overview card with subscriber counts:

List overview

2. Click "Import" in the list toolbar

The wizard entrypoint is on the list detail page:

Import entry point

3. Upload your CSV

Drop the CSV file from the previous platform into the upload area:

Upload empty state

AcelleMail parses the file and confirms detection:

Upload success

4. Map the columns

The wizard auto-detects standard columns (email, first_name, last_name) and shows green Mapped to EMAIL chips. Adjust manually for any non-standard column from the source:

Map columns

5. Pick duplicate handling

In the same screen, choose what AcelleMail does when a subscriber already exists in this list:

  • Skip — keep the existing row, don't overwrite
  • Update — overwrite name/tags/custom fields with values from the CSV
  • Unsubscribe — mark existing rows as unsubscribed (rare; used when re-importing an opted-out list)

6. Run the import

Click Start import. The job runs in the background — close the popup, work elsewhere, return to Audience → [list] → Import to see progress:

Import history

You'll see PendingRunningComplete per import job, with rows-imported / rows-skipped / errors counts.

After the import

  • Verify list count matches your expected size (rows that failed validation appear in the Errors column with a downloadable error CSV).
  • Re-tag if needed — for behavioural data that doesn't fit a CSV column (e.g. "opened campaign X"), you may need to re-create the tag via segmentation rules.
  • Pause for warm-up — if the imported list is large (>10k) and your sending IP is new or recently rotated, run a short warm-up campaign to your most-engaged 10% before the full send. See IP warm-up best practices for the schedule.

Rebuilding MailerLite automations

MailerLite's automation workflows map to AcelleMail's Automations. Equivalent triggers:

MailerLite trigger AcelleMail trigger
Joins group Subscribed to list
Updates field Field value change
Anniversary of date Date relative
Completes a form Subscribed to list (form's target list)
Clicks a specific link Link clicked

Merge-tag syntax differences

MailerLite AcelleMail
{$name} {{ subscriber.first_name }}
{$last_name} {{ subscriber.last_name }}
{$email} {{ subscriber.email }}
{$url_unsubscribe} {{ unsubscribe_url }}
{$url_webversion} {{ web_view_url }}
Advanced: API-driven migration with MailerLite's subscribers endpoint

For large MailerLite accounts or scheduled sync:

Export from MailerLite via API:

# MailerLite v2 API token from Integrations → API
curl -X GET "https://connect.mailerlite.com/api/subscribers?limit=100&page=1" \
  -H "Authorization: Bearer <MAILERLITE_API_TOKEN>" \
  -H "Accept: application/json" \
  -o mailerlite-subscribers.json

Paginate via page; MailerLite returns max 100/page.

Import into AcelleMail:

ACELLE_TOKEN="..."
ACELLE_LIST_UID="..."

jq -c '.data[] | {email: .email, first_name: .fields.name, last_name: .fields.last_name}' mailerlite-subscribers.json \
  | while read sub; do
      curl -X POST "https://acellemail.com/api/v1/subscribers" \
        -H "Authorization: Bearer $ACELLE_TOKEN" \
        -d "{\"list_uid\":\"$ACELLE_LIST_UID\",\"subscriber\":$sub}"
    done

Related articles

24 comments

16 comments

  1. ravi.kumar.del…
    How do you handle the Mailchimp-style merge tags in old templates? We have ~50 templates with *|FNAME|* and dont want to manually rewrite each.
    1. admin
      Right — for RDS specifically, you can change wait_timeout via the parameter group without a reboot if it's set as 'dynamic'. Most defaults are
  2. y.yamamoto
    Did this last year. Confirming: the cron + worker setup is 80% of the install pain. Once those are running, the rest is documentation-following
  3. m.schmidt78
    Tip for anyone planning this: do a dry-run of the import with a small test list first. We caught a CSV encoding issue (Excel saved BOM-prefixed UTF-8) that would've affected all 60k rows.
  4. nadia.r.cl
    If your Mailchimp account has automations triggered by tags, document them carefully BEFORE export — the audit log goes away when you cancel the account and youll need that reference during the rebuild
    1. admin
      Worth adding to the article. PR welcome if you want to author the addition
  5. aditi.s.bom
    we migrated 90k subscribers last march. the parallel period suggestion (10-25-50-75) saved us — the acellemail side hit a deliverability dip on day 3 we wouldnt have caught at 100% cutover.
    1. admin
      Thanks for the breakdown. Saving for our customer-success team's reference library.
  6. v.petrova.ru
    The 8-week timeline is reasonable for marketing-only migrations. If you have transactional email integrated (order confirmations, password resets), add 4-6 more weeks for the API rewiring. That part is underestimated everywhere
  7. ahmed.hassan.c…
    Does this guide assume self-hosted Acelle or does it work with the hosted offering too?
    1. admin
      short answer: yes — set the mysql session variable from your worker's .env on boot and you'll get the longer timeout per connection. we'll add an explicit recipe in the next refresh. tbh
  8. lucas.bernard.…
    what about subscribers who unsubscribed via mailchimp's preference center? does the suppression-list import capture those, or just outright unsubscribes?
    1. admin
      Good question — and one that comes up often enough we should add an FAQ section. Short answer: yes for the common case; the exception is when you're running custom plugins that override the default behavior.
  9. emma.whitaker
    Id push back on the 'random recipient split' for the parallel period. If your campaigns are time-sensitive (flash sales etc), random splitting causes weird timing fragmentation. We split by audience segment instead — simpler ops.
  10. d.cohen.tlv
    Bookmarked. We're evaluating a move next quarter and this is the most operationally-realistic guide I've found.
  11. i.rossi.mil
    Completed this migration in Q1. The list-cleanup step is even more important than this guide makes it. We had 40k subscribers, exported, found that 6k were already on Mailchimp's suppression list. Importing those would've torched our new sender reputation.
  12. tranminh.devop…
    The cost-comparison table is the only honest one I've seen. Most 'AcelleMail vs X' content underestimates the ops cost of self-hosting.
  13. sofia.costa.pt
    For the IP warmup — is dedicated IP worth it at 25k subscribers? Or stick with shared SES?
    1. admin
      we don't recommend that approach in production. It works in dev but has subtle race conditions under concurrent load. Stick with the documented pattern...
  14. cmendoza.mx
    question on DNS migration step — when you say 'add new include alongside old', does that work with strict DMARC alignment or does mixing two SPF includes break the alignment check?
    1. admin
      Yes — strict alignment requires the From: domain to match exactly. Subdomain-level (`bounce.example.com` vs `example.com`) passes relaxed but fails strict. Most operators run relaxed; the rare strict-DMARC setups need explicit subdomain DKIM configuration.
  15. femi.adeyemi
    year 1 cost ended up matching this guide's estimate almost exactly. Year 2 was even better because the VPS upgrade we needed was a one-time $20/mo bump.
    1. admin
      great real-world detail. your point about stale running_pid > 30 min as an alert is something we should add to the diagnostic flow...
  16. bos.devops
    Reading this 2 weeks into our Mailchimp migration. The 8-week timeline is conservative but accurate — we tried to compress to 4 weeks and got bitten by exactly the DNS warmup mistake you describe.

More in Migration & Comparison