Importing data into HubSpot is one of the most common tasks in any CRM setup or migration – and one of the most common sources of data quality problems. A rushed import can create thousands of duplicate contacts, overwrite existing data with stale values, or populate the wrong fields with incorrectly mapped data. Done carefully with the right file preparation, HubSpot’s import tool handles contacts, companies, and deals reliably. This guide covers the full import workflow, the decisions that matter, and the mistakes that cause the most post-import cleanup work.
That makes import planning important for both reporting accuracy and early user adoption.
HubSpot data import is useful when contacts, companies, and deals need to move into the CRM without losing structure. The job is not just to load records, but to make sure the data lands in the right objects and can be used immediately afterwards.
What HubSpot’s Import Tool Supports
HubSpot’s native import tool (under Contacts/Companies/Deals ? Import) handles:
- Contacts: Create new contacts or update existing ones. Deduplication on email address – if an imported contact’s email matches an existing contact, the existing record is updated rather than a new one created.
- Companies: Create or update company records. Deduplication on company name and domain name.
- Deals: Create deal records. HubSpot does not deduplicate deals – every imported deal row creates a new deal record.
- Associated records: Import contacts and companies together in a single file (using a common association column like Company Name or Domain) to create and link both records in one import operation.
File Preparation: The Critical Step
Spending time on file preparation before importing prevents the majority of post-import problems. A clean import file:
- Has a unique, valid email address in every row (for contacts). Rows without emails can be imported but won’t deduplicate properly and create low-quality records.
- Uses consistent formatting for property values that map to dropdowns. If your file has a “Industry” column that maps to HubSpot’s Industry dropdown property, every value in that column must exactly match one of HubSpot’s defined dropdown options (case-sensitive). “Software” will not match “SaaS” or “Technology.”
- Has one row per contact (not one row per contact per product, or per contact per interaction). If you have multiple rows for the same contact, decide in advance whether to deduplicate before import or let HubSpot merge during import (email-based deduplication will merge properties but may produce unexpected results if different rows have different values for the same field).
- Has all date values in a recognised format. HubSpot accepts dates in MM/DD/YYYY, YYYY-MM-DD, and Unix timestamp formats. Mixed date formats in the same column cause import failures.
- Has columns for only the properties you intend to import. Remove extraneous columns that don’t map to HubSpot properties – they’ll show as unmapped during the import wizard and can cause confusion.
Running the Import: Step by Step
- Go to Contacts ? Import ? Start an import.
- Select “Import from file” and upload your CSV (or XLSX). HubSpot accepts files up to 512MB and up to 1 million rows per import (split larger files into batches of 50,000-100,000 rows for manageable processing).
- Map columns to properties: HubSpot auto-suggests mappings based on column header names. Review every mapping – auto-suggestions are often wrong for custom columns or columns with non-standard names. For each column, select the HubSpot object (Contact, Company) and the specific property it maps to.
- Set lifecycle stage and lead status: If your import file contains a specific contact type (e.g., you’re importing trade show leads), set their lifecycle stage and lead status directly in the import – either as a column in the file or as a default value applied to all imported rows.
- Configure the “Don’t overwrite existing data” option: For updates to existing contacts, decide whether to overwrite existing property values or skip update if a value already exists. The safest default: check “Don’t overwrite” for important properties like Lifecycle Stage (you don’t want an import to downgrade an SQL back to Lead).
- Preview before confirming: HubSpot shows a preview of the first few rows of mapped data. Verify the mappings look correct before completing the import.
Using Import Static Lists
During import, HubSpot offers to create a static list containing all imported contacts. Always enable this – name the list with the import source and date (e.g., “HubFlow Conference Import – March 2026”). This static list serves as an audit trail: you can always find and review the imported records, build follow-up segmentation from them, or compare against your de-duplication results. If an import went wrong, you can use the static list to identify affected records and bulk-update or delete them.
Deduplication After Import
Even with email-based deduplication enabled, post-import duplicates occur when: the same person appears with two different email addresses, two records exist with the same email but different capitalisation (HubSpot’s importer is case-insensitive, but some import paths are not), or records were created via separate channels (form submission + manual creation + import) before the import ran. After any large import, run the HubSpot Manage Duplicates tool (Contacts ? Actions ? Manage Duplicates) to identify and merge remaining duplicates.
Importing Deals
Deal import requires specifying the pipeline, deal stage, close date, and deal amount for each deal row. Associate imported deals with contacts by including the contact’s email address as a column (HubSpot matches and links deals to contacts by email). Associate with companies using the company domain or company name column. Note: if the same deal is imported twice (e.g., from a re-import to fix a data error), HubSpot creates a second deal record – there’s no deal deduplication. Check for and delete accidental duplicate deals after any deal re-import.
The best import process is the one that reduces cleanup later. If the file mapping is careless, the CRM inherits problems instead of solving them.
Common Import Errors and Fixes
“Invalid value for [property name]”: The value in the import column doesn’t match the allowed values for a dropdown/radio property. Fix: download HubSpot’s property options list, align your import file values to match exactly, and re-import.
“Invalid date format”: Mixed date formats in a date column. Fix: standardise all dates in the column to YYYY-MM-DD before re-importing.
Records created but with blank lifecycle stage: Lifecycle Stage was not included in the import file and no default was set. Fix: bulk-update the static list for that import to set lifecycle stage via Contacts ? filter by the import list ? Actions ? Edit properties.
Sources
HubSpot, Contacts Import Documentation (2026)
HubSpot, Deals Import Guide (2026)
HubSpot, Data Import Best Practices (2025)
HubSpot, Manage Duplicates Tool (2025)
HubSpot, Import Error Reference (2025)
Is HubSpot easy to learn for beginners?
HubSpot has a learning curve, but its official free training platform HubSpot Academy provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest HubSpot mistakes to avoid?
Top mistakes include: over-customizing before understanding your process, skipping user training, importing dirty data without cleansing, and not establishing naming conventions. Avoid these four and your implementation will be significantly more successful.
How often does HubSpot release new features?
HubSpot releases major updates quarterly. HubSpot also ships smaller updates continuously to all tiers.
Does HubSpot offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. HubSpot Academy and the HubSpot Community are excellent free support resources.
Can HubSpot integrate with other business tools?
Yes. HubSpot App Marketplace has 1,500+ integrations including Gmail, Slack, Zoom, Shopify, and WordPress.
Common Challenges with HubSpot Data Import Guide and How to Solve Them
Problem: Getting Your Team to Consistently Use HubSpot
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where HubSpot adds the most value for your specific role. Focus training on those workflows first. Use HubSpot in-app guidance to provide contextual help at the moment of need rather than relying solely on one-time classroom training.
Problem: CRM Data Quality Degrading Over Time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use HubSpot deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
Problem: HubSpot Reports Not Matching Actual Business Results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue indicate data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.