Importing data into HubSpot should be simple, but even experienced users encounter errors. These five common import errors account for 90% of all import failures. Learn how to identify and fix them before they derail your data import.
Error #1: Duplicate Contacts
The Problem: HubSpot creates duplicate contacts when you import the same email address multiple times. This leads to fragmented contact records, confused sales teams, and inaccurate reporting.
Why It Happens:
- Importing the same CSV file twice
- Merging data from multiple sources without deduplication
- Case sensitivity issues (john@example.com vs John@Example.com)
- Importing contacts that already exist in HubSpot
The Fix:
- 1. Deduplicate before importing: Remove duplicate rows from your CSV based on email addresses
- 2. Use HubSpot's duplicate detection: Enable "Skip duplicates" in the import settings
- 3. Check existing contacts: Export your current HubSpot contacts and remove matches before importing
- 4. Use a tool with automatic deduplication: AI-powered import tools can detect and merge duplicates automatically
Error #2: Invalid Email Addresses
The Problem: HubSpot requires a valid email address for every contact. Invalid emails cause rows to be skipped during import, meaning you lose valuable contact data.
Common Invalid Email Formats:
- Missing @ symbol: "johnexample.com"
- Typos: "john@exmaple.com" (missing 'a')
- Spaces: "john @example.com"
- Invalid characters: "john@example@com"
- Empty cells: Blank email fields
The Fix:
- 1. Validate emails before importing: Use email validation tools or regex patterns
- 2. Clean your CSV: Remove spaces, fix common typos, and standardize formats
- 3. Handle missing emails: Either remove rows without emails or use a placeholder (not recommended)
- 4. Use bulk email validation: Services can validate thousands of emails in minutes
Error #3: Column Mapping Mismatches
The Problem: When CSV column names don't match HubSpot property names, data ends up in the wrong fields or gets skipped entirely. This is one of the most common and frustrating import errors.
Example Mismatches:
| Your CSV Column | HubSpot Property | Result |
|---|---|---|
| "First Name" | "firstname" | ❌ Won't map automatically |
| "Company" | "Company Name" | ❌ Needs manual mapping |
| "Job Title" | "jobtitle" | ❌ Case sensitivity issue |
The Fix:
- Rename CSV columns: Before importing, rename columns to match HubSpot property names exactly
- Use HubSpot's mapping tool: Manually map each column during import (time-consuming but accurate)
- Use AI-powered mapping: Tools can automatically detect and map columns using AI, reducing errors by 90%
- Check property names: Verify exact property names in HubSpot Settings → Properties
Error #4: Date Format Issues
The Problem: HubSpot expects dates in specific formats. Wrong formats cause dates to be imported as text or skipped entirely, breaking date-based workflows and reporting.
Common Date Format Problems:
- US format (MM/DD/YYYY) vs International (DD/MM/YYYY) confusion
- Text dates: "January 15, 2026" instead of "2026-01-15"
- Excel date serial numbers: 45296 instead of actual date
- Mixed formats in the same column
The Fix:
HubSpot's Preferred Format: YYYY-MM-DD (e.g., 2026-01-15)
- 1. Convert all dates to YYYY-MM-DD format before importing
- 2. Use Excel formulas or data cleaning tools to standardize formats
- 3. For date-time fields, use: YYYY-MM-DD HH:MM:SS
- 4. Validate dates to ensure they're not in the future (unless intentional)
Error #5: Missing Required Fields
The Problem: HubSpot requires certain fields for contacts. Missing required fields cause entire rows to be skipped during import.
Required Fields for Contacts:
- Email: Absolutely required - contacts without emails cannot be imported
- First Name or Last Name: At least one is recommended (though not strictly required)
- Company Name: Required if creating company records
The Fix:
- Fill missing emails: If possible, research and add missing email addresses
- Remove incomplete rows: Delete rows missing required fields if they can't be filled
- Use placeholders carefully: Only use "Unknown" or similar if absolutely necessary
- Validate before importing: Check for empty required fields in your CSV
Prevention: Best Practices
The best way to fix import errors is to prevent them. Follow these best practices:
Pre-Import Checklist:
- ✓ Validate all email addresses
- ✓ Remove duplicate rows
- ✓ Standardize date formats to YYYY-MM-DD
- ✓ Map columns to HubSpot properties correctly
- ✓ Fill in missing required fields
- ✓ Test with a small sample (10-20 rows) first
- ✓ Check for special characters that might break imports
- ✓ Verify data types match HubSpot property types
Conclusion
These five errors account for the vast majority of HubSpot import failures. By understanding what causes them and how to fix them, you can dramatically improve your import success rate.
For teams that import data regularly, consider using automated tools that handle data cleaning, validation, and mapping automatically. This saves time and reduces errors, allowing you to focus on what matters: turning imported data into revenue.