---
title: "Freshdesk to HubSpot Service Hub Migration | FlitStack AI"
description: "Migrate Freshdesk to HubSpot Service Hub with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/freshdesk/to/hubspot-service-hub"
---

# Freshdesk to HubSpot Service Hub migration

We migrate Tickets, Contacts, Companies, and conversation history from Freshdesk into HubSpot Service Hub with parent-record lookup resolved before insert, Freshdesk agent-to-HubSpot-user matching confirmed, and every Freshdesk custom field created in HubSpot before the first ticket batch lands. Multi-channel source types are normalized to HubSpot channel equivalents to prevent silent data loss on non-email channels.

Short answer

FlitStack AI migrates tickets, contacts, companies, users and conversations from Freshdesk to HubSpot Service Hub, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/freshdesk/to/hubspot-service-hub#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Freshdesk ![](https://flitstack.ai/platforms-trim/freshdesk.webp)

Destination HubSpot Service Hub ![](https://flitstack.ai/platforms-trim/hubspot-service-hub.webp)

Ticket Contact Company User Conversation

Mapped field by field · sample run · one-click rollback

## What moves from Freshdesk to HubSpot Service Hub?

Moving from Freshdesk to HubSpot Service Hub is a cross-platform migration that requires careful sequencing across two API rate-limit regimes and a fundamentally different object model.

Read the full summary

Freshdesk organizes support around tickets linked to requesters and companies; HubSpot Service Hub attaches tickets directly to CRM contacts and companies, giving agents full lifecycle context without switching tabs. We extract Freshdesk Tickets, Conversations, Contacts, Companies, Agents, SLA Policies, Products, Tags, Time Entries, and Satisfaction Ratings in dependency order, resolving the Freshdesk-to-HubSpot agent match and the contact-to-company lookup before any record lands in HubSpot. Freshdesk automations, macros, and SLA policies do not migrate as code; we deliver written inventories for the customer's admin to rebuild in HubSpot's workflow builder and SLA configuration. The Freshdesk free plan blocks API access entirely, so we require at least the Growth plan before scoping begins.

1:1

### Ticket → Ticket

Freshdesk Tickets map directly to HubSpot Tickets.

How it maps

Subject, status, priority, type, source/channel, and requester link migrate. Freshdesk's channel field (email, phone, chat, portal, tweet, Facebook, survey, forwarded email) is normalized to HubSpot channel values; non-standard Freshdesk channels default to 'custom' and the original channel name is preserved in a metadata field. Freshdesk ticket ID is stored in a custom HubSpot field for cross-reference.

1:1

### Contact (Requester) → Contact

Freshdesk Contacts (requesters) map to HubSpot Contacts.

How it maps

Name, email, phone, job title, language, and company association migrate. Custom contact fields require pre-creation in HubSpot before migration; we create all custom field definitions in HubSpot during the schema phase and map values during transform. Freshdesk contact ID is preserved in a custom HubSpot field for audit. Contact import requires at least 10 existing tickets in Freshdesk for CSV method; we use the API to bypass this gate.

1:1

### Company → Company

Freshdesk Companies map to HubSpot Companies.

How it maps

Company name, domain, industry, and custom fields migrate. The Freshdesk contact-company relationship is preserved as the HubSpot Contact-Company association at migration time. If a Freshdesk contact has no company, we create a stub Company record and link it. Companies are migrated before Contacts to satisfy the lookup dependency on insert.

1:1

### Agent → User

Freshdesk Agents map to HubSpot User records.

How it maps

We match Freshdesk agents by email against existing HubSpot Users in the destination portal. Agents who are also ticket requesters are flagged during scoping to prevent circular references. Any Freshdesk agent without a matching HubSpot User is held in a reconciliation queue; the customer's HubSpot admin provisions missing Users before record migration resumes. Agent groups and roles are documented in the migration inventory for rebuild in HubSpot Teams and permission sets.

1:1

### Conversation (Ticket Replies and Notes) → Conversation (Ticket Conversations)

Freshdesk Conversations (public replies, private notes, and incoming emails) map to HubSpot Ticket conversation records.

How it maps

Each conversation has author, timestamp, body text, and attachments. We preserve the full conversation thread ordering by timestamp. Private notes from Freshdesk migrate as internal ticket notes in HubSpot. Attachments migrate as HubSpot file attachments linked to the conversation record. HTML content is preserved and rendered in HubSpot's conversation view.

configuration

### SLA Policy → SLA Configuration

Freshdesk SLA Policies (available on Pro and Enterprise) define response and resolution deadlines.

How it maps

We audit every SLA policy definition during scoping and deliver a written mapping to HubSpot's SLA configuration. HubSpot SLAs are set at the ticket pipeline level and reference business hours. SLA policy names and definitions are preserved in a migration inventory document; the customer's admin configures the equivalents in HubSpot after migration.

******What moves 12 objects

Freshdesk HubSpot Service Hub

- Ticket Ticket 1:1
- Contact Contact 1:1
- Company Company 1:1
- Agent User 1:1
- Conversation Conversation 1:1
- SLA Policy SLA Configuration transformed

\+ 6 more in the mapping below

## How Freshdesk and HubSpot Service Hub differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                    | Freshdesk                                                                                                     | HubSpot Service Hub                                                                                                 |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Platform model               | Standalone helpdesk with per-agent pricing and optional Freddy AI add-on                                      | CRM-embedded Service Hub with per-seat pricing across Sales, Marketing, and Service hubs                            |
| Ticket-channel normalization | Phone, email, tweet, Facebook, portal, chat, forwarded email, and survey as native channels                   | Email, chat, Facebook, and Instagram as native; phone via Conversations Inbox; other channels require normalization |
| Agent licensing              | Agents as named license holders with group and role assignments                                               | Agents as HubSpot User seats; permission sets control access level across CRM and Service Hub                       |
| SLA policies                 | Per-plan SLA policies with response and resolution targets, Pro and Enterprise only                           | SLA capabilities included in Professional and Enterprise; configured per ticket pipeline                            |
| Custom objects               | Custom objects via API accessible; in-product custom objects are isolated and not programmatically accessible | Custom objects available via HubSpot's custom objects API in Professional and Enterprise                            |
| Reporting model              | Custom dashboards and analytics in Growth and above                                                           | Reports integrated with CRM reporting; pipeline analytics and CSAT in Service Hub Professional and above            |
| API rate limits              | Account-wide limits: 200/min Growth, 400/min Pro, 700/min Enterprise, with endpoint-specific sub-limits       | HubSpot CRM API at 100 calls/second per portal; Service Hub inherits the same limit                                 |

## What to watch for in a Freshdesk to HubSpot Service Hub migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Freshdesk free plan blocks all API access

Freshdesk's free plan has 0 API calls per minute and no API access whatsoever.

How we handle it

Any migration tooling that relies on the Freshdesk REST API will fail immediately on free-plan accounts. We require customers to upgrade to at least the Growth plan ($15/agent/month) before we can begin any programmatic export. We flag this during scoping and advise customers to upgrade early to avoid timeline delays. If the customer has existing paid plan contacts or companies with no paid agent seats, they may need to add at least one Growth agent seat for API access.

high

### Freshdesk endpoint-specific rate limits require query-level throttling

Freshdesk enforces rate limits account-wide with sub-limits per endpoint.

How we handle it

The Growth plan allows 200 calls/min total but the Tickets List endpoint is limited to 20 calls/min. We throttle our export queries to the tightest sub-limit per plan tier and implement exponential backoff on 429 responses. We pre-map each migration to the customer's plan tier rate limits before starting any data pull. Pro plan allows 400 calls/min with 100 list/min; Enterprise allows 700 calls/min with 200 list/min. Migrations with high ticket volumes on Growth plan require more migration windows than Pro or Enterprise.

medium

### Multi-channel source types require normalization to HubSpot equivalents

Freshdesk tickets can originate from phone, forwarded email, tweet, survey feedback, Facebook, portal, chat, and standard email.

How we handle it

HubSpot Service Hub accepts email, chat, Facebook, Instagram, and phone via the Conversations Inbox. Non-standard Freshdesk channels (tweet, survey, forwarded email, portal) are normalized to 'custom' with the original channel name preserved in a metadata field. If the customer relies on channel routing rules based on these channel types, they must be rebuilt as HubSpot workflow conditions post-migration.

medium

### In-product Freshdesk custom objects cannot be accessed programmatically

Freshdesk's custom objects created via the in-product experience (as opposed to the Custom Objects API) are isolated and cannot be accessed by external apps.

How we handle it

We confirm during scoping whether any custom objects were created in-product or via API. In-product custom objects require manual CSV export by the customer and manual entry into HubSpot. API-created custom objects migrate using Freshdesk's custom objects REST endpoints with schema pre-creation in HubSpot's custom objects API.

high

### Automations, macros, and SLA policies do not migrate as code

Freshdesk automations (triggers, workflows, supervisor alerts), macros, and SLA policies are configuration-as-code that does not transfer to HubSpot's different automation model.

How we handle it

HubSpot Service Hub uses its own workflow builder with property-triggered automations and SLA configuration. We deliver a written inventory of every Freshdesk automation and SLA policy with its trigger, conditions, actions, and a recommended HubSpot equivalent. The customer's admin rebuilds these in HubSpot post-migration. This rebuild work is outside standard migration scope.

## How the migration runs

1. ### Discovery and plan tier verification

   We audit the source Freshdesk portal across plan tier (Free/Growth/Pro/Enterprise), active agents, ticket volume, conversation history, custom fields, SLA policies, Products, and any custom objects.

   What this step covers

   We verify that the customer is on at least the Growth plan (required for API access). We confirm whether custom objects were created via API or in-product and adjust the extraction strategy accordingly. The discovery output is a written migration scope document listing all objects to migrate, their estimated counts, and the Freshdesk API credentials with plan-tier rate limit confirmation.

2. ### Schema pre-creation in HubSpot Service Hub

   Before any data moves, we create all required HubSpot objects and properties: custom contact fields, custom ticket fields, custom objects (if applicable), and tag configurations.

   What this step covers

   We also pre-map Freshdesk agents to HubSpot Users by email and flag any agent without a matching HubSpot User in a reconciliation queue for the customer's admin to provision. This step ensures that every insert during migration resolves its lookup dependencies without rejection.

3. ### Demo migration and reconciliation

   We run a representative migration of up to 100 random tickets with associated contacts, companies, conversations, and attachments into a HubSpot Sandbox or the production portal (depending on customer preference).

   What this step covers

   The customer's support manager reconciles the migrated sample against the Freshdesk source: record counts, conversation thread ordering, attachment presence, and field value accuracy. Any mapping corrections are documented and applied to the full migration configuration before the production migration begins.

4. ### Production migration in dependency order

   We run production migration in strict dependency order: Companies (from Freshdesk) first, then Contacts (with company lookup resolved), then Agents (matched to HubSpot Users), then Tickets (with requester and company lookup resolved), then Conversations (linked to tickets), then Tags, Time Entries, and Satisfaction Ratings.

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. We throttle export queries to Freshdesk's endpoint-specific rate limits with exponential backoff on 429 responses.

5. ### Cutover and delta sync

   We freeze Freshdesk writes during cutover, run a final delta migration of any tickets, contacts, or conversations modified during the migration window, and enable HubSpot Service Hub as the system of record.

   What this step covers

   The customer deactivates Freshdesk (or sets it to read-only if they are running in parallel during a transition period). We deliver the automation and SLA inventory document to the customer's admin team for post-migration rebuild in HubSpot's workflow builder.

6. ### Post-migration support and handoff

   We support a one-week hypercare window where we resolve any data quality issues raised by the customer's support team: missing conversations, duplicate records, incorrect contact associations.

   What this step covers

   We do not rebuild Freshdesk automations, macros, or SLA policies as HubSpot workflows inside the migration scope; that work is handled by the customer's admin or a HubSpot implementation partner. We provide a written handoff document summarizing the migration decisions, the object mapping summary, and the open items list.

![](https://flitstack.ai/platforms/freshdesk.svg) Freshdesk ![](https://flitstack.ai/platforms/hubspot-service-hub.svg) HubSpot Service Hub

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Service Hub Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with ticket volume, custom field count, and the number of Freshdesk objects being migrated. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Freshdesk to HubSpot Service Hub →](https://flitstack.ai/contact)

## Why teams move from Freshdesk to HubSpot Service Hub

- Teams already on HubSpot Sales or Marketing Hub migrate Freshdesk to Service Hub for unified customer context. A case study from Vested Marketing documented a team moving from Freshdesk to HubSpot specifically to align their customer support data with existing HubSpot sales and marketing tooling, enabling support reps to see full deal history and marketing engagement inside the same CRM record without a separate integration layer.
- Freshdesk's reporting capabilities fall short for teams that need cross-functional analytics. Reviewers on G2 and Capterra cite limited custom reporting depth and dashboard flexibility compared to CRM-embedded analytics. Teams requiring support metrics correlated with revenue, deal size, or customer lifetime value migrate to HubSpot's integrated reporting model where ticket data lives alongside Opportunity and Contact records.
- Freddy AI add-on pricing is per-session, creating unpredictable monthly costs that surprise teams at renewal. A G2 reviewer on the Freshdesk listing flags the separate AI billing as a cost variable that makes budgeting difficult. HubSpot Service Hub Professional includes Breeze AI capabilities for customer service as part of the seat price, removing per-session billing uncertainty for teams prioritizing AI-assisted support.
- Duplicate ticket handling in Freshdesk is a recurring complaint at volume. Multiple Reddit and community threads cite insufficient deduplication logic as a pain point during high-ticket periods, with agents spending time triaging duplicates rather than resolving issues. HubSpot's CRM-based ticket model deduplicates on contact, reducing duplicate submission surface area for teams with unified contact records.
- Freshdesk's add-on stacking for chat, advanced routing, and custom reporting makes the true cost significantly higher than the base per-agent price. A Reddit thread from a small SaaS company evaluating their second year of Freshdesk noted they were considering alternatives specifically because they were paying for modules beyond the base plan. HubSpot Service Hub bundles chat, inbox management, knowledge base, and SLA tracking into Professional tier without separate module purchases.

Questions, answered

## Freshdesk to HubSpot Service Hub migration questions

How long does a Freshdesk to HubSpot Service Hub migration take?

Most migrations land between three and five weeks for accounts under 15,000 tickets and 5,000 contacts with no custom objects or SLA policies. Migrations with custom objects, multiple Freshdesk portals, large conversation histories, SLA policy inventories, or Products-to-asset associations move to eight to twelve weeks because of Freshdesk API sub-limit throttling, parent-record resolution across linked objects, and the SLA and automation rebuild documentation scope.

Do Freshdesk automations, macros, and SLA policies migrate to HubSpot?

No. Freshdesk automations (triggers, workflows, supervisor alerts), macros, and SLA policies are configuration that does not migrate to HubSpot's different automation model. We do not rebuild them inside the migration scope. We deliver a written inventory of every Freshdesk automation and SLA policy with its trigger, conditions, actions, and a recommended HubSpot workflow equivalent. The customer's admin rebuilds these in HubSpot's workflow builder post-migration. SLA policies require manual configuration in HubSpot Service Hub Professional or Enterprise.

Can we migrate Freshdesk knowledge base articles to HubSpot?

Yes. Freshdesk Articles (knowledge base) migrate to HubSpot Knowledge Base articles. We export articles with all translations, folder hierarchy, and attachments. HubSpot's knowledge base supports categories and article status. Multi-language articles require the customer to have HubSpot Multi-Language content enabled (Professional and Enterprise). Forum Categories map to HubSpot community or knowledge base categories depending on the destination configuration.

Do we lose conversation history and attachments during migration?

No. We migrate the full Freshdesk conversation thread for each ticket: public replies, private notes, and incoming emails with full timestamps and author attribution. Attachments migrate as HubSpot file attachments linked to the conversation record. Inline images are preserved as separate file attachments. HTML content is preserved and rendered in HubSpot's conversation view. We flag any attachment that exceeds HubSpot's file size limits before migration so the customer can decide whether to exclude or compress.

What happens to Freshdesk agents who are also ticket requesters?

We flag agents who are also ticket requesters during scoping to prevent circular references. In Freshdesk, an agent can submit a ticket as a requester; in HubSpot, a User can also be a Contact. We migrate these as HubSpot Contacts with a custom flag indicating their Freshdesk agent role, and we preserve the original agent email in the User mapping for the customer's admin to reconcile permissions post-migration. The migration inventory documents which contacts require admin review for access level assignment.

What if we have Freshdesk Products associated with tickets?

Freshdesk Products are items linked to tickets for asset tracking. HubSpot Service Hub does not have a native Product object for support use cases. We offer two strategies during scoping: map Freshdesk product associations to a custom multi-select picklist on the HubSpot Contact record, or create a custom object in HubSpot for asset management linked to Contacts. The customer selects the strategy based on their asset reporting requirements. We do not create Product records in HubSpot's Sales Hub Product catalog unless the customer specifically requests that.

Can FlitStack AI migrate Freshdesk custom objects to HubSpot custom objects?

Yes, but only for custom objects created via the Freshdesk Custom Objects API. Custom objects created through Freshdesk's in-product experience are isolated and cannot be accessed by external apps. We confirm during scoping which method was used to create any custom objects. API-created custom objects migrate to HubSpot's custom objects API (available in Professional and Enterprise). In-product custom objects require manual CSV export by the customer and manual entry into HubSpot. We document the schema of both source and destination custom objects during scoping.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot-service-hub.webp) Migrate to **HubSpot Service Hub** Every source we move into HubSpot Service Hub, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/helpdesk/hubspot-service-hub)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot Service Hub and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Salesforce Service Cloud to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/hubspot-service-hub) [**Zendesk to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/hubspot-service-hub) [**Intercom to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/intercom/to/hubspot-service-hub) [**Freshdesk to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/zendesk) [**Freshdesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/intercom) [**Freshdesk to Salesforce Service Cloud** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/salesforce-service-cloud)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Batch limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/batch-limits)
3. [Batch read associations — HubSpot Knowledge Base](https://knowledge.hubspot.com/crm-setup/batch-read-associations)
4. [Import knowledge base articles — HubSpot Knowledge Base](https://knowledge.hubspot.com/knowledge-base/import-knowledge-base-articles)
5. [Import to Freshdesk — Freshworks Marketplace](https://www.freshworks.com/apps/import_to_freshdesk/)
6. [Import and export customers and company information — Freshdesk](https://support.freshdesk.com/support/solutions/articles/196491-importing-and-exporting-customer-data)
7. [Throughput and plan-tier limits — Freshdesk](https://support.freshdesk.com/support/solutions/articles/225439)

Get a quote

## Moving from Freshdesk to HubSpot Service Hub?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot Service Hub setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
