StackEvidence Guides · Article index · StackEvidence home
StackEvidence | Independent software buyer guide | Not legal advice
Short answer: A usable email-platform export must preserve more than email addresses. You need enough data to identify who actually consented to each brand, who unsubscribed, who is pending confirmation, and which suppression rules must remain effective after a move. Exportability should be tested before a list becomes valuable.
The visible “Export CSV” button can create a false sense of safety. Imagine moving a newsletter from Provider A to Provider B and importing 900 emails labeled “contacts.” If 100 of those records had unsubscribed or never confirmed their subscription, importing everyone as subscribed creates an avoidable compliance and trust problem.
Name the contact states first
A useful migration inventory separates at least:
| State | Meaning for a migration | Safe default |
|---|---|---|
| Confirmed subscribed | Permission for the stated communications, subject to evidence | Eligible only for matching brand/purpose |
| Pending or unconfirmed | Person has not completed the required confirmation process | Do not treat as an active subscriber |
| Unsubscribed | Person opted out from the relevant stream | Preserve suppression; don't re-enable |
| Bounced or complained | Delivery/reputation problem | Preserve exclusion until properly resolved |
| Customer without marketing opt-in | Bought a product, but didn't explicitly subscribe | Keep transactional needs separate |
The system's exact labels differ across providers. Don't interpret “active contact” as universal evidence of permission.
An export drill before adopting the software
Find the provider's official documentation for exporting subscribed and unsubscribed records. For example, EmailOctopus documents exporting separate status-filtered groups and notes that its generated files are available for download for a limited time. Brevo documents exporting attributes, list IDs and subscription statuses. Those are useful capabilities to verify in your own chosen account; documentation isn't proof that every data field your workflow needs is included.
Test with harmless synthetic addresses or an approved internal test list, not with unrelated people's data. Compare the exported columns with the fields you planned to store. If confirmation timestamp, source form or explicit preference isn't available, decide before launch how that evidence would be retained.
The six questions to ask any provider
- Can I export all contacts with their current subscription status? Distinguish export access from a marketing report of clicks.
- Can I export suppression history? A bounced or unsubscribed address must not silently become marketable because the new platform lacks a flag.
- Can I identify the original brand and consent purpose? One person may subscribe to Brand A but never agree to Brand B emails.
- Can I export tags, segments and custom fields? If not, how will I reconstruct useful preferences without guessing?
- How are duplicates counted and merged? One email appearing on two lists can represent two distinct subscriptions, not permission to blend them.
- Can I remove or delete data when appropriately requested? Evaluate the provider's privacy operations and your own retention policy before collecting information.
A fictional two-brand migration
A publisher operates a software-research newsletter and a separate direct-response education brand. The same person subscribes to the research newsletter but unsubscribes from the marketing education series. During a migration, both records happen to share an email address. A naive deduplication that keeps a single “subscribed = yes” value could defeat the person's preference. The correct approach is to preserve separate purpose-specific records or preferences, and send only the streams the person legitimately requested.
The lesson is not necessarily “buy two accounts.” The lesson is prove brand and purpose isolation in the exact account architecture chosen. A single provider account may work, but don't make its list screens stand in for tested consent behavior.
Migration day is not the first time to test
Before exporting a real list, document:
- Export operator and authorization.
- Each brand's list name and promise.
- Timestamp and origin of active consent where available.
- Status mapping from old to new provider.
- Global and brand-specific suppression handling.
- Sender domain and authentication checks.
- Exact welcome workflow to start after import—and whether existing subscribers should enter at all.
- A rollback plan that avoids duplicate sends.
An existing subscriber who has already received a welcome series should not be dropped into its first message again simply because the software changed. New contacts should only receive promised material when their status is verified.
Keep transactional delivery out of the import mistake
For a digital product, order receipt, course access and purchase support can be separate from a newsletter. In a migration, a paid customer needs continued access to what they bought regardless of whether they joined a mailing list. Confirm the course platform and checkout stay operational during any marketing-list move.
The portable-list test card
Take a sample export and answer: “Can I show, for each sample record, the brand, the permission purpose, the current subscribe status, the suppression status, and whether a welcome automation has already run?” If you cannot, you have discovered a portability risk before your audience grows. That is useful evidence when choosing software.
Related next step: Pair this export test with StackEvidence's email-plan cost worksheet. A cheap plan that loses consent and suppression data can be expensive to correct later.
Sources and scope: EmailOctopus export instructions; Brevo export instructions; Brevo blocklist handling. This is a business operations guide, not a claim that a specific provider currently has every field listed.
Published by StackEvidence. Contact the publisher · Privacy · Editorial standards. Documentation-based education, not individualized legal advice or a claim of hands-on vendor testing. Hosted on BlogBaser.