MailerLite
MailerLite maps subscriber import columns to groups
Plan a cleaner MailerLite import with meaningful group mapping, a consultant example and checks for existing contacts, empty fields and automation.
EmailTonic verdict
Preserve useful audience labels, then verify the result with a small import. A cleaner group structure matters more than copying every historical tag.
What changed in subscriber imports
MailerLite’s 19 October update adds group mapping from import columns, with a review step for proposed groups. This is particularly relevant when an export from another email tool contains audience labels that you want to preserve without rebuilding every membership manually.
EmailTonic has reviewed the product announcement and official import documentation. We have not performed a migration using this release. The example and checks below are an editorial migration plan, not evidence of a completed account test or a claim that every source format will import cleanly.
Decide what each label means first
A migration is a good moment to separate useful audience information from historical clutter. A label such as Workshop interests may support a real editorial decision. A label such as Export final new 2 usually describes an old process rather than a reader preference. Do not carry both forward automatically just because they exist in the source file.
Use groups for deliberate membership and decide separately which information belongs in a subscriber field. Before uploading, write a short mapping sheet with the original value, intended destination and reason for keeping it. Ask the owner of future campaigns to review it. That conversation is more valuable than cleaning up dozens of unexplained groups later.
- Clean the source labels
- Review group mapping
- Verify memberships and automation
Example mapping for a consultant newsletter
These are suggested decisions, not special names or reserved fields in MailerLite. Use a few internal test records to demonstrate the intended result. Include a person who should belong to two groups and a record that should receive no new membership. Keep test addresses under your control.
| Source value | Proposed destination | Check before approval |
|---|---|---|
| Workshop | Workshop interests group | Does the label still reflect interest? |
| Client | Current clients group | Should clients skip prospect emails? |
| PL | Language field or a deliberate group | How will language selection be maintained? |
| Old export batch | Skip unless operationally needed | Who will use it after migration? |
Avoid an accidental welcome sequence
The official import guide includes a setting controlling whether imported subscribers enter automations associated with a group. Review it deliberately. It also describes updating fields with empty values, another choice that deserves attention before importing over existing records.
For a consultant moving an established newsletter, a contact is not necessarily a new lead merely because the destination account has not seen that address before. Write down which existing readers should skip onboarding. Check the expected behaviour of every destination group that starts a sequence, and keep a record of the import settings you choose.
A small import acceptance test
- Keep an unchanged source export and a separate working copy. Record where the list came from and retain the existing permission and suppression records.
- Prepare a handful of controlled examples with one group, multiple memberships, no group and an existing subscriber. Include accented names relevant to your audience.
- Check the current accepted file format and encoding guidance. Match each column deliberately rather than accepting a destination solely because its name looks plausible.
- Review the proposed group matches and any new names. Resolve ambiguous labels before approving the import.
- Choose the automation and empty-field options intentionally. Check resulting subscriber profiles and memberships against your mapping sheet.
- Reconcile successful, rejected and unchanged records. Investigate differences before uploading the complete audience, then retain a dated record of the accepted mapping.
Membership is not a permission record
Putting someone into a group expresses an organisational choice. It should not be treated as proof that the person asked to receive a different kind of email. Preserve the meaning of the original subscription, including relevant language and topic choices, when deciding which campaigns can use the new group.
Also decide what will keep the data accurate after the migration. If Current clients is maintained manually, name the person responsible for removing former clients. A clean import is only the start of a useful audience model. Without ownership, even a well-organised initial structure becomes misleading.
EmailTonic recommendation
Use the mapping option to preserve a small number of meaningful labels during migration or a recurring import. Do not use it to reproduce every old tag without an operating reason. The best outcome is an audience structure that the next campaign owner can understand without finding the original spreadsheet.
Before relying on it at scale, verify the exact file layout, matching behaviour and interaction with existing subscribers in your account. Measure corrections and reconciliation work rather than upload speed alone. If the source data is unclear, clean the definitions first; automatic mapping cannot decide what a reader meant to subscribe to.