# Subscriber export checklist

Preparation checklist · no native provider export executed

## Capture the context

- Provider, exact account plan, publication and export date.
- Selected audience/filter and expected record count.
- Documented source URL and the date you read it.
- Whether the export is an account UI action, public documentation or API output. Do not merge those evidence types.

## Inspect a separately authorised native export

- Count rows and compare the selected audience, rather than assuming every contact was exported.
- Preserve email identity, display name, status, tags and any required custom fields.
- Distinguish confirmed, pending and unsubscribed people. Never map every row to active.
- Check dates and time zones. A creation timestamp may not be the permission record you need.
- Check UTF-8 characters, quoted commas and multiline fields.
- Record paid tier and access expiry separately from email subscription state where relevant.
- Document missing consent/history fields as missing; do not infer them from the presence of an email address.
- Check content exports separately from subscriber exports.
- Keep payment customer/subscription identifiers and any provider migration steps separate from a contact CSV.
- Store exports privately; never publish real subscribers as test evidence.

## Documentation observations, read 9 October 2026

- beehiiv: the Quick and Full subscriber exports are distinct; Full adds custom fields/statistics. The subscriber export API requires separate enablement. https://www.beehiiv.com/support/article/12258595483543
- Kit: select the intended subscriber status and the account-wide selection. Its guide describes status, tags and custom fields among export fields, and says download links expire after five days. https://help.kit.com/en/articles/2502489-how-to-export-subscribers-in-kit
- Buttondown: its subscriber CSV documentation covers tags and custom metadata. Inspect the actual selected file; content Markdown and media backup are separate scopes. https://docs.buttondown.com/data-exports-subscriber

The included CSV is a locally generated schema-inspection fixture, not any provider's native export. Its local_state and synthetic_tier fields are invented labels for this exercise, not guaranteed import fields or valid subscription/permission records.