Mailchimp CSV Normalizer
Mailchimp audience exports can use 'Email Address' or a merge-field code like 'EMAIL', 'First Name' or 'FNAME', and the TAGS column mixes comma- and semicolon-separated tag lists depending on how they were entered. This tool auto-detects those variants and remaps everything onto one stable schema (Email, FirstName, LastName, Tags), normalizing tag lists into a consistent comma-separated, de-duplicated format and lower-casing email addresses. Unrecognized merge-field columns stay visible with a dropdown so you can map them manually. Everything runs locally in your browser; your subscriber list is never uploaded.
Reviewed by Vincenzo Manto, Founder & Lead Developer · Last updated September 27, 2026
How it works
- 1
Paste your Mailchimp audience/subscriber CSV export, or upload the .csv file.
- 2
Review the auto-detected column mapping; each source column is matched to a target field like Email, FirstName, or Tags.
- 3
Override any guess with the dropdown, including merge-field columns the tool didn't recognize (map them to a field or leave as 'ignore').
- 4
Copy or download the normalized CSV with clean headers and consistently formatted tag lists.
Why Mailchimp exports don't line up
Mailchimp lets each audience have its own set of merge fields, and different export flows (audience export, group export, API-based CSV downloads) surface either the display label or the internal merge-tag code as the column header. Combine that with inconsistent tag formatting from manual tagging versus automation rules, and two exports from the same audience can look quite different.
One schema for every export
This tool auto-matches known Mailchimp header variants to a fixed schema (Email, FirstName, LastName, Tags), cleans up tag list formatting, and normalizes email casing, so exports taken months apart or from different audiences land in the exact same shape for import elsewhere.
Frequently asked questions
Why does my Mailchimp export use codes like EMAIL or FNAME instead of readable names?
Mailchimp's merge-field system uses short internal codes (EMAIL, FNAME, LNAME) that sometimes appear as column headers instead of the friendlier 'Email Address', 'First Name', 'Last Name' labels shown in the audience dashboard. This tool recognizes both forms.
How does it handle the TAGS column?
Mailchimp tag lists can be comma- or semicolon-separated depending on how subscribers were tagged. This tool splits on either delimiter, trims whitespace, removes case-insensitive duplicates, and rejoins the tags with a consistent ', ' separator.
What happens to columns it doesn't recognize?
They stay listed in the mapping table with a dropdown defaulted to 'ignore'. You can manually assign any custom merge field (like a birthday or company field) to one of the target columns if needed.
Is my subscriber list uploaded anywhere?
No. Parsing and remapping happen entirely in your browser using JavaScript. Your CSV never leaves your device.
Does it change the case of email addresses?
Yes, output emails are lower-cased and trimmed for consistency, which also makes de-duplication easier in a spreadsheet afterward.