Import Builder/Guides/Email list import errors
Marketing

Email List CSV Import Errors

A list from an event, a partner or an old email tool rarely imports cleanly. Mailchimp, Klaviyo and Brevo each skip, merge or rewrite certain rows, and tell you only afterwards. Here's what each one expects, the errors you'll meet, and the fix for each.

What each platform needs

Mailchimp

A CSV or TXT file, separated by commas, not semicolons; Excel (.xls) files aren't accepted. Files over 200 MB, or about a million contacts, can cause errors. Every row needs an email address, or a phone number for SMS contacts.

Klaviyo

A CSV of up to 50 MB with a header row, imported into a list. Every row needs an email address or a phone number.

Brevo

A CSV, XLSX or TXT file of up to 250 MB with one sheet, separated by commas, semicolons or tabs, saved as UTF-8 or Windows-1252. Every contact needs an email, an SMS, WhatsApp or landline number, or an external ID.

Errors, and the fix

Email addresses are rejected

All three refuse incomplete or malformed addresses. Klaviyo rejects any containing ( ) , : ; [ / ] or spaces, Brevo doesn't accept special characters, and Mailchimp can't read accented characters before the @. Mailchimp also removes addresses with misspelled common domains, so check for spaces and typos such as gmial.com.

info@ and sales@ addresses disappear

Mailchimp removes role-based addresses from imports automatically. Ask for a named person's address instead.

Contacts are missing or merged

Klaviyo skips later rows that repeat an email or phone number. Mailchimp imports a repeated email once and lets later rows update it. Brevo allows one contact per email. Remove duplicates first, so you choose which row's details survive. CSV duplicate rows guide.

Phone numbers land in the wrong country

Start them with + and the country code. Mailchimp's SMS numbers must be in E.164 format (+ then up to 15 digits), Klaviyo needs the country code, and Brevo applies your default country code to numbers without a +. Excel tends to drop the +: Brevo suggests typing an apostrophe before it. CSV phone numbers guide.

Tags are split in the wrong places

Mailchimp reads one Tags column, with tags separated by commas. A tag that contains a comma needs double quotes ("Monday, Wednesday"), tags are limited to 100 characters, and emoji can't be imported. Brevo's multiple-choice attributes look like ['Music'|'Sports'] instead.

Dates and birthdays are wrong

Mailchimp reads YYYY-MM-DD or MM-DD-YYYY for dates, and month and day only (MM/DD or DD-MM) in a birthday field. Brevo's date attributes follow your account's setting, DD-MM-YYYY or MM-DD-YYYY. Year first avoids most mix-ups. CSV date formatting guide.

Accents turn into � or go missing

The file wasn't saved as UTF-8. Brevo skips any value containing the replacement character �. Save as CSV UTF-8 from Excel, or download as CSV from Google Sheets. CSV special characters guide.

Existing details are wiped

When Mailchimp updates existing contacts, blank fields in your file erase what's stored. Brevo only erases data with blanks if you turn on that option. Leave out columns you don't mean to change.

Before you import

Saved as CSV UTF-8, separated by commas
One email per row, with no spaces, typos or stray characters
Named people's addresses rather than info@ or sales@
Duplicates removed, keeping the row with the best details
Phone numbers with + and the country code
Tags and multiple choices written the way the platform reads them
Dates in one format, birthdays as month and day
One file per consent status for Mailchimp, and permission for everyone marked subscribed
Columns you don't want to change left out when updating existing contacts

Collect the list in the right format

Send whoever has the contacts a form instead of a spreadsheet. Emails, phone numbers, duplicates and consent values are checked as they type, and the download is ready to import. Data is checked in the browser and never stored by us.