Every CRM implementation begins with data—and how you get that data into your system determines whether your teams hit the ground running or spend weeks untangling errors. If you're adopting HubSpot CRM, the import process is the single most important step between your old workflows and a fully operational, automation-ready platform.
Yet data imports remain one of the most underestimated tasks in CRM implementations. Mismatched properties, duplicate records, broken associations, and formatting errors don't just create technical debt—they erode trust in your CRM before your team even starts using it. According to industry research, more than half of CRM data quality issues originate from the initial import process.
In this guide, we'll walk through everything you need to know about importing data to HubSpot in 2026—from pre-import planning and file preparation to mapping, associations, error resolution, and post-import validation. Whether you're migrating 500 contacts from a spreadsheet or 500,000 records from another CRM, this guide will help you do it right the first time.
HubSpot's import tool supports a wide range of CRM objects and activities. Understanding what you can bring in—and how records relate to each other—is the first step to a clean migration.
| Object Type | Can Create | Can Update | Unique Identifier |
|---|---|---|---|
| Contacts | ✅ | ✅ | Email address |
| Companies | ✅ | ✅ | Company domain name |
| Deals | ✅ | ✅ | Record ID |
| Tickets | ✅ | ✅ | Record ID |
| Products | ✅ | ✅ | Record ID |
| Custom Objects | ✅ | ✅ | Record ID or custom unique property |
| Tasks | ✅ (create only) | ❌ | — |
| Notes | ✅ (create only) | ❌ | Must be associated with an object |
| Calls | ✅ | ✅ | Record ID |
HubSpot accepts three file types for imports:
Important file requirements:
The difference between a smooth import and a disaster almost always comes down to preparation. These steps will save you hours of cleanup.
Before you touch HubSpot's import tool, conduct a thorough data audit:
Data cleaning is non-negotiable. Address these common issues before import:
Create a mapping document that aligns every column in your source data to a HubSpot property:
| Source Field | HubSpot Property | Property Type | Notes |
|---|---|---|---|
| Text (unique) | Primary unique identifier | ||
| Company Website | Company domain name | Text (unique) | Use domain only, not full URL |
| Lead Status | Lifecycle stage | Dropdown | Must match HubSpot's internal values |
| Sales Rep | Contact owner | Owner | Use email address, not name |
| Annual Revenue | Annual revenue | Number | Remove currency symbols and commas |
Pro tip: If your source data contains fields that don't exist in HubSpot, create custom properties in HubSpot before you import. This prevents the import wizard from skipping those columns.
Unique identifiers are how HubSpot recognizes whether to create a new record or update an existing one. Getting these right prevents the most common import problems:
Critical rule: If Record ID is mapped during your import, it supersedes all other unique identifiers. Only use Record ID when updating records you've already exported from HubSpot.
Use this when importing one type of record (e.g., contacts only):
Use this when importing related records together (e.g., contacts + companies):
Option A: Single file with both objects
Option B: Two separate files with a common column
You can import calls, emails, meetings, notes, and tasks alongside records:
Associations are the relationships between HubSpot records—linking a contact to their company, a deal to its associated contacts, or even contacts to other contacts (same-object associations).
To link contacts to companies during import:
For relationships like manager-to-employee:
Association labels let you specify the nature of a relationship—like "Decision Maker," "Billing Contact," or "Primary Company." Include a column with the label name that matches a label you've already created in HubSpot.
Even with careful preparation, errors happen. Here are the most common HubSpot import errors and their solutions:
Cause: Email format doesn't match standard format (name@domain.com)
Fix: Check for missing @ symbols, spaces, or invalid characters. Ensure emails are properly formatted.
Cause: A dropdown/checkbox value in your file doesn't match any existing option in HubSpot
Fix: Compare your values against the property's options in HubSpot. Use the internal value, not just the display label.
Cause: The owner name/email in your file doesn't match any active HubSpot user
Fix: Use the owner's email address (not name) and verify they're an active user in your account.
Cause: Two or more rows share the same unique identifier value
Fix: Remove duplicate rows or use Record ID to update specific records.
Cause: The unique identifier used for association doesn't match any existing record
Fix: Verify unique identifier values exist in HubSpot. Export current records to get correct Record IDs.
Cause: Date values don't match the format selected during import
Fix: Ensure all dates use a consistent format and match your selection in the import wizard.
Cause: A required property has no value for one or more rows
Fix: Fill in the required fields before re-importing. Check which properties are marked as required in your HubSpot settings.
Follow these proven strategies to ensure consistently clean imports:
For organizations with technical resources, HubSpot's Import API enables programmatic imports:
POST /crm/v3/importsFor ongoing data synchronization (not just one-time migration), consider HubSpot's native Data Sync:
Tools like Import2, Trujay, and SyncMatters specialize in CRM migrations:
At Vantage Point, we've guided hundreds of organizations through HubSpot CRM implementations—and we know that data migration is where projects succeed or fail. Our team brings deep expertise in:
Whether you're migrating from another CRM or consolidating data from spreadsheets and disconnected tools, Vantage Point ensures your HubSpot implementation starts with a rock-solid data foundation.
HubSpot accepts CSV (.csv), Excel 97-2003 (.xls), and Excel 2007+ (.xlsx) files. CSV is the most commonly used and recommended format. Files must be under 512 MB, contain only one sheet, and have column headers in the first row.
Use unique identifiers in your import file—email addresses for contacts and company domain names for companies. When updating existing records, include the Record ID column. Select "Create and update" during the import process so HubSpot matches existing records instead of creating duplicates.
Yes. HubSpot offers a native Salesforce integration that can sync data between the two platforms. You can also export Salesforce data to CSV files and import them into HubSpot manually. For complex migrations, HubSpot's self-service transfer tool or a partner like Vantage Point can help ensure a smooth transition.
A single import file can contain up to 1,048,576 rows (the maximum for most spreadsheet applications). However, for best results and easier error handling, we recommend importing in batches of 5,000–10,000 records. The maximum file size is 512 MB.
Include both the contact's email address and the company's domain name in your import file. During the import process, select the option to import multiple objects and associate them. HubSpot uses the unique identifiers to create the relationship automatically.
First, review the import summary for error details. Download the error file, which contains the specific rows and error codes. Fix the issues in your original file (formatting, missing values, incorrect identifiers), then re-import only the affected rows. Common errors include invalid email formats, unrecognized dropdown values, and missing required properties.
Small imports (under 5,000 records) typically complete in under 5 minutes. Larger imports (50,000–100,000+ records) may take 30 minutes to several hours depending on file complexity and association mapping. The total project timeline—including planning, cleaning, and validation—ranges from a few hours to several weeks for enterprise migrations.
Importing data into HubSpot isn't just a technical step—it's the foundation of your entire CRM strategy. Clean, well-structured data powers accurate reporting, reliable automation, effective segmentation, and ultimately, better customer experiences. Taking the time to audit, clean, map, and validate your data before import pays dividends for months and years to come.
Whether you're handling your first import or managing a complex multi-system migration, the principles remain the same: prepare thoroughly, use unique identifiers consistently, test before going live, and validate after every import.
Ready to get your HubSpot data migration right the first time? Contact Vantage Point to learn how our team can help you plan, execute, and optimize your data import for maximum CRM performance.
Vantage Point is a certified Salesforce and HubSpot partner specializing in CRM implementation, data migration, integration, and AI-powered automation. We help businesses of all sizes build connected, intelligent customer platforms using Salesforce, HubSpot, MuleSoft, Data Cloud, and Anthropic Claude AI. Learn more at vantagepoint.io.