Freshdesk to HubSpot
Cloud help desk with ticketing, contacts, companies, knowledge base, SLA policies and automations.
Freshdesk data can move into HubSpot, landing mainly in Service Hub. 3 of 8 mapped objects move directly (Contacts (requesters), Companies and Tickets); 4 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 Freshdesk
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 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
Under 5,000 tickets
A tool or CSV import is enough.
Mid migration
5,000-50,000 tickets
A migration tool plus workflow rebuild.
Large migration
Over 50,000 tickets
Engineer-led, with archived tickets and inline image re-hosting.
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 Freshdesk: what you need to get in, what lands in HubSpot, and what will not.
REST API v2 (JSON)
Freshdesk subdomain and an API key from an agent profile.
Admin access is needed for the account export and to see all tickets, contacts and KB. The exact permission model was not verified.
Per-minute and account-wide. The official docs page lists Growth 100, Pro 400 and Enterprise 700, with per-endpoint sub-limits. Other guides cite 200 for Growth. List All Tickets stops at 300 pages (about 30,000 tickets).
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Freshdesk.
- You need: Freshdesk subdomain and an API key from an agent profile.
- Permission: Admin access is needed for the account export and to see all tickets, contacts and KB. The exact permission model was not verified.
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.
- UI CSV export of tickets and contacts (omits conversation threads and archived tickets)
- Account export (XML/JSON dump)
- REST API v2 for tickets, conversations, contacts, companies and KB articles
- Archived tickets fetched one by one by ID
Limits: Per-minute and account-wide. The official docs page lists Growth 100, Pro 400 and Enterprise 700, with per-endpoint sub-limits. Other guides cite 200 for Growth. List All Tickets stops at 300 pages (about 30,000 tickets).
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 Freshdesk
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (requesters) | Contacts | yes | Match on email. Contacts can carry other_emails, so dedupe beyond the primary email. Custom fields become custom properties. |
| Companies | Companies | yes | Create companies before contacts, then associate them. |
| Tickets | Tickets | yes | List endpoint returns only the last 30 days unless updated_since is set. Fields include status, priority, group, source and dates. |
| Ticket conversations (replies, notes, forwards) | Emails | partial | Needs a separate call per ticket. CSV export omits them. Private notes need visibility validation. They land as engagements (emails). |
| Attachments and inline images | Files | partial | Attachments are uploaded individually to HubSpot's File Manager. Inline images need re-hosting. |
| KB articles (categories, folders, articles) | Custom objects | manual | The API returns HTML bodies with the folder hierarchy. The article destination in HubSpot (knowledge base) was not verified here. |
| Ticket tags | Tickets | partial | There is no native tag object on HubSpot tickets. Map tags to a custom multi-select property. |
| SLA policies | Tickets | manual | Rebuild as HubSpot SLA and workflow configuration. SLA semantics are not migrated as data. |
What to expect
There is no bulk list endpoint. Archived tickets can only be fetched by known ID, and the account export is used for discovery.
These are configuration and not exported as portable data. They must be rebuilt in HubSpot.
The scope note says to rebuild them. Exact HubSpot equivalents were not verified.
The scope note requires validating SLA semantics.
Inline images are dropped by the native sync.
Ticket owner mapping needs existing users.
Walk by updated_since date windows and reconcile counts against the Freshdesk reports.
Use an API-level or dedicated migration tool for history.
Test private-note visibility on a demo batch.
Throttle and watch the X-RateLimit-Remaining header.
Store the overflow as notes or a file.
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.
The API, export paths and object mapping are supported by Freshworks-referencing guides and migration vendors. I did not open the Freshworks or HubSpot docs directly. SLA, automation and macro semantics rest on category-level knowledge. Rate limits conflict between sources.
Sources
Related migrations
Frequently asked questions
How do I migrate Freshdesk to HubSpot?
1. Confirm the Freshdesk plan and its per-minute API limit, then generate an API key from an admin agent. 2. Count tickets, including archived ones, via the account export, and compare with the 30,000 cap. 3. Inventory custom ticket and contact fields, and create matching HubSpot custom properties. 4. Create HubSpot users and teams for agents and groups.
What data can move from Freshdesk to HubSpot?
These objects move directly: Contacts (requesters), Companies and Tickets. Check the mapping table for partial and manual items.
What does not move from Freshdesk to HubSpot?
Archived tickets via bulk listing and Routing rules, automations and macros. Plan to rebuild or retire these.
How long does a Freshdesk to HubSpot migration take?
Small (Under 5,000 tickets): 1-3 weeks. Mid (5,000-50,000 tickets): 3-8 weeks. Large (Over 50,000 tickets): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Freshdesk?
Freshdesk subdomain and an API key from an agent profile. Admin access is needed for the account export and to see all tickets, contacts and KB. The exact permission model was not verified.
Is there a native HubSpot connector for Freshdesk?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Freshdesk data?
Check: Tickets and attachments may contain health, financial or minors' data depending on the customer and Regulated accounts should use an engineer-led migration with an audit trail. Agree consent, retention and access rules before exporting.
Moving Freshdesk 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