Check a contacts-only quick-import file for headers, identifiers, duplicate records, property formats, tier limits, and workbook shape before a small test.
A HubSpot contact CSV preflight checks local file evidence before import. This private workspace masks contact values, requires explicit property types, and blocks contact-data exports until structural and identity blockers are resolved.
A contact row is only safe when file structure, identity, and destination property expectations agree. The complete file is checked locally.
Drop a file, paste CSV, or load an imperfect or ready sample. Workbook selection and parsing stay local.
Set Free or paid limits, create or update behavior, a unique identifier, date interpretation, and explicit column types.
Resolve blockers, then download normalized UTF-8/LF CSV and the first 100 complete ready rows in source order.
The desk validates what a file can prove and labels every portal-dependent uncertainty for review.
Check one-sheet workbook shape, tier byte limits, row and column limits, UTF-8 evidence, row width, and 1 MB cells or rows.
Review First name, Last name, Email, Record ID, custom unique columns, duplicates, and Record ID precedence by import intent.
Explicitly check email, date, number, percentage, checkbox, phone, owner, enumeration, and additional-email columns.
Findings and reports omit contact values and filenames. Contact-data exports preserve every cell string and require no blocker.
The preflight never signs in to HubSpot or requests a property. Portal state and automation still need a controlled import test.
This release covers the quick contacts-only path. Multi-object imports, associations, marketing-contact settings, and overwrite settings are outside scope.
Custom properties, options, owners, existing records, account timezone, permissions, workflows, and lists are not queried.
Review mapping, import at most 100 test contacts, inspect records and errors, and retain the source and a rollback export.