HubSpot invalid email import error

HubSpot can reject a contact row with INVALID_EMAIL or INVALID_DOMAIN when the Email value is not a single valid address in name@domain.tld form.

Email also affects deduplication. Reusing the same email in more than one row can update or overwrite the same contact instead of creating separate contacts, depending on the import mode and existing records.

HubSpot expects the primary Email column to contain one primary email address. Addresses with malformed domains, repeated dots, missing top-level domains, or extra addresses in the same cell can fail validation.

• Malformed addresses can trigger INVALID_EMAIL.
• Malformed or impossible domains can trigger INVALID_DOMAIN.
• Duplicate emails may dedupe into the same contact instead of creating one contact per row.
• Multiple emails belong in HubSpot's Additional email addresses property, not mixed into the primary Email cell.

1. Trim spaces around every Email value.
2. Fix obvious malformed addresses, repeated dots, missing domains, and trailing punctuation.
3. Deduplicate rows that use the same email address unless you intentionally want to update the same contact.
4. If a contact has more than one email, keep the primary address in Email and put the others in HubSpot's Additional email addresses column using semicolon-separated values.
5. Review whether blank Email rows still have enough identity data for the import path you are using.

ReadyCSV checks the Email column for malformed email values, domain-shape risks, duplicate emails, and cells that appear to contain multiple addresses. When multiple addresses are found in Email, ReadyCSV points you toward HubSpot's Additional email addresses convention.

These checks run locally in your browser before import. ReadyCSV does not upload email addresses, contact rows, Issue Reports, or exported CSVs to a server.