---
title: "Migrate from Help Scout to Freshdesk | ClonePartner"
description: "There is no native migration path from Help Scout to Freshdesk. Help Scout uses a shared inbox model organized around mailboxes, customers, and conversations, w"
source: Help Scout
target: Freshdesk
canonical: "https://clonepartner.com/migrate/help-scout-to-freshdesk/"
---

# Help Scout → Freshdesk migration

Seamless Help Scout to Freshdesk migration — all records moved with accuracy and care.

## Why teams migrate from Help Scout to Freshdesk

There is no native migration path from Help Scout to Freshdesk. Help Scout uses a **shared inbox model** organized around mailboxes, customers, and conversations, while Freshdesk provides a **robust ticketing platform** with groups, custom fields, automation rules, and a hierarchical knowledge base.



The bridge between these two platforms is the API, but Freshdesk assigns **new IDs to every imported object** — you must maintain a local mapping of old Help Scout IDs to new Freshdesk IDs for every agent, contact, and ticket.



Every migration requires strict object sequencing, multipart/form-data attachment handling, and manual rebuilding of workflow automations and URL redirects.

## Key migration challenges

- **ID Remapping** — Freshdesk assigns new IDs to every object. A local mapping table of Help Scout IDs to Freshdesk IDs must be maintained throughout.
- **Attachment Handling** — Files must be downloaded from Help Scout and re-uploaded as multipart/form-data to Freshdesk. URL passing is not supported.
- **Custom Field Pre-creation** — Freshdesk custom fields for tickets, contacts, and companies must exist before import or data values are silently lost.
- **Status/Priority Translation** — Help Scout and Freshdesk use different terminology and values for status and priority that must be manually mapped in payloads.

## Entity mappings

- **Conversations** (Help Scout) → **Tickets** (Freshdesk)
- **Conversation Threads** (Help Scout) → **Ticket Conversations** (Freshdesk)
- **Conversation Attachments** (Help Scout) → **Ticket Attachments** (Freshdesk)
- **Customers** (Help Scout) → **Contacts** (Freshdesk)
- **Companies** (Help Scout) → **Companies** (Freshdesk)
- **Users** (Help Scout) → **Agents** (Freshdesk)
- **Teams** (Help Scout) → **Groups** (Freshdesk)
- **Tags** (Help Scout) → **Ticket Fields** (Freshdesk)
- **Custom Fields** (Help Scout) → **Ticket Fields** (Freshdesk)
- **Mailboxes** (Help Scout) → **Products** (Freshdesk)
- **Conversation Notes** (Help Scout) → **Ticket Conversations** (Freshdesk)
- **Customer Emails** (Help Scout) → **Contacts** (Freshdesk)
- **Webhooks** (Help Scout) → **Not Available** (Freshdesk)

## What breaks during migration

- **Agents / Users** [Direct] — Direct mapping from Help Scout users to Freshdesk agents.
- **Teams / Groups** [Direct] — Direct mapping with no transformation required.
- **Organizations / Companies** [Direct] — Direct mapping; must be created before contacts for linking.
- **Customers / Contacts** [Workaround] — Must link to correct company ID after creation; deduplication may be needed.
- **Conversations / Tickets** [Workaround] — Status and priority fields require explicit value mapping between platforms.
- **Threads / Replies** [Workaround] — Chronological ordering and reply vs note type distinction must be preserved.
- **Attachments** [Breaks] — Binary download and multipart/form-data re-upload required; slowest migration step.
- **Knowledge Base** [Workaround] — Hierarchical structure (Collections → Categories → Articles) must be preserved.
- **Saved Replies / Canned Responses** [Direct] — Direct API mapping between platforms.
- **Satisfaction Ratings** [Workaround] — Must be mapped to Freshdesk's CSAT format to preserve feedback history.

## What we migrate

### Migration Filter

- **User Selection** — Migrate tickets for specific users or agents
- **Time Range** — Migrate tickets from a specific time period
- **Conversation Type** — Filter by chat, email, or social media conversations
- **Tag-Based Selection** — Migrate tickets with specific tags only

### Data Types

- **Knowledge Base** — Articles, categories, and help center content
- **Tickets & Conversations** — Full conversation history with all metadata
- **Customer Profiles** — Customer information and interaction history
- **Automations & Macros** — Workflows, templates, and automation rules

## Complete technical guide

For a deep-dive into the technical process, data mapping, and step-by-step migration workflow, read our full guide: [The Complete Guide to Migrating from Help Scout to Freshdesk](https://clonepartner.com/blog/help-scout-to-freshdesk-migration-guide/).

## Frequently asked questions

### Who can view my data?

For each migration project, you'll be assigned a migration engineer. Only the migration engineer can view your data. No one else at ClonePartner can view your data.

### Can I sign an NDA?

If you are reaching out to us via one of our partners, we already have an NDA signed with them that unilaterally applies to all their customers. If you are reaching us directly and need an NDA signed, we'll be happy to sign your NDA or ours.

## Get a fixed-price quote

[Talk to an engineer](https://cal.com/clonepartner/meet?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Help Scout → Freshdesk migration.