HubSpot’s importer is good at what it was built for: getting rows from a spreadsheet into HubSpot records, with associations between them. It is not a migration tool, and the difference shows up in history. Create dates, activity dates, relationship labels and the ability to fix mistakes are where imports go wrong. This guide gives the limits from HubSpot’s documentation, then each gap and how to handle it.
What are HubSpot’s import limits?
| Limit | Free tools | Smart CRM, Starter, Professional, Enterprise |
|---|---|---|
| File size | 20 MB | 512 MB |
| Rows per file | (not stated separately) | 1,048,576 |
| Imports per rolling 24 hours | 50 | 500 |
| Rows per rolling 24 hours | 500,000 | 10,000,000 |
| Columns | Fewer than 1,000 | Fewer than 1,000 |
| Sheets per file | One | One |
The limits apply to a rolling 24-hour window, not a calendar day.
How do I import contacts into HubSpot?
- Prepare one file per object, or one file containing two objects if you want them associated in a single import.
- Include the required columns. Contacts need Email. Companies need Name or Company domain name. To update existing records, include a unique identifier: Record ID, Email or Company domain name.
- Add an owner column named “Contact owner” (or “[Object] owner”) with the user’s email address. Names work but clash when two users share one. Owners assigned by import are not notified.
- Create custom properties first for any column that has no matching HubSpot property, and match dropdown values exactly.
- In HubSpot, go to CRM > Contacts > Import, choose the file and object, map columns to properties, and choose create, update, or both.
- Decide the marketing status. New contacts are non-marketing by default. A single-file contacts import has a checkbox to set them as marketing contacts, which counts them toward your billable tier.
- Review the error file HubSpot produces and fix rows that failed.
How do I import deals into HubSpot?
Deals need a pipeline and stage that already exist. Build the pipelines and stages first, then map the source’s stage names to them in the file. To link deals to companies and contacts:
- One file: put deal columns and company columns on the same row. HubSpot creates both and associates them.
- Several files: import companies, then deals, and pick a common column (for example the company domain) that HubSpot uses as the key between files.
Deal Create date is documented as editable, so you can carry the original value. Map deal amounts, close dates and owners at the same time.
What happens to create dates on import?
This is the most common question from teams moving into HubSpot. HubSpot’s default contact properties page says the contact Create date is “automatically set by HubSpot”. So an imported contact shows the import date as its create date. Deal Create date, by contrast, is set automatically but can be edited by users.
The practical fix: import the source system’s created date into a custom date property (for example “Original create date”) on contacts and companies, and use it in reports, lists and lifecycle analysis. Decide this before the first import, because re-importing to add it later counts against your daily limits.
How do associations and association labels import?
Associations come from the file structure: two objects on one row, or a shared column across files. Association labels are stricter:
- Custom labels need a Professional or Enterprise subscription.
- The labels must exist in HubSpot before you import.
- Importing a label adds it to the association. It doesn’t overwrite an existing label.
If the source CRM has relationship types (for example “decision maker”, “billing contact”, or a contact who belongs to several companies), list them, create the matching labels, and add a label column to the file.
Can I import activities and notes into HubSpot?
Yes. HubSpot’s import file guide lists the required columns per activity type:
| Activity | Required columns |
|---|---|
| Calls | Call notes |
| Emails | Email body, Email direction |
| Meetings | Meeting description, start time, end time |
| Notes | Note body |
| Tasks | Task title, Due date |
Two rules decide whether history survives:
- Map Activity date. If you leave it out, HubSpot sets the activity date to the date and time of the import, and the whole timeline collapses onto one day.
- Get it right first time. HubSpot says existing emails, meetings, notes and tasks can’t be updated through import, however you import them. A mistake means deleting and re-importing.
Each activity also has to be associated with the right contact, company or deal, using the same identifiers as your record files. Use “Activity assigned to” for the owner.
Can I import custom objects into HubSpot?
Custom object records import the same way as standard ones, once the object and its properties exist in HubSpot. Define the object, its required properties and its associations to contacts, companies and deals first. Then import parents before children so the associations resolve.
How do I check a HubSpot import worked?
- Open the import in Imports and download the error file; fix and re-import only the failed rows.
- Compare record counts per object with the source file.
- Open ten records with the most activities and check their timeline dates and owners.
- Filter for records with no associated company or contact to find broken links.
What does a HubSpot import not do?
- Extract from your old CRM. You need an export from the source first, and many exports leave out emails, call logs or files.
- Translate the data model. Lead objects, record types and stage logic from other CRMs need decisions before mapping.
- Undo. There is no rollback. You find and delete the imported records.
- Keep the old system in sync during cutover. Anything changed after the export needs another import.
- Prove completeness. You get an error file, not a reconciliation against the source.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It reads the source through its API, proposes field-level mappings with AI for you to review, and runs a sample before the full migration. It moves activities with original timestamps and user attribution, preserves create dates, rebuilds associations and labels, validates every record, and offers one-click rollback. Delta migration picks up changes during cutover. The HubSpot implementation service builds pipelines, properties and workflows in the destination.
Common routes: Salesforce to HubSpot and Pipedrive to HubSpot. Compare with HubSpot’s own Smart Transfer, or see the HubSpot migration hub. For a quote, book a free scoping call.