FreshdeskHubSpot

Freshdesk to HubSpot migration

Migration specialists move your tickets, replies and private notes into HubSpot, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 16 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Freshdesk to HubSpot at a glance

Leaving Freshdesk for HubSpot starts with finding the whole history: Freshdesk's ticket list looks back 30 days by default, so we read every year in date windows. Tickets then land in a Service Hub pipeline beside your CRM contacts and companies, with replies as email activities, private notes as notes and public notes clearly marked. Agents keep using Freshdesk until the catch-up sync.

Objects mapped
16
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Freshdesk support teams moving into HubSpot Service Hub so tickets, contacts and deals share one CRM, often when sales already works in HubSpot.
What does not move
Canned responses, scenario automations, dispatch and supervisor rules, SLA policies, business hours and portal themes. Each one is documented so your admin can recreate it in HubSpot.
What sets the scope
Years of ticket history, replies and notes per ticket, ticket types and products, solution articles and portals, and how many Freshdesk statuses need a HubSpot pipeline stage.

What moves

What moves from Freshdesk to HubSpot

Freshdesk tickets move into a HubSpot ticket pipeline with their replies as email activities and their private and public notes as notes, alongside contacts, companies, custom fields, files and solution articles.

  • 16 included
FreshdeskHubSpot
  • ContactsContacts

    Freshdesk keeps one contact per email, which lines up with HubSpot's email match, so existing CRM contacts are updated in place.

  • CompaniesCompanies

    Matched on domain where the Freshdesk company has one, then associated to its contacts.

  • AgentsUsers (ticket owners)

    Matched to HubSpot users by email; users are added before tickets so each keeps its owner.

  • GroupsTeams

    Set up as HubSpot teams before tickets load, so assignment by group carries over.

  • TicketsTickets

    Subject, description, priority, source, owner and stage, with the Freshdesk ticket ID kept for the catch-up sync.

  • Statuses (Open, Pending, Resolved, Closed and custom)Pipeline stages

    Each one becomes a stage marked open or closed; Resolved and Closed can stay separate stages.

  • Ticket types and productsTicket property or pipelines

    A property by default; separate pipelines where the stages differ, agreed on the call.

  • RepliesEmail activities

    Customer replies as incoming and agent replies as outgoing, at their original time.

  • Private notesNotes

    Internal in HubSpot, with author and time. Notes over 65,536 characters are scoped during the free sample.

  • Public notesNotes marked public

    Opened with a public-note marker, or loaded as outgoing email activities if you choose.

  • Attachments and inline imagesFiles

    Each file is attached to the reply or note it came with. Freshdesk's 20 MB per ticket is well inside HubSpot's per-file allowance.

  • Ticket, contact and company custom fieldsCustom properties

    Created with matching types before the records load.

  • TagsMultiple checkboxes property

    One option per tag in use on the tickets in scope.

  • CCsAssociated contacts

    Each CC'd address is associated to the ticket as a contact.

  • Solution categories and foldersKnowledge base categories and subcategories

    Folders become subcategories under their category, set up before the articles.

  • Solution articlesKnowledge base articles

    With their images; drafts stay drafts, and articles with tables are reviewed first.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Freshdesk to HubSpot as-is

Canned responses, scenario automations, dispatch and supervisor rules, SLA policies and portal themes are Freshdesk configuration, so each is written up for rebuilding in HubSpot.

Satisfaction ratingsOn request
In HubSpot: Ticket propertiesHubSpot's survey responses API cannot create responses, so each Freshdesk rating and comment is kept on its ticket.
Time entriesOn request
In HubSpot: Ticket property or noteTotal time per ticket as a number property, or each entry as a note with agent and duration.
Product portalsOn request
In HubSpot: Knowledge bases or categoriesSeveral portals become separate knowledge bases or one knowledge base with a category per product, agreed on the call.
Canned responsesNot migrated
In HubSpot: Snippets and templatesExported with their text and folders, so your team can recreate the ones still in use.
Scenario automations, dispatch and supervisor rulesNot migrated
In HubSpot: WorkflowsEach rule is written up with its conditions and actions, then rebuilt as a HubSpot ticket workflow.
SLA policies and business hoursNot migrated
In HubSpot: Help desk SLAsConfigured again in HubSpot; past SLA outcomes can move as ticket properties.
Portal themes and article URLsNot migrated
In HubSpot: Knowledge base theme and URLsHubSpot builds its own article URLs; we supply an old-to-new list for redirects.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Freshdesk to HubSpot migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We count Freshdesk tickets by year, ticket types, products and portals, and agree what public notes, time entries and satisfaction ratings become in HubSpot.

    • Access on both sides

      You0.5 day

      You share a Freshdesk API key from an admin agent and install a HubSpot app with the ticket, contact, company and file scopes. Agents are added as HubSpot users.

    • Statuses, pipelines and properties

      Both1 day

      Every Freshdesk status becomes an open or closed pipeline stage, and custom ticket, contact and company fields become HubSpot properties, before any record moves.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, weighted towards long threads, public notes and old tickets, loaded into your HubSpot help desk with ticket notifications off.

    • Sample sign-off

      You1 day

      Your team checks reply order, note types, owners and the Freshdesk date properties. HubSpot cannot patch activities by import, so this sign-off locks the mapping.

    • History load

      MigrateX2-3 days

      Freshdesk history read in date windows, then companies, contacts, tickets, replies, notes and files loaded into HubSpot in that order, within both platforms' quotas.

    • Catch-up sync

      MigrateX0.5 day

      Tickets updated in Freshdesk since the history load are refreshed on their Freshdesk ticket ID, with only new replies added.

  3. Validation

    Day 8-10

    • Count check

      MigrateX1 day

      Freshdesk tickets against HubSpot tickets per status and year, conversations against email activities and notes, and solution articles against knowledge base articles.

    • Go-live

      You1-2 days

      Your leads review a random set, ticket workflows are switched on, and Freshdesk stays available read-only, with a rollback plan, until you sign off.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 2 solved
  • 4 handled
  1. 01SolvedMost critical

    Most Freshdesk history is outside the default ticket list

    The problem

    A Freshdesk export built on the plain list call collects one month of tickets, and never more than 30,000. Everything older stays behind, and the export still reports success.

    How we handle it

    We walk your history in date windows with updated_since, count tickets per window against Freshdesk's own totals, and load nothing into HubSpot until the counts match.

    Source: Freshdesk API documentation, checked 13 Nov 2026

  2. 02Handled

    Freshdesk public notes have no public twin in HubSpot

    The problem

    Freshdesk lets an agent add a note the customer can see. In HubSpot, notes on a record are internal, and comments on a conversation only appear in the inbox and are never sent to the customer.

    How we handle it

    Public notes load as HubSpot notes that open with a clear public-note marker, so agents know the customer saw them. If your team prefers, they load as outgoing email activities instead; you choose on the scoping call.

    Source: HubSpot developer documentation, checked 15 Nov 2026

  3. 03Solved

    HubSpot's built-in Freshdesk transfer stops at records and files

    The problem

    HubSpot Smart Transfer lists Freshdesk contacts, companies, tickets, agents and groups, and only attachments for its one-time extra pass. Freshdesk replies and notes are not on the list, so tickets arrive without their threads.

    How we handle it

    MigrateX reads each ticket's conversations from Freshdesk and writes every reply and note to the HubSpot ticket timeline, so the full thread arrives with the ticket.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  4. 04Handled

    Freshdesk ticket types can use up HubSpot's pipeline allowance

    The problem

    Teams often want one HubSpot pipeline per Freshdesk ticket type or product. Seat-based HubSpot accounts get 15 custom pipelines on Starter and 100 on Professional, shared across every object, and more than one ticket pipeline needs Service Hub.

    How we handle it

    We count your Freshdesk types and products on the scoping call and propose pipelines only where the stages really differ. The rest become a ticket property your views can filter on.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  5. 05Handled

    HubSpot sets its own Close date when a ticket closes

    The problem

    HubSpot fills in a ticket's Close date when it moves from an open to a closed status, and clears it if the ticket reopens. A resolved Freshdesk ticket loaded today could look as if it closed today.

    How we handle it

    Freshdesk created, resolved and closed dates go into dedicated date properties on every ticket, and we confirm how Close date behaves on closed tickets during your free sample before reports are built on it.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  6. 06Handled

    Smart copy of Freshdesk solutions has conditions

    The problem

    HubSpot can copy articles from a Freshdesk-hosted knowledge base, but only into a knowledge base that is new or already migrated, at most 400 articles per run, and without tables.

    How we handle it

    We check which solution articles hold tables before the move, and how those tables are carried is scoped with you during the free sample. Folders load as HubSpot subcategories, in batches under 400.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

Technical profile

What makes this route technical

Freshdesk hides older tickets from its default list and caps list calls below its other API limits, and HubSpot accepts each activity once, so the mapping is proven before the full load.

Exporting from Freshdesk: the ticket list starts 30 days back
Freshdesk's list tickets call returns only tickets created in the last 30 days unless told otherwise, and stops after 300 pages, or 30,000 tickets. Earlier years are reached through the updated_since filter, one date window at a time.

Source: Freshdesk API documentation, checked 13 Nov 2026

Exporting from Freshdesk: listing tickets has its own quota
Freshdesk accounts get 100 API calls a minute on Growth, 400 on Pro and 700 on Enterprise, but listing tickets is held to 40, 100 and 200 a minute on the same plans, across the whole account.

Source: Freshdesk support documentation, checked 13 Nov 2026

Exporting from Freshdesk: each thread is read on its own
Freshdesk returns replies and notes from a separate conversations endpoint for every ticket, so a ticket with a long thread costs several calls on top of the ticket itself.

Source: Freshdesk API documentation, checked 13 Nov 2026

Why the Freshdesk list-view export falls short
A ticket export from the Freshdesk list view leaves out full conversations and archived tickets, so the file cannot carry a ticket's history.

Source: Freshdesk support documentation, checked 13 Nov 2026

Importing into HubSpot: what stops duplicates
HubSpot updates an existing record instead of creating a second one when the import carries a unique identifier: Record ID, a unique-value custom property, the email of a contact or the domain name of a company.

Source: HubSpot Knowledge Base, checked 15 Nov 2026

Importing into HubSpot: every status is open or closed
Each stage of a HubSpot ticket pipeline carries a ticketState of OPEN or CLOSED, so every Freshdesk status, custom ones included, is given one of the two before tickets load.

Source: HubSpot developer documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Freshdesk and HubSpot documentation. Each fact links its source.

Freshdesk to HubSpot questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How does HubSpot Service Hub compare with Freshdesk for a support team?

The main difference is where tickets live. In HubSpot, a ticket is a CRM record linked to the same contacts, companies and deals sales uses, with replies on its timeline; Freshdesk is a separate help desk. HubSpot's help desk workspace needs Service Hub Professional or Enterprise, so the tier is worth checking before the move.

Will Freshdesk tickets older than 30 days come across to HubSpot?

Yes, every year of them. MigrateX reads older Freshdesk history in date windows with the updated_since filter, and checks ticket counts per window against Freshdesk before anything is written to HubSpot.

Do Freshdesk replies, private notes and public notes stay separate in HubSpot?

Yes, in three recognisable forms: Freshdesk replies become HubSpot email activities, private notes become HubSpot notes, and public notes become notes that open with a public-note marker, or outgoing email activities if you prefer.

Does HubSpot Smart Transfer move Freshdesk conversations, or only tickets?

Only tickets, the records around them and attachments: HubSpot's Smart Transfer list for Freshdesk names no replies or notes. MigrateX moves the Freshdesk conversations too, each on its ticket, in order, with the agent who wrote it.

Will our Freshdesk ticket dates and statuses survive in a HubSpot pipeline?

Yes. Every Freshdesk status, custom ones included, becomes a HubSpot pipeline stage marked open or closed, and the Freshdesk created, resolved and closed dates sit in dedicated date properties. How HubSpot's own Close date behaves on those tickets is confirmed during your free sample.

Can Freshdesk solution articles move to the HubSpot knowledge base with their categories and folders?

Yes. Freshdesk solution categories stay categories and folders become subcategories in the HubSpot knowledge base, built before the articles arrive in batches of under 400. Articles holding tables are reviewed first, and article URLs change, so you get an old-to-new list for redirects.

Do Freshdesk canned responses, scenario automations and SLA policies move to HubSpot?

No, they are rebuilt. Canned responses become HubSpot snippets or templates, and scenario automations, dispatch rules and supervisor rules are written up one by one so your admin can recreate them as ticket workflows. SLA policies and business hours are configured again as help desk SLAs.

How long does a Freshdesk to HubSpot migration take, and can agents keep working?

Our default plan is about 10 business days, and agents keep answering in Freshdesk throughout. The Freshdesk side is paced by its list-tickets quota of 40 to 200 calls a minute by plan. A catch-up sync before go-live brings over anything changed during the run, so the switch happens in one planned window.

What does a Freshdesk to HubSpot migration cost?

The quote follows your Freshdesk volume: tickets with their replies, notes and files, contacts and companies, solution articles, and any portals or ticket types to consolidate. MigrateX first moves 100 of your records as a free sample, then sends a fixed quote within 24 hours.

How it compares

Four ways to run Freshdesk to HubSpot

The same data, moved four different ways. This is what changes between them.

Object coverage (cases, emails, comments, files, Knowledge)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Linked records, files and knowledge often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Public replies vs internal notes

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the HubSpot cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Freshdesk to HubSpot migration

Related routes

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your HubSpot move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.