Step one: find where the emails are
| How the emails got into Salesforce | Where they’re stored | Exportable? |
|---|---|---|
| Enhanced Email (Gmail/Outlook integration, send from Salesforce) | EmailMessage and EmailMessageRelation, plus a Task for compatibility | Yes, via API or Data Loader |
| Older logging or Salesforce for Outlook | Task with Type = Email (subject and description) | Yes |
| Einstein Activity Capture, legacy setup | Outside standard objects | No. Salesforce says this data “couldn’t be exported” |
| Einstein Activity Capture with “Sync Email as Salesforce Activity” (since Summer ‘25) | Task and EmailMessage | Yes, from when the setting was on |
If your team used legacy EAC, the history may exist only in the reps’ mailboxes. Then the source is Gmail or Outlook, not Salesforce. This is the point the EAC thread turns on, and HubSpot’s docs don’t cover it.
What the native tools do / where they stop
- Smart Transfer syncs Salesforce Email Messages as HubSpot email activities. It can only move what sits in standard objects.
- HubSpot’s import tool creates email activities from a file. It needs Email body and Email direction (Incoming or Outgoing). Without Activity date, it uses the import time. Imported emails can’t be updated afterwards.
- Connecting inboxes to HubSpot doesn’t backfill. HubSpot says historical emails “will not be logged to the CRM automatically.”
Steps (import route)
- Query EmailMessage (
Subject,TextBody,FromAddress,ToAddress,MessageDate,Incoming) and EmailMessageRelation for the people involved. - Turn
Incominginto Email direction values. - Resolve each email to its HubSpot contact by email address, and to its deal or company by Salesforce ID.
- Map
MessageDateto Activity date and the sender’s user to the activity owner. - Import a sample, check the threads on a few contact timelines, then import the rest.
Where FlitStack AI fits
FlitStack AI reads EmailMessage and email tasks through the Salesforce API. It loads them as HubSpot email activities with original dates, owners and associations. See Salesforce to HubSpot or HubSpot migrations.