Help Scout to Freshdesk Migration (and Freshdesk to Help Scout): What Moves and How

Help Scout and Freshdesk can migrate data in either direction, but they organise it differently. Conversations and tickets, customers and contacts, tags, attachments and knowledge base articles move. Help Scout inboxes map to Freshdesk groups and support email addresses, Help Scout Docs collections map to Freshdesk Solutions categories, and saved replies map to canned responses. Workflows, automations, custom field definitions, SLAs and reports have to be rebuilt by hand, whichever way you go.

This guide covers the mapping for both directions, the export and import routes each product actually supports, and a cutover plan. For the product decision itself, see our Freshdesk vs Help Scout comparison.

How do Help Scout and Freshdesk differ?

Help Scout is built to feel like shared email. Work happens in inboxes (formerly called mailboxes), each tied to an email address. A conversation contains threads: customer messages, replies and notes. Statuses are simple: active, pending and closed. The knowledge base is Docs, organised as sites, collections, categories and articles.

Freshdesk is a ticketing system. Tickets belong to groups and carry a richer status, priority, type and field model. Tickets contain conversations (replies and private notes). Automation is split across ticket creation rules, update-triggered rules and time-triggered rules. The knowledge base is Solutions, organised as categories, folders and articles.

So the migration question is mostly about structure. How should each Help Scout inbox show up in Freshdesk, and how should three status values expand into four or more?

What maps to what between Help Scout and Freshdesk?

Reverse the table for Freshdesk to Help Scout. The awkward rows flip: Freshdesk’s richer field and status model has to collapse into Help Scout’s simpler one, and Help Scout’s own documentation says custom fields, ticket types and custom statuses have no direct equivalent there.

How do you export data from Help Scout?

Help Scout is clear about this in its data export documentation: apart from report exports, the API is the only way to get data out.

• Report exports. CSV or XLSX from the All Channels, Email, Company and Happiness reports. These do not include conversation thread contents, so they are no use for a migration beyond checking counts.
• Inbox API. Conversations, threads, customers and users. This is what migration tools use.
• Docs API. All Docs articles.
• Customer list on request. Account owners can ask support for a CSV of customer names and emails, without conversation history.

How do you export data from Freshdesk?

Freshdesk gives you more options:

• Account export. From Admin, Account, Account Details, Export, an account admin receives an XML export of account data including tickets and solution articles, as described in Freshdesk’s support article. Take this first as a backup.
• Ticket list export. CSV or Excel of ticket fields, without conversation threads.
• Freshdesk API. Tickets, conversations, contacts, companies and solutions. Per the Freshdesk API docs, ticket listing returns only the last 30 days by default, so use updated_since for history, and a single list query is capped at 300 pages. Rate limits depend on plan, listed at 100 calls per minute on Growth, 400 on Pro and 700 on Enterprise, with lower sub-limits for ticket listing.

For an API-driven Freshdesk export migration, the rate limit is usually what sets the timeline on large accounts. Run extraction outside business hours if your agents also use apps that call the API.

Help Scout to Freshdesk: the steps

1. Inventory Help Scout. Inboxes, users, workflows, saved replies, tags, custom fields, Beacon settings and Docs structure. Export what you can for reference.
2. Build Freshdesk. Create a group and support email address for each inbox you are keeping, add agents, create ticket fields and decide the status mapping. Create Solutions categories and folders.
3. Choose the route. Your own scripts (Help Scout Inbox and Docs APIs out, Freshdesk API in), or a migration service such as Help Desk Migration that supports Help Scout as a source and Freshdesk as a target. Run the service’s demo migration on real records.
4. Sample migration. 20 to 100 conversations from each inbox, including long threads, notes, attachments and custom field values. Check that each landed in the right group with the right status.
5. Rebuild automation. Recreate Help Scout workflows as Freshdesk automation rules, saved replies as canned responses, and your SLA policy.
6. Move Docs. Migrate articles, decide which single folder each multi-category article belongs in, fix links, and redirect old Docs URLs.
7. Cut over. Point each support address’s forwarding at Freshdesk, replace Beacon with the Freshdesk widget, run a delta migration, and keep Help Scout readable until counts are verified.

Our guide to leaving Help Scout covers the decision side of this move.

Freshdesk to Help Scout: the steps

The reverse direction has a native path. Help Scout’s import documentation describes imports run through its partner Import2, available to account owners and administrators on Standard, Plus and Pro plans. Imports of up to 500,000 records are free when started from inside Help Scout; above that, Help Scout lists $500 per 500,000 records.

What that import covers and does not:

• Moves: emails or tickets with their customer profiles and tags.
• Does not move: users and inbox settings (create them first so data maps correctly), knowledge base articles (use the Docs API), saved replies, macros, ticket rules and automations (rebuild as saved replies and workflows), and custom fields, ticket types and custom statuses.

Help Scout’s own tips are worth following: tag records in the old help desk with something like imported before the sample run, redirect email forwarding before the full import, schedule the full import for a quiet period, and have the team stop working in Freshdesk once it starts.

Two Freshdesk-specific cautions. First, collapse your Freshdesk groups into a sensible number of Help Scout inboxes before importing, because each inbox adds cost on lower tiers: Help Scout’s pricing page lists two inboxes on Standard, with extras at $10 per month. Second, move Solutions articles separately and set redirects, or your help centre traffic will hit dead links. Our Freshdesk migration guide has the export checklist.

Which direction makes sense?

• Help Scout to Freshdesk usually happens when a team outgrows simple workflows and needs richer routing, ticket fields, multiple SLA policies or more channels. See Freshdesk alternatives and fit.
• Freshdesk to Help Scout usually happens when Freshdesk’s breadth has become overhead, or after a price change. Our Help Scout migration guide covers what leaving it involves.

On price, neither is automatically cheaper. Freshdesk lists Growth at $19, Pro at $55 and Enterprise at $89 per agent per month billed annually on its pricing page. Help Scout lists Standard at $25, Plus at $45 and Pro at $75 per user per month, with a free plan for up to five users capped at 100 contacts a month. Price the tier you would actually need, including AI add-ons. Our helpdesk migration checklist lists the costs that tend to appear after the move, and the Freshdesk to HubSpot guide covers a different destination for Freshdesk data.

Can you avoid the gap during cutover?

The week of a helpdesk switch is when response times slip: agents are learning the new tool, email forwarding is changing, and the knowledge base is between homes.

An AI resolution layer that sits alongside the helpdesk rather than inside it can keep customers answered through that period. Fidiora connects to Help Scout and Freshdesk, answers repetitive questions from your docs with cited sources, and creates a ticket in whichever helpdesk is live when a person is needed. You can connect your knowledge sources once and keep them connected while the helpdesk underneath changes. Pricing is $0.69 per genuine resolution, dropping to $0.45 above 1,000 a month, with no seat fees and free handoffs.

If your reason for switching is the size of the queue rather than a missing feature, it is worth measuring how much of that queue an AI layer resolves before you pick the destination, because it changes the seat count on either side.