What HubSpot and Hype & Dexter validate when migrating data into HubSpot
During Import
HubSpot automatically runs a series of validation checks to ensure the data can be processed correctly. Some of these include:
- Column headers: Checks that every column has a header; flags blanks or duplicates.
- Duplicate columns: Prevents mapping the same column twice to different properties.
- Blank columns: Flags and ignores any with no header or data.
- Empty rows: Skips rows that contain no data across all columns.
- Malformed values: Rejects values that don’t match expected formatting (e.g., invalid date, text in a number field).
- Property mapping: Ensures each column is mapped to a valid HubSpot property.
- Data type validation: Confirms values match the property type (e.g., number, date, text, or boolean).
- Picklist/multi-select validation: Flags values not in the property’s defined options; prompts to add them if allowed.
- Email addresses: Validates format when importing contacts.
- Object uniqueness:
-
-
Contacts → unique by email or custom unique property.
-
Companies → unique by domain name or custom unique property.
-
Deals, tickets, custom objects → unique by record ID or chosen unique property.
-
-
Associations: Checks that associations point to valid existing records (or can be created).
-
Deduplication: Prevents duplicate records based on primary identifiers.
-
Record IDs: Verifies HubSpot record IDs exist and match the right object if used for updates.
-
Error handling: Any invalid or rejected rows are skipped and logged in an error file.
-
Batch processing & rate limit safety: Large imports are broken into chunks and processed in compliance with HubSpot’s API rate limits.
Post Import
Post the Import into HubSpot, Hype & Dexter will check all of the raised validation errors by HubSpot and update the data manually or by a new import.
Manual data checks also take place by creating reports to show record counts/associations. Views are created to check property data, and spot checks are completed on a set of records to validate that data has been imported correctly against the Data Migration Brief.
*Note that, based on your Data Migration Tier, validation into a Sandbox environment may also be included before importing into a Production environment.