Inventory and preserve subscriber states and evidence first; test restrictions, existing-record handling and sending paths in the destination before moving the audience, and reconcile new opt-outs before either cutover or rollback.
Move the restrictions as carefully as the active audience. A newsletter migration should preserve who may receive it, who must not, why that decision was made and how future signups and opt-outs will work. Importing every address as a new subscriber can undo the most important part of the old list.
This walkthrough uses MailerLite to Brevo as a concrete direction, based on their current documentation. The sequence is an editorial migration plan, not a live migration we performed. We have not exported contacts, configured accounts or sent messages for this article. Other destinations need their own verified status mapping; a reversed CSV is not a complete reverse procedure.
1. Decide what must move before choosing the import button
Inventory the source and any existing destination audience, not just the subscriber total. Record the account version, responsible administrator, lists/groups, custom fields, status definitions, confirmation history, forms, integrations, scheduled campaigns and automations. Include people currently queued in a sequence and messages already sent to them.
Separate three things: historical evidence of the subscription, the current permission/preferences for this newsletter, and the platform’s technical sending status. A creation date can be the date a record was imported; it is not automatically the date that person agreed to receive your newsletter.
| Source or destination record | Migration treatment | Release check |
|---|---|---|
| Active with suitable subscription evidence | Candidate for the intended newsletter, after checking the other system’s restrictions | Correct topic, fields, preference and destination status |
| Unsubscribed | Preserve the applicable no-send restriction and its history | Excluded from newsletter recipients and welcome sequences |
| Bounced or complaint | Preserve the reason and applicable suppression; keep hard/soft distinctions where available | Do not turn a restricted record into an active subscriber |
| Unconfirmed or evidence missing | Hold outside the eligible audience until an appropriate, documented resolution | No campaign or automatic confirmation blast triggered by migration |
| Conflicting records across systems | Exclude from sending while the current preference and evidence are reconciled | The migration does not silently override a restriction in either system |
A CSV does not create permission. Preserve the original signup/confirmation time and timezone where available, source/form, promised topic and a reference to the notice or wording shown. Keep event evidence that is not included in the contact export in appropriate restricted storage. Do not fill missing consent dates with the migration date. MailerLite’s permission policy is one relevant acceptance rule; assess the actual destination policy and applicable audience requirements separately.
2. Export MailerLite states and fields deliberately
MailerLite’s export guide requires an account administrator and lets you select active, unconfirmed, unsubscribed, bounced and spam-complaint records. Export each relevant state or a clearly identified complete selection. Check whether Select all means the current page or the entire filtered list.
Set the required visible columns before exporting: only those columns/fields are included. Select Groups if group membership matters. Inspect the resulting files, not just the export-success notice. Preserve an unchanged original plus a separate working copy, with export time, filters, columns and row counts recorded. Classic users need the Classic documentation rather than assuming the same controls.
Before merging files, map the source identity, status, channel, group membership, original dates and evidence reference. Check delimiters, encoding, date formats, blank values and repeated addresses. Do not merge different people because names look similar, discard conflicting statuses or let a spreadsheet silently rewrite dates. Keep unnecessary personal data out of the migration copy and apply your actual access and retention policy.
If Brevo already contains contacts, export its existing records too. Select the needed attributes, subscription states and List ID. Confirm filters and full-list selection. Preserve its existing exclusions and more recent preference changes rather than treating the MailerLite file as universally authoritative.
3. Build separate restriction and eligible-recipient files
For this move, make the eligible newsletter file from records supported by the intended subscription evidence, then exclude applicable restrictions from either system. If current records conflict, do not send until they are resolved. This is a conservative release rule for the migration, not a claim about an automatic precedence algorithm in either product.
Keep a restriction file with the address, relevant channel and original reason/date or evidence reference. A contact field labelled “unsubscribed” is useful history but is not the same as the destination’s actual blocklist setting. Do not send a bulk “please confirm again” message to opted-out or complaint records as a migration shortcut.
Brevo’s blocklisted-import procedure requires explicit channel options. Put only records with the same channel restrictions in each file: the chosen restrictions apply to every contact in that import. In the email-newsletter file, select the email-campaign restriction. Do not accidentally block unrelated SMS, WhatsApp or essential transactional services by treating every channel as interchangeable.
Brevo treats resubscription as a separate operation. Do not use it to undo a valid opt-out simply because the new account contains fewer active contacts. If a person later makes a genuine new subscription request, handle that through the documented process and keep its evidence separate from the migration.
4. Prevent accidental workflow entry and replay
Keep new destination workflows inactive while mapping and importing. For existing workflows in either account, record queued contacts, last completed steps, pending delays and scheduled messages before changing status. Decide whether each person should finish in the old service, resume at an appropriate new step or enter no sequence. Recreating a welcome workflow does not justify welcoming the entire old audience again.
Brevo’s new editor distinguishes Paused from Inactive: Paused prevents new entry while active contacts continue; Inactive also removes active contacts. Therefore pause alone is insufficient when the goal is to stop all affected workflow sending. Record the queue before an authorized stop and plan how legitimate pending work will be handled.
Review re-entry, restart and exit conditions, and the actual Brevo triggers connected to destination lists. List addition can be an event; list movement and other triggers have different behavior. An import does not transfer a subscriber’s old workflow position.
MailerLite also has a consequential import option for triggering group-associated automations. Its manual workflow enrollment can bypass original trigger checks. These controls matter during a rehearsal, correction or rollback. Never resolve missing history by bulk-adding everyone to the start.
5. Rehearse Brevo import and existing-contact handling
Use a small, clearly separated test list containing only addresses you control. Model a new eligible contact, an existing contact with newer data, an already restricted contact and a duplicate appearing in conflicting source groups. You can set controlled records to unsubscribed/blocklisted for the test; do not send to invented addresses or generate real spam complaints or bounces to manufacture a test.
Follow Brevo’s import workflow to map fields and lists, then inspect the final options. Update the attributes of the existing contacts controls overwriting existing data. Import empty fields to erase existing attribute data is a different control that can remove existing values. Leave erasure off unless each deletion is intentional; choose updates only for fields whose incoming value should replace the current value.
For the rehearsal, import the controlled restrictions using the actual email-campaign blocklist option, then import the separately eligible file. Confirm status after both operations. A historical permission field must remain historical metadata; do not map it to a new native confirmation event or assume a custom field blocks sending.
Read the import reports and reconcile new, updated, unchanged, rejected and duplicate records. Stop if a restricted contact becomes eligible, a field disappears, counts cannot be explained or an automation unexpectedly starts. A successful upload alone is not acceptance.
If the destination is MailerLite instead, its documented existing-account status guards reject some already unsubscribed, bounced, unconfirmed or complaint records. Those guards do not automatically know another provider’s history. Verify and implement that destination’s supported suppression process before any audience import; this article’s Brevo procedure must not be copied in reverse.
6. Rebuild the signup, preferences and sending identity
A contact export does not transfer forms, templates, automations, webhooks, campaign histories or their operating settings. Rebuild only the journeys you need and retain required historical evidence separately. Inventory embedded website forms, landing pages, plugins, shop integrations and links in older emails so signups and opt-outs do not continue unnoticed in the old account.
For new Brevo signups, configure the chosen confirmation path and inspect its event and transactional logs. Form submission and final confirmation are different events. Imported historical dates do not become native Brevo confirmation logs. Test a fresh controlled signup, its consent wording, destination status, group/list and any welcome sequence before replacing the live form.
Follow Brevo’s current domain-authentication instructions using the account-specific verification and DKIM records. Review the existing DMARC policy: an automatic setup may offer to replace it. Preserve other legitimate senders and receiving-mail MX; do not paste a generic authentication example over working DNS. Use our sender-inventory and authentication guide to coordinate the change.
7. Check the whole path before the first audience campaign
Use Brevo’s preview and test controls for layout, links and personalization, with their stated limits. Then use a deliberately scoped regular campaign to your own eligible test recipients to exercise the actual unsubscribe path. Review the real campaign recipient selection and exclusions immediately before sending; a test-list name alone does not prevent a broad selection.
| Check | Expected evidence before release |
|---|---|
| Restricted test contact | Correct channel blocklist after all imports; absent from eligible campaign recipients |
| Existing contact and blank fields | Only intended values changed; retained data and historical dates remain correct |
| Fresh signup | Chosen confirmation completes, correct record appears and only the intended workflow starts |
| Actual opt-out | Unsubscribe updates the controlled contact’s status and excludes it from a subsequent recipient selection |
| Message and reply path | Expected sender, reply inbox, links, readable mobile content and documented authentication result |
| Queued sequences | No unintended replay, duplicate welcome or messages from the retired sender |
Do not test exclusion by deliberately sending another campaign to someone who opted out. Inspect their status and the next campaign’s recipient selection instead. One received message does not establish general inbox placement or future deliverability. Our first-newsletter walkthrough helps distinguish a preview from a complete subscriber journey.
8. Reconcile the final delta, then cut over
Agree a cutover time and who controls sending in each system. Stop scheduled or automated newsletter sends through the appropriate documented controls, after recording queues. Export the final delta: new signups, confirmations, address changes, opt-outs, bounces and complaints since the first snapshot. Reapply restrictions and reconcile eligible records before the first audience send.
Switch the approved forms and integrations, test them again, and ensure only the intended platform sends that newsletter. Keep monitoring older email unsubscribe links and old form submissions while they can still create changes. Record how those changes reach the current restriction record; do not assume replacing the website form updates links already in inboxes.
Cancellation and rollback need the newest restrictions
Keep the old service available until exports, history, required links, integrations, queue handling and destination verification are accepted. Check the actual cancellation date, retained access and data/deletion terms before cancelling. Do not cancel while an old opt-out path is still needed without a working continuity arrangement.
If you roll back, stop affected destination sends and capture new opt-outs, signups and delivered workflow steps first. Update the old service’s exclusions and eligible audience before resuming; an original export would lose changes made after cutover. Avoid replaying messages already delivered. Rollback cannot unsend an email, recreate missing permission evidence or justify resubscribing people who left.
Keep a private migration record
Copy these deliberately unfilled fields into a private handover. This is a template, not a migration we observed. Store contact files and evidence under restricted access; the handover should reference their private location rather than reproduce the audience.
- Source/destination, account version and authorized owner: [service references; responsible person]
- Snapshots and selection: [time/timezone; states; filters; fields; private file references]
- Mapping and conflicts: [status/channel/group rules; excluded or unresolved records]
- Rehearsal and import results: [controlled cases; reports; observed outcomes; remaining limits]
- Cutover and final delta: [sending owner; changes reconciled; forms/links checked]
- Rollback/cancellation gate: [latest restrictions; delivered steps; required retained access; decision owner]
Choose a destination only for a documented improvement
You can stay with your existing service if it already meets the newsletter’s needs. If migration is justified, obtain matched quotes for the eligible audience, stored restricted records, sends, required workflows, seats and export access. The cheaper headline may omit a capability you need to operate the list responsibly.
Use MailerLite versus Brevo and MailerLite Free versus paid for the separate capacity and product decision. If you actually need to move a normal mailbox, start with email hosting versus newsletter software: this subscriber procedure does not transfer inbox messages or change receiving-mail delivery.
Sources and verification
Editorial review 2026-10-10. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- MailerLite: Export subscribersChecked Account administrators can export selectable subscriber states; only selected visible columns/fields are exported and Groups must be explicitly included.
Limits: A subscriber CSV is not proof that every permission event, automation position, template or campaign report was exported; Classic has separate documentation. - MailerLite: Import subscribersChecked Import settings map fields and groups and offer automation triggering; addresses already unsubscribed, bounced, unconfirmed or spam-complaint in that account may fail to import.
Limits: Existing-account guards do not automatically import another provider’s historical exclusions; no live import or full bidirectional migration was tested. - MailerLite: Add existing subscribers to a workflowChecked Manual enrollment can bypass original trigger checks; enabling workflows and choosing existing subscribers can replay entry at selected steps.
Limits: A migration must deliberately decide which contacts, if any, enter; this article does not instruct bulk reenrollment. - MailerLite: Anti-Spam PolicyChecked MailerLite requires provable permission for the relevant email topic and honoring unsubscribes; list possession alone is insufficient.
Limits: Provider acceptance policy is not a complete legal assessment for every location or audience; no legal compliance is certified. - Brevo: Import a list of blocklisted contactsChecked Blocklisting requires explicit import options; one file applies the chosen channels to every contact, so differing channel restrictions need separate files.
Limits: An ordinary field value named unsubscribed is not presented as a substitute for the platform’s actual channel blocklist state. - Brevo: Import contactsChecked Imports map attributes and lists; updating existing contacts and erasing data with empty fields are separate options; the import report identifies added, changed, unchanged and erroneous records.
Limits: No live account import, automatic status precedence, consent validation or feature availability was exercised; review the intended import options and actual result. - Brevo: Blocklist, unblock or resubscribe contactsChecked Subscription restrictions are channel-specific; resubscription is a separate contact-level operation and must not override an explicit opt-out.
Limits: Do not use this vendor’s legal wording as a universal legal conclusion or import negative states as fresh permission. - Brevo: Export contactsChecked Export can include selected contact attributes, List ID and subscription states; selecting all contacts differs from selecting a page, filter or segment.
Limits: The exported creation/modification date is not automatically the original consent timestamp; select the required data and inspect the result. - Brevo: New automation editor overviewChecked Paused stops new entry while active contacts continue; Inactive stops entry and removes active contacts.
Limits: Stopping an existing workflow changes its queue; document positions and choose the appropriate procedure rather than assuming pause stops all sends. - Brevo: Automation entry, exit and restart conditionsChecked Re-entry after exit, waiting, exit conditions and restart conditions are separately configurable.
Limits: Preserve relevant exclusions and past journey position; copying a list does not transfer automation history or justify re-entry. - Brevo: Automation triggers, actions and rulesChecked List additions can be entry events; list moves and other triggers behave differently.
Limits: Do not infer that every import enters every workflow or that a disabled entry removes existing queued work. - Brevo: Authenticate a domainChecked Use the account’s Brevo verification and DKIM records and review the existing DMARC policy; automatic setup can offer to replace DMARC.
Limits: The rollout includes different setup flows. Existing legitimate senders and mailbox MX must be preserved; authentication is not an inbox-placement guarantee. - Brevo: Double opt-in and signup logsChecked New double-confirmation forms and external-form workflows differ; event and transactional logs capture distinct parts of that provider’s confirmation journey.
Limits: Imported historical fields do not become native Brevo confirmation events; provider advice does not certify legal compliance or promise engagement. - Brevo: Preview and test emailChecked Preview/test methods inspect content and delivery to controlled addresses and have plan-specific limitations.
Limits: An editor test is not evidence that a subscriber’s actual unsubscribe and campaign exclusion path works or that all recipients will reach an inbox. - Brevo: Create and send an email campaignChecked Recipients, exclusions, sender and unsubscribe settings require deliberate review before scheduling; blocklisted contacts are excluded from campaign recipients.
Limits: One observed controlled send would not prove universal delivery or legal eligibility; no campaign was sent for this guide.