Transfer newsletter exclusions without reactivating recipients

Move the reasons not to send before approving the new newsletter audience. Keep unsubscribes, complaints, bounce records and unresolved permission questions out of the candidate recipient list. An address marked active in one export does not settle a conflict with another record.

This is a data-reconciliation procedure for an existing newsletter, not a recommendation to change platforms or a legal assessment. The worked example is fictional. The proposed checks do not require sending a campaign, contacting excluded people or treating a migration as fresh consent.

Decide exactly which communication is moving

Name the newsletter, sending account, source account and destination owner. Record whether an exclusion concerns that newsletter, email marketing generally or another communication category. Preserve the original scope even when you conservatively hold an ambiguous address out of this migration.

Choose a snapshot time and a final cutoff time. Pause the newsletter's scheduled sends and relevant automations during reconciliation, while maintaining a monitored route for new opt-outs. Identify signup forms, integrations and manual imports that can change the audience. A second person must own the procedure when the usual sender is absent.

Keep the existing platform if the team cannot identify these entry points or maintain exclusions reliably. Retaining its working audience controls may be worth more than a smaller invoice.

Export status deliberately

In MailerLite, only account administrators can export subscribers. The export page supports selections for active, unconfirmed, unsubscribed, bounced and spam-complaint records; exported fields depend on the columns displayed. Include group membership deliberately if needed. This documentation directs Classic users to a separate help centre. MailerLite export boundaries.

Have the administrator save each relevant status selection with its count, selected columns and extraction time. Keep an unchanged copy. A file of active subscribers alone leaves the central task unfinished. If a needed event time or reason is absent, inspect the available source record and record the gap; do not invent a timestamp.

In Brevo, contact CSV exports let you select subscription statuses separately from contact attributes and list IDs. EMAIL, LAST CHANGED and CREATION DATE are selected by default. Clear unintended filters when exporting the full population. Brevo export settings.

Brevo provides separate views for email-campaign and transactional unsubscriptions. Its campaign blocklist can be filtered by reason, while transactional email blocks have their own view and sender information. Unsubscribe views, blocklist scope.

Preserve those distinctions. A campaign export should not be described as a complete transactional suppression history. Nor should a transactional status be interpreted as permission for marketing.

Build one exclusion register and a separate candidate list

For each address, retain the source identifier, source status, reason, communication scope, event time and timezone, extraction time, evidence location and reconciliation decision. Keep raw values alongside any normalised comparison fields. Trim accidental surrounding spaces, but do not merge different addresses merely because names match or remove dots and plus tags by assumption.

Use three outcomes: excluded, held for review, or candidate. In this proposed procedure, an unresolved unsubscribe, complaint or bounce conflict keeps an address out. Missing evidence goes to review. Candidate means the records support further approval for this newsletter; it is not a declaration of consent created by the spreadsheet.

Event time matters more than which file arrived last. A profile's last-changed time could describe an unrelated edit. A newly imported active record does not, by itself, reverse a previous exclusion. Any genuine later request to resume needs its own evidence and human review outside this transfer exercise.

A fictional reconciliation, including a late opt-out

Every address and event below is invented, using example.com. Nothing should be sent to these addresses. The first snapshot is 2026-10-20 at 12:00 UTC; the final cutoff is 2026-10-21 at 12:00 UTC. All event times below are UTC.

Address	Conflicting or relevant records	Final decision for this newsletter
ada@example.com	Active on Oct 18; newsletter unsubscribe on Oct 19 at 09:00	Exclude; keep the unsubscribe evidence
ben@example.com	Hard bounce on Oct 17 at 14:00; active row imported Oct 20 at 08:00	Exclude; import time does not resolve the bounce
chen@example.com	Active on Oct 18; spam complaint on Oct 19 at 16:00	Exclude; preserve the complaint reason
dev@example.com	Active with reviewed newsletter permission at snapshot; opt-out arrives Oct 21 at 10:00	Remove from candidates during the final change check
eli@example.com	Active with reviewed newsletter permission; no conflicting record through cutoff	Candidate for human approval
fay@example.com	Active in one file, unconfirmed in another; event times unavailable	Hold; do not choose a winner by row order

At the snapshot there are three excluded addresses, one held address and two candidates. The late opt-out changes the final tally to six unique addresses = four excluded + one held + one candidate. The underlying export row count can be higher because one address can have multiple records. Reconcile unique addresses as well as raw rows.

This conservative table is our proposed handling rule, not a claim about automatic vendor conflict resolution. Keep all original reasons even if the destination has only one suppression status.

Apply the result within the destination's actual scope

Brevo: its blocklist import has explicit campaign-channel options. Every contact in an import file receives the selected channel exclusions, so separate files are needed for different scopes. After import, inspect the report and channel-specific blocklist indicators. Brevo blocklist import.

MailerLite: its ordinary import documentation says existing unsubscribed, bounced, unconfirmed or complaint records can fail to import. It also offers an option to trigger group-linked automations during import. That protection for records already in the account does not establish that an arbitrary source CSV will install every external exclusion correctly. Keep automation triggering off during a controlled import rehearsal and verify the intended status-preservation route before loading real records. MailerLite import behaviour.

Gmail mail merge: Google supplies unsubscribe notifications but no complete list of unsubscribed recipients. Opt-outs apply to that sender's mail merge; ordinary messages and other sending accounts remain outside that suppression. Recipients within the sender's organisation cannot unsubscribe through this mechanism. Google's documented scope.

For Gmail, keep the exclusion register outside the candidate recipient sheet and reconcile every planned audience against it. Do not assume a contact CSV installs exclusions in Gmail. A sender change needs the same check. If previous Gmail activity left an incomplete opt-out history, retain the current newsletter arrangement until that history is resolved; notifications collected only from today do not establish the past.

Rehearse without a live send, then capture the delta

Use a separate worksheet with the fictional rows to check deduplication, scope and totals. Have the backup owner reproduce the final result without your help. For an account-level rehearsal, use only approved test contacts under your team's control, with sending and automation disabled. Verify statuses through the destination interface or a supported report; a successful upload is insufficient.

Immediately before approving the real candidate list, collect changes since the snapshot from every monitored source, including direct opt-out requests. Preserve their timestamps and reconcile them again. Brevo's old daily-export feature was discontinued, so do not assume a legacy export integration is supplying this delta. Brevo's daily-export notice.

Fail the transfer if an excluded or held address appears in the candidate list, a channel mapping is unclear, counts cannot be explained or the backup owner cannot repeat the reconciliation. No send is needed to detect those failures.

Roll back without restoring stale eligibility

Keep the source account and restricted evidence archive accessible through acceptance. If the destination fails, suspend the new process and reconcile every exclusion received during the pilot back into the retained source before resuming there. Never restore the old active list alone. Keep the failed import report, final register and delta log so the next attempt starts from current evidence.

Assign continuing ownership and an appropriate retention policy for the exclusion register. The archive needs enough evidence to explain a decision without becoming an unrestricted copy of every contact attribute.

For the same billing period, calculate current newsletter-platform charge − remaining same-platform charge − incremental replacement costs. Include temporary overlap once and record reconciliation labour separately. An unchanged Workspace bill is not an additional migration cost. Use the subscription audit after the exclusion process passes, not as a reason to rush it.