Freshsales to HubSpot
Freshsales (Freshworks CRM) is a sales CRM covering contacts, accounts, deals, leads, activities and custom modules.
Freshsales data can move into HubSpot, landing mainly in Sales Hub. 3 of 13 mapped objects move directly (Contacts, Accounts and Deals); 5 items need manual work and 2 do not move. Plan roughly 1-3 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Freshsales
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k records
CSV import of core objects with light rebuild.
Mid migration
25k-250k records
Tool or API for activities, with rebuilt workflows and reports.
Large migration
>250k records plus heavy activity history
API throttling, custom modules and a phased cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Freshsales: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON)
API key from Settings > API Settings, plus the account domain (yourdomain.freshsales.io).
Admin access is needed to obtain the API key and read all data.
Sources conflict. Per-plan hourly limits are reported as 1,000 (Free/Growth), 2,000 (Pro) and 5,000 (Enterprise) per account. One source also cites 400 requests/min. Confirm in the live account.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Freshsales.
- You need: API key from Settings > API Settings, plus the account domain (yourdomain.freshsales.io).
- Permission: Admin access is needed to obtain the API key and read all data.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Native CSV export per module, emailed as a download link
- Export limited to about 50,000 records per file (third-party source), so split large modules by filter
- Each module exports separately, so associations are not in one file
- Scheduled exports in Classic (70 fields, 5 schedules per module, per third-party source)
- REST API extraction, with bulk operations up to 100 records per request
Limits: Sources conflict. Per-plan hourly limits are reported as 1,000 (Free/Growth), 2,000 (Pro) and 5,000 (Enterprise) per account. One source also cites 400 requests/min. Confirm in the live account.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Freshsales
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | CSV or API. Records without an email can be dropped by the sync connector, so import those by CSV. |
| Accounts | Companies | yes | Import companies and contacts before deals so associations can be created. |
| Deals | Deals | yes | Map pipeline stages first. Stage history does not come across. |
| Leads | Contacts | partial | Migration tools map Freshsales leads to HubSpot leads. Decide whether to use Contacts with lifecycle stage or the Leads object. |
| Notes | Notes | partial | The native sync does not carry notes. Use the API or a migration tool. |
| Call logs | Calls | partial | Not covered by the native sync. Use the API or a tool. |
| Appointments | Meetings | partial | Not covered by the native sync. Use the API or a tool. |
| Emails | Emails | partial | A tool needs an API key and an active license for each Freshsales user whose email is migrated. |
| Tasks | Tasks | partial | Available through the API and migration tools. |
| Files/attachments | Files | partial | Some tools skip attachments because of API limits. |
| Users/owners | Contacts | manual | Create HubSpot users first, then map the Freshsales owner to HubSpot owner. The owners selector endpoint omits deactivated users. |
| Custom modules | Custom objects | partial | Native export and API cover them. HubSpot custom objects depend on plan, otherwise collapse the data into properties. |
| Sales pipelines/stages | Deals | manual | Rebuild pipelines and stages in HubSpot before import. |
What to expect
The import does not bring stage history across, so velocity reports restart at cutover.
Needs reconfiguration in HubSpot.
Automation rules are not moved by data import tools.
Field-level permissions are an Enterprise feature in Freshsales. HubSpot permission sets must be built separately.
Reports are not exportable as definitions. Rebuild them in HubSpot.
Freshsales custom fields need matching HubSpot properties.
Native CSV exports each module separately, so rebuild associations with IDs or the API.
Carry Freshsales IDs into HubSpot properties and use them to rebuild associations.
Plan a separate API or tool track for activities.
Throttle requests, read the rate-limit headers, and run the extraction off-hours. The quota is shared across all integrations on the account.
Count and export these records before cutover and import them by CSV.
Check the plan limits in the live account before sizing the timeline.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
API auth, rate limits and export routes are supported by vendor developer docs and secondary sources. Object mapping rests mainly on migration-vendor and community sources, not HubSpot docs. Native HubSpot import docs, the automation and permission export paths, and data residency were not verified.
Sources
Related migrations
Frequently asked questions
How do I migrate Freshsales to HubSpot?
1. Generate an admin API key in Settings > API Settings and note the account domain. 2. Confirm the plan's hourly API limit and plan features such as custom modules. 3. Inventory modules: contacts, accounts, deals, leads, tasks, notes, appointments, calls and custom modules. 4. Count contacts that have no email address.
What data can move from Freshsales to HubSpot?
These objects move directly: Contacts, Accounts and Deals. Check the mapping table for partial and manual items.
What does not move from Freshsales to HubSpot?
Deal stage history / pipeline velocity history and Freshsales telephony configuration. Plan to rebuild or retire these.
How long does a Freshsales to HubSpot migration take?
Small (<25k records): 1-3 weeks. Mid (25k-250k records): 3-8 weeks. Large (>250k records plus heavy activity history): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Freshsales?
API key from Settings > API Settings, plus the account domain (yourdomain.freshsales.io). Admin access is needed to obtain the API key and read all data.
Is there a native HubSpot connector for Freshsales?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Freshsales data?
Check: Free-text notes and call logs may contain health or financial data. Review them case by case.. Agree consent, retention and access rules before exporting.
Moving Freshsales into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner