HubSpot import missing required fields

For HubSpot Contacts, a row needs at least one of First name, Last name, or Email. If all three are blank, HubSpot does not have enough contact identity data to create or match the contact.

A row with a name but no Email can still represent a contact, but Email is the safer matching and dedupe key for contact imports and updates.

HubSpot needs a contact identifier. A row with no First name, Last name, or Email is effectively an empty contact identity, even if other fields such as Company, Phone, or Lifecycle Stage are present.

Name-only rows can be valid for some create flows, but they are riskier for updates and duplicate-safe imports because the Email key is missing.

1. Find rows where First name, Last name, and Email are all blank.
2. Add at least one real identity value, or remove rows that do not represent contacts.
3. Prefer adding a valid Email when you need duplicate matching or updates to existing contacts.
4. Review name-only rows before import so you understand how HubSpot will create or match them.
5. Do not fill missing identity fields with placeholders just to pass validation.

ReadyCSV flags rows where Email, First name, and Last name are all blank as missing_identity critical blockers. Those rows need source review before export.

ReadyCSV also warns with email_recommended_for_dedup when Email is blank but a First name or Last name is present. That warning means HubSpot may still create the contact, but Email is recommended for matching, updates, and duplicate-safe imports.

These checks run locally in your browser. ReadyCSV does not upload contact rows, names, emails, Issue Reports, or exported CSVs to a server.