Quick answer: Move the sending rules with the contact file. Keep eligible subscribers, opt-outs and unresolved records separate; verify the destination’s exclusion controls before enabling a campaign or automated journey. A successful CSV upload is only one part of a migration.
Reader fit: This guide is for a small service business moving an existing newsletter between email tools. It is a research-based operating checklist, not a completed migration test or a legal compliance assessment. The examples below are fictional; use controlled addresses for your own checks.
Disclosure: Some related buying guides linked below contain affiliate links. Read our affiliate disclosure.
Jump to: Export inventory · Status mapping · Acceptance checks · Cutover record
- Start with the people who should not receive the next campaign
- 1. Keep a dated export inventory
- 2. Map each source status to an explicit destination rule
- 3. Write the expected result before testing
- 4. Reconcile counts and changes, not just upload success
- 5. Close the gap between the first export and the first send
- Choose the tool after the migration rules are clear
Start with the people who should not receive the next campaign
During a move, the tempting question is “Did all the contacts arrive?” A more useful question is “Who is eligible for this particular message after the move?” A customer record, newsletter subscription and open quote request serve different purposes. Keep the signup promise separate from an enquiry.
A public email-marketing discussion asks whether old unsubscribes need to move to a new platform. That question inspired this checklist; comments are not evidence of how your chosen account behaves. Confirm the destination’s current instructions and test your configuration.
1. Keep a dated export inventory
Before changing forms or integrations, name the migration owner and list every route that can add or update contacts: website forms, manual CSV imports, CRM syncs and connected shops. Record scheduled sends and automated journeys separately. Decide which owner can pause each route.
Keep an untouched source export and a separate working copy. Record the source audience, export time and time zone, record count, status and filename. Store customer files in your normal restricted workspace; this checklist needs counts and record references, not a public copy of the list.
Useful detail: Mailchimp exports may put different marketing statuses in separate CSVs inside a ZIP. The status can be in the filename. Its contact export also excludes campaign open and click reports, so export reporting separately if you need a historical baseline. See the official export guide.
2. Map each source status to an explicit destination rule
The table is a proposed review structure, not a universal set of product status names. Write the actual destination field or control in your own copy. Do not turn every row into “subscribed” to make the import totals match.
On a phone, swipe the table sideways to see every column.
| Source record | Proposed handling | Evidence to check |
|---|---|---|
| Eligible newsletter subscriber | Map the permission and scope needed for the intended message. | Source, current status and destination eligibility. |
| Unsubscribed or excluded | Keep out of the intended marketing route using the supported control. | Exclusion survives import and the relevant sync. |
| Enquiry only or unclear permission | Hold outside the newsletter while the owner reviews it. | An enquiry is not silently relabeled as a subscription. |
| Conflicting duplicate records | Hold the conflict for review before enabling sends. | Which record, scope and timestamp support the final rule? |
For example, Mailchimp documents importing suppression lists as unsubscribed contacts. That is a Mailchimp-specific procedure: it is audience-specific, not global, and cannot unsubscribe existing subscribed contacts. For those, its guide points to the bulk unsubscribe tool. GetResponse describes a suppression list selected when choosing newsletter recipients, while its blocklist controls joining lists. Do not assume those controls have identical scope across newsletters, automations and integrations.
3. Write the expected result before testing
Use permitted internal test addresses that you control. Keep live campaigns and entry-triggered journeys paused during the test. Use IDs in the record below instead of customer details. These are acceptance criteria to run, not measured results or vendor guarantees.
- T01 — eligible subscriber: appears in the intended review audience; no unexpected welcome message is triggered by the import.
- T02 — opted-out contact: is excluded from that audience. Check a later update from the source integration as well.
- T03 — enquiry only: remains outside newsletter eligibility while its service request can still have a human owner.
- T04 — conflicting duplicate: is held for review; the owner records which evidence resolves the conflict.
- T05 — new opt-out during cutover: reaches the destination exclusion process before a real campaign is released.
Inspect stored status, the recipient preview and the relevant journey entry rule. A normal test email may not exercise campaign eligibility, so do not count its delivery as proof that exclusions work. If a particular path cannot be checked safely, record it as unverified and keep that path paused.
4. Reconcile counts and changes, not just upload success
Use mutually exclusive review buckets for the working file. A fictional export of 120 rows might contain 90 eligible subscribers, 20 opt-outs and 10 unresolved records. The review total is 120; the proposed campaign audience is not. If duplicates reduce the distinct record count, explain the difference instead of forcing the old total.
Separate imported, rejected, duplicate, excluded and unresolved counts. Keep the platform’s status labels alongside your review labels so the next owner can trace a discrepancy. Our CRM migration checklist covers the wider owner and cutover process.
5. Close the gap between the first export and the first send
Contacts may subscribe or opt out after the initial export. Choose either a short controlled pause or a documented way to transfer those changes; record the last processed source time. Redirect one entry route, verify its result, then enable the next. Do not leave two welcome journeys running for the same signup by accident.
Copy this handover record:
- Owner and reviewer:
- Source audience and export time zone:
- Destination audience and status mapping:
- Imported, rejected, duplicate, excluded and unresolved counts:
- Test IDs, observed results and remaining gaps:
- Last source change processed:
- Routes enabled and time enabled:
- Pause or rollback action and who can perform it:
Stop rule: If an opted-out test record becomes eligible, the counts cannot be explained, or a journey starts unexpectedly, keep affected sending paused and resolve the cause. Restoring an older export alone can lose newer opt-outs; review changes before any rollback.
Choose the tool after the migration rules are clear
If GetResponse is on your shortlist, use our subscriber-journey guide to evaluate the complete signup-to-stop route. If your current tool meets the workflow, this checklist is not a reason to replace it.
Sources checked October 22, 2026: Mailchimp export and suppression-import guidance; GetResponse suppression and blocklist guidance linked above. The inventory, review buckets, fictional example and acceptance checks are PSL editorial proposals. Retention, permission and message-type requirements need a separate review for your circumstances.
