Most of your Freshsales data can move to HubSpot. Contacts, accounts, deals, products, notes, tasks, appointments and call logs all have a direct equivalent. Tags, territories, sequences, workflows and Freddy AI scores don't, so they're converted into HubSpot properties or rebuilt. Sales email content doesn't migrate, though teams on Gmail can bring their email history into HubSpot from their own inboxes. How much activity history comes across depends on what Freshsales exports and how the import is set up.
Part of our HubSpot guides.
How do Freshsales objects map to HubSpot?
Each core Freshsales module has a matching HubSpot object, with a few that need converting. The table below is the mapping we start from when planning a Freshsales migration.
| Freshsales | HubSpot | Notes |
|---|---|---|
| Contacts | Contacts | Direct match. Email is the unique identifier |
| Leads (Freshsales Classic) | Contacts with a lifecycle stage | Optional Lead record in Sales Hub for prospecting |
| Accounts | Companies | Matched to contacts by domain |
| Deals | Deals | Imported into recreated pipelines |
| Deal pipelines and stages | Deal pipelines and stages | Good time to retire unused stages |
| Products | Products | Direct match |
| Deal products | Line items | Must be associated with a deal |
| Notes | Notes | Original date needs mapping |
| Tasks | Tasks | Can be created on import, not updated |
| Appointments | Meetings | Original date needs mapping |
| Call logs | Calls | Original date needs mapping |
| Sales emails and conversations | Not migrated | Gmail history can be imported from each inbox |
| Custom fields | Custom properties | Field types should match |
| Custom modules (Enterprise) | Custom objects | Requires Enterprise in HubSpot |
| Files and attachments | Files | Not listed in the Freshsales account export |
| Tags | Multi-select property | No tag equivalent on HubSpot records |
| Territories | Teams or a property | Often combined with owner rules |
| Sequences and workflows | Sequences and workflows | Rebuilt, not migrated |
For the step-by-step process, see how to migrate from Freshsales to HubSpot.
Which Freshsales data doesn't migrate to HubSpot?
Automation, AI scoring and a few organising features don't migrate as data. They're rebuilt or replaced in HubSpot, ideally as an improvement on what was there.
- Sales sequences. Steps and templates can be copied across manually. Enrolment history doesn't carry over.
- Workflows. Freshsales workflow logic doesn't export. Each one is reviewed and rebuilt in HubSpot workflows, and some are retired.
- Freddy AI scores and insights. These are calculated inside Freshsales. HubSpot lead scoring replaces them.
- Tags. Converted into a multi-select property so they can still be filtered and reported on.
- Territories. Recreated as HubSpot teams, a territory property, or assignment rules in a workflow.
- Saved views and reports. Rebuilt as HubSpot views, lists and reports.
Does activity history move from Freshsales to HubSpot?
Activity history can move, but it takes the most planning. Notes, tasks, meetings and calls can all be created in HubSpot through its import tool or API, as long as each one is linked to the right contact, company or deal. Sales email content is the exception, covered below.
Two details decide whether the history is useful once it's there:
- Original dates. HubSpot sets the Activity date to the date and time of the import unless you map a date column. Without it, five years of notes look like they all happened on migration day.
- Associations. Each activity needs a shared identifier, such as the contact's email or the original record ID, to attach it to the right record.
For a sales-led team, call history is usually what matters most. When we moved a Sydney financial services company off Freshsales in 2025, the history their five reps relied on was call details and notes across around 20,000 leads in one pipeline.
We plan migrations around what Freshsales can actually hand over. Where an older system holds history in a format that won't map cleanly, it's sometimes better to bring across a summary note or keep an archive export than to force it in.
Can you migrate Freshsales emails to HubSpot?
No. Sales email content logged in Freshsales doesn't migrate into HubSpot. If your team uses Gmail, HubSpot's historical email import can bring past emails into the CRM from each rep's own inbox instead.
What to know about that route:
- It only works with Gmail accounts connected to HubSpot as individual work emails. Outlook and Microsoft 365 aren't supported.
- It needs Sales Hub Professional or Enterprise. It's in beta, so a Super Admin opts the account in and sets the import timeframe.
- It reads from each rep's mailbox, not from Freshsales, so it only finds emails that are still in that inbox.
- For teams on Outlook, the email conversations in the Freshsales export are worth keeping as an archive.
- Once inboxes are connected to HubSpot, new emails log automatically from the day you switch over.
What happens to Freshsales custom fields in HubSpot?
Each Freshsales custom field becomes a HubSpot custom property, or is merged into an existing default property, or is dropped. The field type should match: dropdowns become dropdown properties with the same options, date fields become date properties, and so on.
This is the step where migrations tend to improve or degrade a CRM. A useful test for each field is whether anyone has filled it in during the past year and whether any report uses it. Fields that fail both tend to be better left behind.
What are HubSpot's import limits?
HubSpot's import tool accepts CSV, XLSX and XLS files with one sheet and fewer than 1,000 columns, according to HubSpot's knowledge base. On paid subscriptions, each file can be up to 512 MB and 1,048,576 rows, with up to 10,000,000 rows imported per rolling 24 hours. Free HubSpot tools have a 20 MB file limit and 500,000 rows per day.
These limits rarely constrain a typical Freshsales migration. Activity history is usually the largest file.
Frequently asked questions
Do Freshsales record owners carry over to HubSpot?
Yes, if your users are created in HubSpot first. Owners are matched by the user's email address, so each Freshsales user needs a HubSpot seat or a decision on who inherits their records.
Can we keep the Freshsales record IDs?
Yes. We add the Freshsales ID as a custom property on each record. It makes the migration traceable and helps match activities and later delta imports.
Do Freshsales deal values and close dates migrate?
Yes. Amount, close date, stage, owner and custom deal fields import into HubSpot deal properties. Closed deals are often worth bringing across for revenue reporting.
What happens to Freshsales products and CPQ quotes?
Products import into the HubSpot product library and deal products become line items. Historical quote documents usually stay as an archive, with new quotes created in HubSpot.
Do unsubscribes and email consent come across?
They should. Opt-out status needs mapping so people who unsubscribed in Freshsales aren't emailed from HubSpot. This is worth checking before any marketing email goes out.
The pattern we see
The fields that matter most in a migration are usually the ones the team uses every day: owner, stage, call outcomes and notes. Everything else has to earn its place. How many of your Freshsales fields were filled in this year?