The Black Friday sale: $100 off Mimeo. Buy now →
Docs menu CSV import

CSV import

Bring in a list from anywhere. Mimeo takes any CSV with a header row — there's no required column order and no required template, because you do the mapping.

Mapping columns

After you upload, Mimeo shows every column in your file and asks what each one is. Your choices per column:

Map to Behavior
A core field Email, first name, last name, or subscribed on. Email is the match key — it's lowercased, and an existing person with that address is updated rather than duplicated.
Subscribed on The date the person joined the list — map your old tool's subscribe-date column here. Only an earlier date replaces what Mimeo already has, so re-running an import is safe and the order you import batches in doesn't change the result. A cell Mimeo can't read as a date leaves the stored date alone rather than failing the row.
A custom field Any field you've declared under People → Fields. If the field doesn't exist yet, you can create it right here during mapping.
Tags The cell's value becomes one or more tags. Multi-value cells are split on |, ,, and ;, so customer, pro; beta becomes three tags.
Already unsubscribed Marks the person as suppressed. Recognized markers are true, 1, yes, y, t, x, and unsubscribed (case-insensitive), or a parseable timestamp. A timestamp is preserved as the unsubscribe date. Normalize other status labels before importing.
Skip Ignore this column entirely.

Historical imports and automations

Applying a tag emits an event, and events can start flows. The checkbox Treat this import as history, so it triggers nothing is on by default. Import-generated events are marked historical, and flows ignore them by default.

The exception matters: a flow can opt into historical events, when Don't start this flow on events marked historical is unticked in its entry rules. Review relevant flows and the scheduled queue before importing, and pause or cancel anything that must not run during the migration. Historical mode does not cancel existing scheduled sends.

Turn historical mode off only when you intend to trigger live automations, such as a small batch of genuinely new signups entering a welcome flow. Test a small batch first.

An import your agent runs makes the same choice, and also treats the import as history by default. See backfilling without sending mail for what "historical" means everywhere else.

Import posture: fill or overwrite

For people who already exist, you choose how the incoming data is applied:

  • Fill blank fields only — existing values are left alone; the import only writes where Mimeo currently has nothing. This is the safe default for merging a supplementary list.
  • Overwrite — incoming values replace what's there. Use this when the CSV is the authority, like a fresh export from the system that owns that data.

The posture applies to field values. Tags are additive either way — an import never strips tags a person already has.

Static tags

Separate from any tag column, you can apply a set of tags to every row in the import. This is how you keep provenance: tagging an import from-mailchimp-2026-07 means you can always find, filter, and if necessary undo that batch later.

Importing as already unsubscribed

Enable Import everyone as already unsubscribed to suppress the entire file, regardless of column mapping. CSV imports do not resubscribe people who are already suppressed.

This is the one to reach for when migrating off another platform. Export your old tool's suppression list, import it with this on, and those addresses arrive in Mimeo already opted out. Do this before importing your active list, and nobody who unsubscribed from your old tool gets mail from your new one. See it tested with Mailchimp and Kit exports.

Preview before you commit

Choose Save mapping to refresh the preview. Check the names, fields, and tag splitting before choosing Start import. For suppression data, verify the whole-file switch or normalized markers, then inspect sample person records after a small import before processing the full file. The migration guide covers the order of operations.

The import report

After the import runs you get a report with:

  • Created — new people added.
  • Updated — existing people matched by email and modified.
  • Skipped — rows that couldn't be imported, most commonly a missing or malformed email address.
  • Row errors — the line-by-line account of each skipped row and why.

Row errors are per-row, not fatal: a handful of bad addresses doesn't stop the rest of the file from importing. Fix those rows in a small follow-up CSV rather than re-running the whole thing.

Importing with your agent

The same import — upload, mapping, posture, preview, commit — is available end to end through the Imports API, and your manager repo ships an import-a-csv skill that walks an agent through it: it reads the file, proposes the mapping, asks the questions above, and commits only after you confirm.

View as Markdown

Powerful email automation you fully control.

Buy now