Help Scout to Freshdesk migration
We migrate Conversations, Customers, Mailboxes, Tags, and Docs from Help Scout into Freshdesk with the Conversation-to-Ticket status translation resolved upfront, thread history including internal notes preserved through the Freshdesk Tickets API, and every Help Scout Custom Field mapped to its Freshdesk equivalent before cutover.
FlitStack AI migrates tickets, contacts, groups, agents and tags from Help Scout to Freshdesk, 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: 2-4 weeks.

What moves from Help Scout to Freshdesk?
Moving from Help Scout to Freshdesk is a data-model translation, not a record copy.
Read the full summary
Help Scout organizes support around Conversations and Mailboxes with a contact-based pricing model; Freshdesk uses Tickets and Groups with per-agent pricing. We resolve the Conversation status matrix (active, pending, closed, spam) against Freshdesk's Ticket status enumeration during scoping, migrate full thread history with internal notes intact via the Freshdesk v2 API, and map Help Scout Custom Fields to Freshdesk custom ticket fields — noting that Custom Fields are gated behind Help Scout's Plus plan and must be detected during scoping. Docs articles and Collections migrate to Freshdesk's Knowledge Base with category hierarchy preserved. Workflows and Saved Replies do not migrate as configuration; we deliver a written inventory for the admin to rebuild. Help Scout's per-account API rate limit requires chunked batch pacing on bulk runs to avoid 429 throttling mid-transfer.
Conversation → Ticket
Help Scout Conversations map to Freshdesk Tickets.
How it maps
Each conversation's thread — public replies and internal notes — migrates as a chronological comment sequence on the ticket. We translate Help Scout status (active, pending, spam, closed) to Freshdesk ticket status (open, pending, resolved, closed) using a mapping matrix defined during scoping. Closed and archived conversations migrate with their original resolved status preserved. Help Scout's unique internal Conversation ID is stored in a custom ticket field hs_conversation_id__c for cross-reference.
Customer → Contact
Help Scout Customers map to Freshdesk Contacts.
How it maps
Standard fields (email, name, phone, address, company name) transfer directly. Customer Properties custom fields (distinct from conversation Custom Fields) map to Freshdesk contact custom fields. We resolve the Freshdesk contact by email as the dedupe key to avoid duplicate records on re-migration. Note that Freshdesk uses singular Contact; Help Scout's 'Company' field on a Customer maps to the Freshdesk contact's company_name or a linked Organization record if the customer uses Freshdesk's Organizations object.
Mailbox → Group
Help Scout Mailboxes map to Freshdesk Groups.
How it maps
Each mailbox's assigned agents and routing preferences inform the Group membership during migration. Conversations tagged to or created in a specific mailbox are routed to the equivalent Freshdesk Group. Help Scout supports up to 2 mailboxes on Standard and unlimited on Plus; Freshdesk Groups are unlimited on all paid plans.
User (Agent) → Agent
Help Scout Users map to Freshdesk Agents by email match.
How it maps
Role assignment (admin, user) maps to Freshdesk agents with Agent type and Group membership. Help Scout's unlimited-user pricing means large support teams on source will map to a comparable agent count in Freshdesk at per-agent billing rates. Inactive or deleted Help Scout users are held in a reconciliation queue for the admin to provision in Freshdesk before final record import.
Tag → Tag
Tags applied across Conversations and Customers migrate to Freshdesk Tags.
How it maps
Tag assignments on conversations link to the migrated ticket via the Freshdesk Tags API. Freshdesk Tags are shared across tickets, contacts, and companies, matching Help Scout's cross-object tag model. We preserve all tag names exactly to maintain segmentation used in Help Scout Workflows — noting that the Workflow logic itself requires manual rebuild.
Custom Field (Conversation) → Custom Ticket Field
Help Scout Custom Fields (Dropdown, Single line, Multi line, Number, Date) on conversations map to Freshdesk custom ticket fields.
How it maps
We detect the source account's plan tier during scoping — Free and Standard accounts do not have Custom Fields in their schema and will skip this mapping entirely. For Plus and Pro accounts, we match field types and option lists, mapping Help Scout Dropdown options to Freshdesk dropdown custom fields with equivalent choice values. Required field flags carry over. If the Freshdesk destination plan does not support custom fields, we fall back to mapping values as tags or conversation notes.
- ConversationTicket1:1
- CustomerContact1:1
- MailboxGroup1:1
- UserAgent1:1
- TagTag1:1
- Custom FieldCustom Ticket Fieldtransformed
+ 2 more in the mapping below
How Help Scout and Freshdesk 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 | Help Scout | Freshdesk |
|---|---|---|
| Ticket model | Conversations organized by Mailbox with unique internal ID | Tickets organized by Group with customer-facing ticket number |
| Channel depth | Email and chat only; no native phone, SMS, or community forums | Native phone, email, chat, WhatsApp, Facebook, Twitter, and community forums across all paid plans |
| Custom Fields | Gated to Plus and Pro plans; per-inbox, up to 10 fields | Available on all plans; configurable at ticket and contact level |
| Knowledge base | Docs with Collections and Beacon widget; 1 site on Free | Knowledge base with categories, articles, portal, and community forums |
| Pricing model | Contact-based (customers, not users); caps on Free and Standard | Per-agent with unlimited contacts across all paid plans |
| Reporting | Basic; historical data requires manual CSV export from UI | Dashboards, CSAT, SLA, and agent reports on all paid plans |
| Automation | Automatic Workflows with triggers on Plus and Pro plans | Automations, Rules, and SLA policies from the Growth plan onward |
What to watch for in a Help Scout to Freshdesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Help Scout per-account API rate limit throttles bulk conversation export
Help Scout's API rate limit applies per account across all users, not per API key.
How we handle it
The limit is measured per 10-minute window and varies by plan. On large accounts (5,000+ conversations), we chunk migration batches to avoid hitting the 429 ceiling mid-transfer. We use exponential backoff on throttled responses and resume from the last successfully exported conversation ID. Accounts with high message-per-conversation density are particularly affected because thread body calls count toward the limit.
Freshdesk List Tickets API caps at 300 pages during export
Freshdesk's List Tickets endpoint returns paginated results capped at 300 pages regardless of per_page settings.
How we handle it
For accounts exceeding this limit, the export must proceed via the Freshdesk Admin Account Export feature (which delivers an XML file per entity) rather than the REST API. We coordinate with the customer to trigger the Admin export, receive the download link, parse the XML, and merge it with any records extracted via the API for the current period. This two-path export strategy is the only way to guarantee complete ticket history on high-volume Freshdesk accounts.
Help Scout Workflows and Saved Replies do not translate to Freshdesk equivalents
Help Scout Automatic Workflows use triggers based on conversation status, mailbox, and customer properties with nested conditional branching.
How we handle it
Freshdesk Automations and Rules use a different logic model with different action types. We do not migrate Workflows as code. We deliver a written inventory of every active Help Scout Workflow and Saved Reply with its trigger conditions, actions, and recommended Freshdesk Automation equivalent for the customer's admin to rebuild post-migration. Saved Replies migrate as Canned Responses (content only), but Workflow logic is not automatable in the migration scope.
Docs redirects require manual Freshdesk portal configuration
Help Scout Docs articles may have been linked from external sites, help center pages, or email templates.
How we handle it
When migrating Docs to Freshdesk Knowledge Base, old article URLs will change. Help Scout does not expose a Docs Redirects API endpoint, so we cannot programmatically create URL redirect rules in Freshdesk. The customer must configure Freshdesk's portal URL redirects manually, using the exported list of original Help Scout article URLs as a reference checklist. We provide the full URL map as part of the migration handoff documentation.
How the migration runs
Scoping and plan detection
We audit the source Help Scout account across plan tier (Free, Standard, Plus, Pro), inbox count, conversation volume, custom field definitions, Docs site count, active Workflow count, and saved reply inventory.
What this step covers
We detect whether Custom Fields exist in the schema (Plus/Pro only) and flag contact counts relative to the current plan's contact cap. We confirm whether internal notes are required in thread history and whether archived or spam conversations are in scope. The scoping output is a written migration specification and a line-item object count for the customer to approve before any data extraction begins.
Freshdesk destination setup
We configure the Freshdesk destination before importing any data.
What this step covers
This includes provisioning Groups to mirror Help Scout Mailboxes, setting up Agents to mirror Help Scout Users, creating ticket Status values that map to the Help Scout Conversation status matrix, defining custom ticket fields to match Help Scout Custom Fields (if applicable), and creating the Knowledge Base category hierarchy to mirror Help Scout Docs Collections. We run this in a Freshdesk trial or sandbox environment for validation before production migration.
Data extraction and transformation
We extract data from Help Scout in dependency order: Users first (for agent mapping), then Customers (for contact dedupe keys), then Mailboxes (for group routing), then Docs (for knowledge base content), then Conversations (for tickets with full thread history).
What this step covers
We transform Help Scout Conversation status values against the Freshdesk status matrix, resolve Help Scout owner email to Freshdesk agent ID, and map Help Scout tags to Freshdesk tags at the record level. Custom Field values transform using type-matched Freshdesk custom ticket fields. Internal notes flag migrates as a private Freshdesk comment.
Demo migration and reconciliation
We run a demo migration of a representative sample (typically 50-100 records per object) into the Freshdesk destination.
What this step covers
The customer's admin spot-checks migrated tickets against Help Scout source records for thread completeness, status accuracy, tag preservation, and internal note fidelity. Any mapping corrections — particularly around custom field type mismatches, status translation, and Docs category placement — are applied before the full migration. We do not proceed to production migration until the customer signs off on the demo results.
Production migration and delta sync
We run the full production migration in record-dependency order: Agents, Contacts, Groups, Knowledge Base articles, then Tickets.
What this step covers
Each object phase emits a row-count reconciliation report before the next phase begins. During the production migration window, any new Help Scout conversations created after the extraction snapshot are held for a delta sync phase run immediately before cutover. We pace extraction against Help Scout's per-account rate limit using chunked batch processing and exponential backoff to avoid 429 throttling on large accounts.
Cutover and handoff documentation
We freeze Help Scout as the system of record, run the final delta migration of any records created during the migration window, then hand off to the customer to update DNS and email routing to point to Freshdesk.
What this step covers
We deliver the Migration Handoff Package: a complete object count reconciliation report, a Help Scout Workflow inventory with Freshdesk Automation equivalents, a Docs URL map for redirect configuration, and a Saved Reply-to-Canned Response content map. We support a three-day post-cutover window for the customer to raise reconciliation issues before closing the engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with conversation volume, custom field count, and whether Docs migration is in scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Help Scout to Freshdesk →Why teams move from Help Scout to Freshdesk
- Teams needing voice, phone, or community forums hit a hard ceiling in Help Scout, which supports only email and chat natively. Freshdesk bundles phone (via Freshcaller), WhatsApp, Facebook, Twitter, and community forums at Growth tier and above without requiring third-party integrations. Reviewers on G2 and comparison sites cite the absence of a native phone channel as the reason they moved for omnichannel consolidation.
- Help Scout recently restructured pricing toward a per-customer-interaction model, making costs less predictable for growing support orgs. Reddit discussions and G2 reviews from mid-2025 document teams receiving notification of significant price changes that broke their forecasting. Freshdesk's per-agent model with unlimited contacts on all paid plans offers more predictable cost scaling for teams that handle high conversation volume.
- Freshdesk's reporting and analytics outpace Help Scout's basic dashboards. Teams managing high ticket volumes cite the need for SLA tracking, agent workload dashboards, CSAT trends, and custom report builders as a reason for switching. Help Scout's reporting requires manual CSV exports for historical data and lacks real-time or custom segmentation.
- Contact-based billing on Help Scout's Free and Standard plans (50 and 100 contacts respectively) causes unexpected bill spikes when teams import historical customer records from a previous platform. The contact cap does not apply to users (Help Scout uses unlimited-user pricing) but catches teams migrating from Zendesk or Freshdesk where contact records are plentiful. Freshdesk charges per agent with no contact cap, removing this billing variable.
- Custom Fields in Help Scout are gated behind the Plus plan ($83/month), which surprises teams on Standard that have been using custom field data in their current platform. Freshdesk exposes custom ticket fields and contact fields on Growth and above at no extra charge, making the feature more accessible for teams with segmented support workflows.
Questions, answered
Help Scout to Freshdesk migration questions
How long does a Help Scout to Freshdesk migration take?
Most migrations land between two and four weeks for accounts under 5,000 conversations with no custom fields and a single Docs knowledge base. Accounts with 5,000-25,000 conversations, custom fields, multi-mailbox routing, and a full Docs migration extend to four to eight weeks because of thread history extraction pacing against the Help Scout per-account API limit and the Docs hierarchy mapping. Large enterprise accounts with 25,000+ conversations or multiple Docs sites may require a longer engagement scoped separately.
Do Help Scout Workflows and Saved Replies migrate to Freshdesk?
Help Scout Workflows do not migrate as automation configuration. The conditional logic models differ significantly between platforms, and we do not write automation code as part of the migration scope. We deliver a written Workflow inventory listing every active Help Scout Workflow with its trigger, conditions, and a recommended Freshdesk Automation equivalent for the customer's admin to rebuild. Saved Replies migrate as Canned Response content (shortcut text and folder) but without any Workflow dependency. Docs Redirects also require manual Freshdesk portal configuration; we provide the full original-to-new URL map in the handoff package.
Can we keep Help Scout Docs while migrating conversations to Freshdesk?
Yes. A common partial-migration pattern is to move conversations, contacts, and agents to Freshdesk while maintaining Help Scout Docs as the knowledge base. We scope the Docs migration separately during discovery and can exclude Docs from the production migration if the customer chooses to keep Help Scout Docs running alongside Freshdesk. We flag that Help Scout Docs is separately priced ($20/month per additional site on annual) and that the customer should evaluate whether consolidating knowledge bases into Freshdesk's built-in Knowledge Base reduces total platform cost.
Do internal notes from Help Scout conversations migrate to Freshdesk?
Yes. Help Scout internal notes migrate as private comments on Freshdesk tickets. We flag these as private during import using the Freshdesk Tickets API's private comment flag so that agent visibility rules are respected in Freshdesk. Internal note attribution (which Help Scout user added the note) maps to the equivalent Freshdesk agent. Customers should confirm during scoping that internal notes are required in the migration scope, as this affects extraction time and storage in the destination.
What reporting data can be migrated from Help Scout to Freshdesk?
Help Scout reporting data — CSAT scores, response time metrics, happiness ratings, and channel-specific analytics — is not accessible via the Help Scout API and cannot be migrated programmatically. We ask customers to export historical Reports data manually from Help Scout's Reports UI (CSV or XLSX) before migration if they need to preserve it. Freshdesk's reporting starts fresh from the migration cutover date. Customers who rely heavily on Help Scout historical reporting should export and archive that data separately and plan to build Freshdesk-native reports post-migration.
Can FlitStack AI migrate to Freshdesk from multiple Help Scout accounts simultaneously?
Yes. If the customer operates multiple Help Scout accounts (for example, one per brand or region), we can consolidate data from all source accounts into a single Freshdesk destination. Each source account's conversations, contacts, and agents migrate into the unified Freshdesk instance with a source-account tag applied for segmentation. We handle the multi-account scoping in a single discovery phase and produce one consolidated migration specification before proceeding.
Related migrations
Sources: official documentation
- Import to Freshdesk — Freshworks Marketplace
- Import and export customers and company information — Freshdesk
- Throughput and plan-tier limits — Freshdesk
- Associating different object types in Freshdesk
- Freshdesk integration reference
- Ticket attachment size limit — Freshdesk Support
- Freshworks Data Import to Freshdesk — Marketplace
Get a quote
Moving from Help Scout to Freshdesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.
Get a quote