--- title: "Migrate from Freshdesk to Help Scout | ClonePartner" description: "There is no native migration path from Freshdesk to Help Scout. Freshdesk is a full-featured ticketing platform with Products, Companies, and native satisfactio" source: Freshdesk target: Help Scout canonical: "https://clonepartner.com/migrate/freshdesk-to-help-scout/" --- # Freshdesk → Help Scout migration Seamless Freshdesk to Help Scout migration — all records moved with accuracy and care. ## Why teams migrate from Freshdesk to Help Scout There is no native migration path from Freshdesk to Help Scout. Freshdesk is a **full-featured ticketing platform** with Products, Companies, and native satisfaction surveys. Help Scout is a **conversation-first platform** with mailboxes, teams, and a simpler organizational model. The fundamental gap is that Freshdesk has objects like **Products and Satisfaction Ratings** that have no direct equivalent in Help Scout — requiring creative workarounds like custom field dropdowns or private note threads to preserve the data. Every migration requires strict sequencing from agents through companies to tickets, manual mailbox and custom field setup since Help Scout's API cannot create these, and careful inbox ID mapping to prevent tickets from landing in the wrong destination. ## Key migration challenges - **Product Data Mapping** — Freshdesk Products have no Help Scout equivalent; must be migrated as custom field dropdowns or separate Docs Sites depending on usage. - **Mailbox & Field Setup** — Help Scout's API cannot create mailboxes or custom field schemas, requiring manual setup and careful ID recording before migration. - **Satisfaction Rating Preservation** — No Create endpoint exists for Help Scout Ratings; historical CSAT data must be preserved as private notes or tags on conversations. - **Inbox ID Mapping** — Manually created Help Scout mailbox IDs differ entirely from Freshdesk Mailbox IDs, requiring a strict mapping table to prevent misrouted tickets. - **Knowledge Base Hierarchy** — Freshdesk's three-level Solutions structure (Categories, Folders, Articles) must be mapped to Help Scout's different hierarchy (Collections, Categories, Articles). ## Entity mappings - **Tickets** (Freshdesk) → **Conversations** (Help Scout) - **Ticket Conversations** (Freshdesk) → **Conversation Threads** (Help Scout) - **Ticket Attachments** (Freshdesk) → **Conversation Attachments** (Help Scout) - **Contacts** (Freshdesk) → **Customers** (Help Scout) - **Companies** (Freshdesk) → **Companies** (Help Scout) - **Agents** (Freshdesk) → **Mailboxes** (Help Scout) - **Groups** (Freshdesk) → **Tags** (Help Scout) - **Ticket Fields** (Freshdesk) → **Custom Field Values** (Help Scout) - **Contact Fields** (Freshdesk) → **Customer Properties** (Help Scout) - **Email Configs** (Freshdesk) → **Mailboxes** (Help Scout) - **Canned Responses** (Freshdesk) → **Not Available** (Help Scout) - **Solution Articles** (Freshdesk) → **Not Available** (Help Scout) - **Satisfaction Ratings** (Freshdesk) → **Not Available** (Help Scout) - **Time Entries** (Freshdesk) → **Not Available** (Help Scout) - **SLA Policies** (Freshdesk) → **Not Available** (Help Scout) ## What breaks during migration - **Products** [Breaks] — No native equivalent; must choose between custom field dropdown or separate Docs Sites - **Satisfaction Ratings** [Breaks] — Cannot be created via API; must be preserved as private notes or tags losing dashboard analytics - **Mailboxes (Inboxes)** [Workaround] — Cannot be created via API; manual setup with strict ID mapping critical for ticket routing - **Custom Fields** [Workaround] — Schema must be manually recreated; field IDs recorded for programmatic value insertion - **Tickets to Conversations** [Workaround] — Require correct mailbox, customer, and user ID mapping plus tag and custom field application - **Conversations to Threads** [Workaround] — Must preserve reply types (Customer, Chat, Phone, Note) for readable chronological history - **Companies to Organizations** [Direct] — Direct mapping between Freshdesk Companies and Help Scout Organizations - **Contacts to Customers** [Direct] — Names, emails, phones, and social profiles map with Organization linking - **Agents to Users** [Direct] — Straightforward creation with Team assignment - **Canned Responses** [Direct] — Direct mapping to Help Scout Saved Replies via API ## 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 Freshdesk to Help Scout](https://clonepartner.com/blog/freshdesk-to-help-scout-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 Freshdesk → Help Scout migration.