The file
This page covers emails you already have as data, from an old CRM or an export. For emails that only exist in people’s inboxes, see the related answer on historic emails.
| Column | Required? | What to put |
|---|---|---|
| Email body | Yes | Plain text is safest; HTML from old systems often renders badly |
| Email direction | Yes | Incoming or Outgoing |
| Activity date | Strongly recommended | The original sent date and time. Without it, HubSpot uses the import time |
| Email subject | Recommended | Makes the timeline readable |
| From / To | Recommended | Sender and recipient addresses, for reference |
| Activity assigned to | Recommended | The HubSpot user who owned it, by email |
| Contact email / company domain / deal Record ID | Yes, at least one | Associates the email with the record |
Steps
- Load contacts, companies and deals first.
- Convert the source’s direction flags (inbound/outbound, sent/received) to Incoming or Outgoing.
- Turn dates into one format and time zone, and test a few to check the timezone shift.
- Run a multi-object import (emails plus contacts, or plus deals) and map the identifier columns.
- Import a sample of 100 emails and open five timelines to check them.
- Import the rest. On paid accounts, HubSpot allows 1,048,576 rows per file and 10 million rows per rolling 24 hours.
What the native tool does / where it stops
The importer does a good job of putting emails on the timeline. Its limits are about correcting mistakes:
- Imported emails can’t be updated, only deleted and imported again.
- Each email must be associated with a record.
- Attachments aren’t part of the email activity.
- Threading isn’t rebuilt; each email is a separate activity.
Plan the mapping carefully: a wrong timezone across 200,000 emails is slow to fix.
Where FlitStack AI fits
FlitStack AI loads email history from the source CRM’s API as HubSpot email activities, with original timestamps, owners and associations. It runs a sample check first. See the HubSpot import guide or HubSpot migrations.