---
title: "Migrate to Freshdesk: Helpdesk Migration Guide & Service"
description: "Migrating to Freshdesk? Import limits, the full migration checklist and every source FlitStack AI moves into Freshdesk, with history and rollback."
url: "https://flitstack.ai/migrations/helpdesk/freshdesk"
---

# Migrate to Freshdesk

Freshdesk is a multi-channel helpdesk whose import model rewards teams that pre-create agents, ticket fields and groups, and that treat Dispatch'r, Observer and Supervisor rules as rebuild work rather than import work.

Short answer

FlitStack AI migrates tickets, threads, and customer histories into Freshdesk from 250+ helpdesks, including Zendesk, Intercom, Kayako, Gorgias. Every field is mapped to Freshdesk's objects, history and associations come across, the Freshdesk setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See every source →](https://flitstack.ai/migrations/helpdesk/freshdesk#sources-list)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/zendesk.webp) ![](https://flitstack.ai/platforms-trim/intercom.webp) ![](https://flitstack.ai/platforms-trim/kayako.webp)

Destination Freshdesk ![](https://flitstack.ai/platforms-trim/freshdesk.webp)

Zendesk Intercom Kayako Gorgias Salesforce Service Cloud

250+ sources mapped into Freshdesk

## Systems we move into Freshdesk

The helpdesks teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[Zendesk to Freshdesk](https://flitstack.ai/migrations/helpdesk/zendesk/to/freshdesk) [Intercom to Freshdesk](https://flitstack.ai/migrations/helpdesk/intercom/to/freshdesk) [Kayako to Freshdesk](https://flitstack.ai/migrations/helpdesk/kayako/to/freshdesk) [Gorgias to Freshdesk](https://flitstack.ai/migrations/helpdesk/gorgias/to/freshdesk) [Salesforce Service Cloud to Freshdesk](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/freshdesk) [Jira Service Management to Freshdesk](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/freshdesk) [Zoho Desk to Freshdesk](https://flitstack.ai/migrations/helpdesk/zoho-desk/to/freshdesk) [![](https://flitstack.ai/platforms-trim/sysaid.webp) SysAid to Freshdesk](https://flitstack.ai/migrations/helpdesk/sysaid/to/freshdesk) [Crisp to Freshdesk](https://flitstack.ai/migrations/helpdesk/crisp/to/freshdesk) [Chatwoot to Freshdesk](https://flitstack.ai/migrations/helpdesk/chatwoot/to/freshdesk) [![](https://flitstack.ai/platforms-trim/help-scout.webp) Help Scout to Freshdesk](https://flitstack.ai/migrations/helpdesk/help-scout/to/freshdesk)

## What Freshdesk supports, and where its import tools stop

- Free tier for 1-2 agents with no credit card makes initial evaluation risk-free and appeals to startups and small support teams.
- Per-agent pricing is predictable and scales cleanly as teams grow from Growth at $15/agent/month to Enterprise at $89/agent/month.
- Freddy AI Copilot and Email AI Agent bring AI assistance without forcing a full platform switch, appealing to teams already embedded in Freshdesk.
- Multilingual help desk and customer portal features serve global SMB teams without requiring enterprise-level investment.

**REST only** API key (included on all paid plans)

**Rate limits** Account-wide per-minute limits: Free=0, Growth=200, Pro=400, Enterprise=700. Each endpoint has sub-limits (e.g., Tickets List capped at 20-200/min depending on plan).

| Object                                   | Support | Note                                                                                                                                                                                                                                                                                                                                                                                                |
| ---------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tickets                                  | full    | Tickets are the primary object. All standard fields (subject, status, priority, type, channel, source, group, agent, requester, company) are documented and stable. Conversations, attachments, and time entries nest under tickets. We map channel types explicitly for destinations that do not support all Freshdesk source channels (phone, forwarded email, tweet, Facebook, survey feedback). |
| Contacts (Requesters)                    | full    | Contacts are standard with name, email, phone, job title, company association, and language. Custom contact fields are supported via Admin > Support Operations > Customer Fields. The API exposes list and view endpoints at 20-100 calls per minute depending on plan. We bulk-fetch contacts in paginated batches respecting rate limits.                                                        |
| Companies                                | full    | Companies are a separate object linked to contacts. Import via CSV requires a company column in the contact CSV; missing company names create new company records. We preserve the contact-company relationship and map it to any CRM that uses Accounts or Organizations.                                                                                                                          |
| Agents                                   | full    | Agents are full-license users with group and role assignments. Agent groups and team structures are migrated as role maps. We flag agents who are also ticket requesters to prevent circular references in the destination system.                                                                                                                                                                  |
| Custom Fields (Ticket and Contact)       | mapped  | Custom fields must be created in the destination before import. On Freshdesk, custom fields are managed via Admin > Support Operations > Customer Fields or Ticket Fields. All custom field definitions are fetched via the API field endpoints. We map picklist values and multi-select fields with explicit value translation between source and destination schemas.                             |
| Custom Objects                           | mapped  | Custom Objects use entity storage introduced with FDK 7.3.x and are not accessible across apps. They are created via the developer platform or in-product experience and have their own REST API endpoints for CRUD operations. We read the custom object schema via the API and map each entity and relationship individually per destination. Custom Objects are only available on Pro and above. |
| Products                                 | full    | Products are used to associate items with tickets and track assets. Standard object with name, description, and status. We migrate product-to-ticket associations as ticket custom fields or linked objects depending on the destination schema.                                                                                                                                                    |
| SLA Policies                             | mapped  | SLA Policies define response and resolution times per plan tier. Only available on Pro and Enterprise plans. We audit SLA policy definitions and map them to equivalent SLA constructs in the destination platform, noting any feature gaps.                                                                                                                                                        |
| Forums (Categories and Topics)           | mapped  | Forums hold community discussions. Categories contain Topics, and Topics contain Posts. The forum structure is flat in Freshdesk. We map Forum Categories to KB Categories in destinations that support community forums and flatten nested topics as needed.                                                                                                                                       |
| Articles (Knowledge Base)                | mapped  | Articles live in categories and folders with attachments and translations. Multi-language support via .yml file upload is available. We export articles with all translations, attachments, and folder hierarchy and map them to KB Articles or Help Center articles in the destination.                                                                                                            |
| Tags                                     | full    | Tags are cross-object labels applied to tickets, contacts, companies, and solutions. The tag list is flat with no hierarchy. We migrate tags as-is and map them to equivalent tagging systems in the destination.                                                                                                                                                                                   |
| Conversations (Ticket Replies and Notes) | full    | Conversations are the messages within a ticket: public replies, private notes, and incoming emails. Each conversation has an author, timestamp, body, and attachments. We preserve full conversation threads in chronological order and map channel attribution to the destination's conversation model.                                                                                            |
| Time Entries                             | full    | Agents can log billable or non-billable time against a ticket. Time entries include duration, note, and billable flag. We migrate time entries as line items or custom fields depending on whether the destination supports native time tracking.                                                                                                                                                   |
| Satisfaction Ratings                     | full    | Post-resolution CSAT surveys generate satisfaction ratings attached to tickets. Ratings include score (satisfied/dissatisfied) and comment. We preserve satisfaction ratings as custom fields or survey objects in the destination.                                                                                                                                                                 |
| Collaborators                            | mapped  | Collaborators are view-only users who can be added to tickets to provide context without taking actions. Included up to 5,000 on paid plans. We migrate collaborators as Contacts and note their view-only role; the destination may require explicit permission mapping.                                                                                                                           |

## The Freshdesk migration guide

## Why teams migrate to Freshdesk

*The four shapes a Freshdesk migration takes, and what makes the platform easier — or harder — than the category average.*

Freshdesk is the customer-support product from Freshworks, founded in Chennai, India in 2010 by Girish Mathrubootham and Shan Krishnasamy[1](https://flitstack.ai/migrations/helpdesk/freshdesk#source-1). The company is now headquartered in San Mateo, California and went public on Nasdaq in 2021. Freshdesk sits inside a broader Freshworks suite that includes Freshservice (ITSM), Freshchat (messaging), Freshcaller (voice) and Freshsales (CRM).

The typical Freshdesk customer is a B2C or SMB support organisation — 3 to 500 agents — running inbound volume across email, web portal, social and chat without the admin overhead of Zendesk or ServiceNow. Compared with Zendesk, Freshdesk positions on simpler pricing and a flatter learning curve; compared with Help Scout or Front, it positions on a deeper automation engine and built-in Freddy AI for triage and reply suggestions.

Migration shapes that land on Freshdesk fall into four patterns. First, consolidation: replacing a stack of Zendesk plus Intercom plus a separate KB tool with Freshdesk's combined helpdesk and Solutions KB[4](https://flitstack.ai/migrations/helpdesk/freshdesk#source-4). Second, Zendesk exits — driven by pricing pressure or AI-deflection economics where Freddy Copilot replaces Zendesk AI's per-resolution fees.

Third, legacy replacements — shared Gmail inboxes, osTicket, Spiceworks or homegrown ticket systems — where the source has no real schema and the project is really a re-architecture. Fourth, M\&A integration, where an acquired business standardises onto the parent's Freshdesk. A Zendesk migration usually has clean ticket-and-user parity but messy trigger logic; a shared-mailbox migration has no schema at all.

What makes migrating to Freshdesk easier than the category average is the Sandbox feature, which builds a full replica of production configuration and lets admins dry-run schema changes and imports before pushing to live[27](https://flitstack.ai/migrations/helpdesk/freshdesk#source-27). The native Contacts and Companies CSV importer is forgiving on date formats and auto-resolves duplicates by email.

What makes it harder than the average is that Dispatch'r, Observer and Supervisor rules, Scenario Automations, SLA policies, canned responses and Solutions categories do not import — all rebuild in the admin UI. Throughput is shaped by the plan tier you sit on, and Custom Objects are Enterprise-only, capped at 20 per account[11](https://flitstack.ai/migrations/helpdesk/freshdesk#source-11).

Teams that scope the rebuild up front finish on time; teams that assume parity do not.

> Freshdesk is flexible and forgiving on the surface, but under the hood it has very clear opinions about how tickets, contacts, agents, groups, and fields fit together.

## The Freshdesk data model you need to map into

*Tickets, Contacts, Companies, Agents, Groups, Solutions and Custom Objects — the destination schema decoded.*

Freshdesk is built around a small set of standard objects with default and custom fields, plus lookup relationships. Solutions (Freshdesk's knowledge base) sits alongside the ticketing schema; Custom Objects extend it on Enterprise.

Before you can map a field on the source side, you need to know exactly which destination object the row belongs on, what fields it requires, and which value will serve as its upsert key. The table below summarises the objects you will touch in a Freshdesk migration.

| Object         | What it stores                                                             | Required                                                                        | Tier                                                                                                              |
| -------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Tickets        | Support requests across email, portal, phone, chat and social              | Requester (email or contact ID), subject, description, status, priority, source | All tiers                                                                                                         |
| Contacts       | End-users / requesters — individuals who raise tickets                     | Email (primary unique key) or phone                                             | All tiers                                                                                                         |
| Companies      | Customer organisations that contacts belong to                             | Name (unique within account)                                                    | All tiers; multi-company per contact requires the feature toggle                                                  |
| Agents         | Internal users who resolve tickets                                         | Email, name, role; occasional vs full-time flag                                 | All tiers; seat-counted                                                                                           |
| Groups         | Agent collections used by routing and SLAs                                 | Name; member agent IDs                                                          | All tiers                                                                                                         |
| Solutions (KB) | Categories → Folders → Articles, with translations                         | Category, folder, article title, body                                           | All tiers; multilingual on Growth+                                                                                |
| Products       | Lines of business in multi-product accounts                                | Name; primary email                                                             | Estate / Forest legacy; succeeded by Workspaces                                                                   |
| Workspaces     | Newer isolation model replacing multi-product                              | Workspace name; assigned agents and fields                                      | Enterprise (newer accounts)                                                                                       |
| Custom Objects | Customer-defined record types associated to tickets, contacts or companies | Schema defined first; per-field requirements                                    | Enterprise; max 20 per account, 100 fields each[11](https://flitstack.ai/migrations/helpdesk/freshdesk#source-11) |

Contacts use email as the default unique identifier — the importer overwrites an existing contact if the CSV email matches one already in the helpdesk[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9). A contact can hold a primary email plus up to nine secondary emails, allowing one person to span ten addresses[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9). Companies match on name by default and are case-insensitive on dedup.

Tickets do not have a natural unique key — Freshdesk assigns a sequential ticket ID at creation. The standard pattern is to import with a `unique_external_id` custom text field on contacts and a custom number or text field on tickets that stores the source platform's ticket number, then use that for reconciliation and any later delta sync.

When you import via CSV, Freshdesk upserts contacts and companies on their unique key: matches update, misses create. Tickets always create — there is no native upsert for ticket CSV. Custom field types determine validation; the catalogue below covers what you can model and the limits to plan around.

| Field type                                   | Limit                                                    | Notes                                                                                                                                     |
| -------------------------------------------- | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Text                                         | 255 chars (single-line); larger for paragraph            | Stores any alphanumeric string; case-preserved                                                                                            |
| Paragraph (multi-line)                       | \~64,000 chars                                           | Rich-text not supported; HTML stripped                                                                                                    |
| Number                                       | Integer; signed                                          | Numeric filters and reports supported                                                                                                     |
| Decimal                                      | Two decimal places by default                            | Locale-dependent display; store as period-separated                                                                                       |
| Date                                         | YYYY-MM-DD only                                          | Date-only; timezone-stripped — wrong format aborts import[16](https://flitstack.ai/migrations/helpdesk/freshdesk#source-16)               |
| Dropdown                                     | Up to 3 levels of nesting on dependent fields            | Dropdown values are case-sensitive — exact match required[12](https://flitstack.ai/migrations/helpdesk/freshdesk#source-12)               |
| Checkbox                                     | true / false                                             | Multi-select uses a separate field type                                                                                                   |
| Lookup relationship                          | Up to 5 associations per Custom Object                   | Custom-Native links Custom Objects to Tickets, Contacts, Companies only[13](https://flitstack.ai/migrations/helpdesk/freshdesk#source-13) |
| Custom fields per ticket / contact / company | Plan-gated: Free 0, Growth/Pro/Enterprise scale per type | Custom fields cannot be deleted once data exists; archive instead                                                                         |

Relationships in Freshdesk are modelled as lookup fields added to ticket, contact or company forms. Native objects support Custom-Native and Native-Custom associations for Tickets, Contacts and Companies only — other native objects do not participate in custom-object associations[13](https://flitstack.ai/migrations/helpdesk/freshdesk#source-13). Custom Objects support up to 5 associations each, and a Custom Object record limit is not enforced as a hard ceiling but plan-scaled throughput effectively gates it[11](https://flitstack.ai/migrations/helpdesk/freshdesk#source-11).

**20 / 100 / 5** Custom Objects per account / fields per object / associations per object Enterprise plan ceilings. Hitting any one of these forces a schema redesign — and tickets only support one custom-object lookup per ticket, which catches teams who plan a many-to-many model.

There is no native master-detail cascade-delete: deleting a parent contact does not delete its tickets — reproduce that in Workflow Automator if your source platform relied on it. Companies-to-contacts is one-to-many by default; a feature toggle enables one contact across multiple companies.

## Pre-migration prep — the work before you touch Freshdesk

*What must be true on the source, the destination, and across the team before the first row hits the import tool.*

The single best predictor of a clean Freshdesk migration is how much work you do on the source side before the first import button is pressed. Practitioners describe it plainly: teams that respect Freshdesk's schema end up with calm migrations; teams that do not spend weeks cleaning up after go-live.

> The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material that needs to be shaped to Freshdesk's expected formats — email lowercased, phone normalised to E.164 with country code (Freshdesk's phone channel requires `+14088481234` style, not `408-848-1234` [9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9)), dropdown values cased exactly as configured in the destination, dates rewritten to `YYYY-MM-DD`, agents resolved to Freshdesk agent emails.

### Source-side prep

- Audit and dedup the source contact list before export — email deduplication should be done on the source spreadsheet, not relied on at import time. Practitioners report 10–25% fuzzy-match false positives in B2B lists where two people share name + company, so dedup requires human review.
- Decide ticket scope — how much history is operationally useful? Two to five years of tickets is common; full history is technically possible but adds little value beyond about three years and substantially increases migration time and storage.
- Normalise emails to lowercase, trim whitespace, and remove role-based addresses (info@, sales@) that you do not want flooding the contact database. Freshdesk will overwrite an existing contact when an import row matches its email[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9).
- Convert dropdown values to exact destination casing — Freshdesk dropdowns are case-sensitive on import. `High` and `high` are different values; mismatches are silently dropped or fail the row[12](https://flitstack.ai/migrations/helpdesk/freshdesk#source-12).
- Stamp a stable external ID on every record in the source export — the source platform's primary key or a UUID — so re-runs, delta migrations and reconciliation are deterministic.

### Destination-side prep

- Build a Sandbox from Admin → Support Operations → Sandbox — a Sandbox is a full replica of your Freshdesk configuration used to dry-run schema changes and imports end-to-end before pushing to production[17](https://flitstack.ai/migrations/helpdesk/freshdesk#source-17).
- Provision every agent including inactive or legacy ones needed for historical ticket ownership — rows whose assigned agent does not exist at import time land unowned, which silently breaks group reporting.
- Create groups and assign agents before importing tickets, because group-based routing and SLA policies key off group membership at the moment a ticket is created or imported.
- Pre-create every custom field on the right object (ticket, contact, company) with the right type — text vs paragraph vs dropdown matters because Freshdesk will not let you change a field's type after data has been written to it[12](https://flitstack.ai/migrations/helpdesk/freshdesk#source-12).
- Define Custom Objects and their associations before importing related ticket data — Custom Object schemas must exist before records of that type can be created, and a ticket only supports one custom-object lookup per ticket[11](https://flitstack.ai/migrations/helpdesk/freshdesk#source-11) [13](https://flitstack.ai/migrations/helpdesk/freshdesk#source-13).
- Disable automations during import — Dispatch'r, Observer, Supervisor rules, Scenario Automations and email notifications should all be turned off in Admin → Workflows before you import, or every imported ticket will fire its full automation chain at customers.

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the helpdesk. Train agents on Freshdesk ticket-handling and rebuilt macros before go-live, not after. A typical Freshdesk migration runs roughly 2,000 tickets per hour through managed-migration tools, so plan the cutover window against total ticket count.

## Import mechanisms: UI wizard, CSV, and managed-migration tools

*The load paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.*

Freshdesk exposes several load paths and the right one depends on dataset size, object mix, and whether you need to re-run idempotently. The native CSV importer covers Contacts and Companies through the UI. Tickets, conversations and attachments come in through managed-migration tools that sit on top of Freshdesk and add staging, transformation and dedup layers.

### UI Import — Contacts and Companies

The native import lives under Admin → Customers → Contacts (or Companies) → Import[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9). It accepts CSV with headers that the importer auto-maps to Freshdesk fields; you can also manually adjust the mapping if column names diverge from field names[8](https://flitstack.ai/migrations/helpdesk/freshdesk#source-8). Existing contacts matched on email are overwritten by import rows, so backups before re-importing are essential.

Limits on the native CSV path are modest: the importer does not publish a hard per-file row cap but practical experience and the Freshworks marketplace `Import` app exist precisely because the native flow becomes unwieldy past a few thousand rows[5](https://flitstack.ai/migrations/helpdesk/freshdesk#source-5). Tickets are not importable through the native UI — they must come in via a managed-migration tool.

### Third-party and managed-migration tools

Several specialist managed-migration apps live on the Freshworks Marketplace, alongside generic iPaaS tools like Airbyte and Fivetran[5](https://flitstack.ai/migrations/helpdesk/freshdesk#source-5) [29](https://flitstack.ai/migrations/helpdesk/freshdesk#source-29). For one-time migrations from sources such as Zendesk, Intercom, Help Scout, Jira Service Management or shared inboxes, these tools handle ticket-by-ticket loading, conversation threading, attachment transfer and delta sync after the initial load.

For ongoing syncs (the post-migration phase), Airbyte and Fivetran become the system of integration — Airbyte's open-source Freshdesk connector lands ticket and contact data into a warehouse for analytics, and reverse-ETL flows write enrichment back into Freshdesk.

Under 5,000 contacts/companies on standard fields → native CSV import. Any ticket history, any conversation threads, or any cross-platform migration → managed-migration tool.

## Mapping your data into Freshdesk

*The longest section — because field mapping is where almost every migration that fails actually breaks.*

Mapping is where every helpdesk migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether agents can find historical tickets on day two, whether SLAs fire correctly on day five, and whether reporting trusts the data on day thirty.

Work object by object, top to bottom of the import order: Agents and Groups first (so tickets can be assigned), then Companies (so contacts can be associated), then Contacts, then Tickets and their conversation threads, then Solutions (KB), and finally Custom Object records.

### Contacts and Companies

| Source                        | Destination                           | Note                                                                                                                                                 |
| ----------------------------- | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| email                         | email (unique identifier)             | Lowercased on import; upsert key by default — match overwrites[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9)                       |
| secondary emails              | secondary\_emails (up to 9)           | One contact can hold 10 emails total[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9)                                                 |
| first / last name             | name                                  | Freshdesk stores a single `name` field; concatenate on the source side                                                                               |
| phone                         | phone                                 | Normalise to E.164 with country code (`+14088481234`) so the phone channel can match[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9) |
| company                       | company\_id (lookup) or company\_name | Import companies first; contacts resolve to the most recent matching company name                                                                    |
| view all company tickets flag | view\_all\_tickets                    | Set during import or contact cannot see organisation-level ticket lists[9](https://flitstack.ai/migrations/helpdesk/freshdesk#source-9)              |
| language                      | language                              | Two-letter code; defaults to account language if missing                                                                                             |
| time zone                     | time\_zone                            | Use the IANA format Freshdesk expects (`America/Los_Angeles`)                                                                                        |

### Tickets, conversations and threads

Tickets are the centre of gravity. Each carries a requester, subject, description (first message body), status, priority and source channel — the source value (email, portal, phone, chat, feedback widget, outbound) drives Source-based reports.

Conversations on a ticket come in two flavours: public notes (visible to the requester) and private notes (internal-only). Both carry author, body, timestamp and optional attachments. The migration pattern: create the ticket with the description as the first message, then load remaining conversation entries as notes (private and public agent notes) and replies (outbound public agent replies). Backdating `created_at` on each note keeps the thread chronological rather than collapsing to import-day[21](https://flitstack.ai/migrations/helpdesk/freshdesk#source-21).

| Source                    | Destination                                                                          | Note                                                                                                                         |
| ------------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| ticket\_id / case\_number | Custom number field: `legacy_ticket_id`                                              | Freshdesk assigns its own sequential ID — store the source ID in a custom field for reconciliation                           |
| subject / title           | subject                                                                              | Required                                                                                                                     |
| first message body        | description                                                                          | HTML accepted; inline images need attachment re-upload                                                                       |
| requester email           | email or requester\_id                                                               | Import contact first; use email if contact already exists                                                                    |
| status                    | status (numeric: 2=Open, 3=Pending, 4=Resolved, 5=Closed)                            | Map source statuses to the integer codes Freshdesk expects[19](https://flitstack.ai/migrations/helpdesk/freshdesk#source-19) |
| priority                  | priority (numeric: 1=Low, 2=Medium, 3=High, 4=Urgent)                                | Same integer-code mapping; defaults to Low if missing                                                                        |
| channel / source          | source (numeric: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedback widget, 10=Outbound) | Drives Source reports — get this right or your channel mix breaks                                                            |
| assigned agent            | responder\_id (or email)                                                             | Agent must exist in Freshdesk at import time or ticket lands unassigned                                                      |
| group                     | group\_id                                                                            | Group must exist; otherwise ticket falls into default group                                                                  |
| tags                      | tags (array)                                                                         | Free-form strings; tag spillover is a common cleanup issue post-migration                                                    |

### Solutions (knowledge base)

Freshdesk's knowledge base is Solutions, a three-level hierarchy: Category → Folder → Article. Categories group folders (often by product or audience), folders group articles, and articles carry title, HTML body, status (draft/published) and visibility (public/logged-in/agents-only).

Import KB content top-down: categories first, then folders inside each category, then articles inside each folder. Translations are imported separately per article per language code and require the article to exist in the primary language first. Inline images in article HTML must be re-uploaded as attachments — source URLs that point at the old platform's CDN will break.

### Automation rebuild — Dispatch'r, Observer, Supervisor, Scenario Automations

Freshdesk has three automation engines and none of them import — they are rebuilt by hand in Admin → Workflows. Dispatch'r fires on ticket creation (events like a new email arriving). Observer fires on ticket update (events like status changes or note additions). Supervisor is time-based and runs hourly across the helpdesk — useful for SLA escalations and stale-ticket nudges[20](https://flitstack.ai/migrations/helpdesk/freshdesk#source-20).

Scenario Automations (Freshdesk's equivalent of macros) are agent-invoked bundles of actions and likewise rebuild-only. Document every source rule with its trigger conditions and actions, group them by engine type, and rebuild in priority order — Dispatch'r first because it shapes incoming tickets, then Observer for in-flight updates, then Supervisor for time-based housekeeping, then Scenario Automations once agents start working in the system.

### SLA policies, business hours and CSAT

SLA policies are configured under Admin → Workflows → SLA Policies and combine a business-hours calendar (working days and times), a set of priority-based response and resolution targets, and an escalation chain. SLA policies do not import — recreate every policy with its priority-level targets, link each to the right business-hours calendar, and assign products or groups as scoping conditions[20](https://flitstack.ai/migrations/helpdesk/freshdesk#source-20).

CSAT ratings live on resolved tickets. Historical CSAT scores can be loaded onto migrated tickets through a managed-migration tool — this is optional and only worth doing if you need year-over-year CSAT trend reporting in Freshdesk Analytics. New CSAT surveys post-go-live are sent automatically on ticket resolution based on the survey configuration in Admin → Customer Satisfaction.

### Multi-channel inbox setup

Channel configuration is entirely UI-driven and must happen after the data import and before go-live. Email requires connecting each support address under Admin → Channels → Email with SPF/DKIM verification and forwarding from the source provider. Phone is a Freshcaller number; chat enables Freshchat; social connects Twitter, Facebook or Instagram; WhatsApp/SMS through the WhatsApp Business or SMS channel apps.

Do not enable email forwarding from production support inboxes until after the import window closes — otherwise every email forwarded during the migration creates a duplicate ticket against the contact you just imported[21](https://flitstack.ai/migrations/helpdesk/freshdesk#source-21).

### Files and attachments

Attachments on tickets are capped at 20 MB per conversation on paid plans (15 MB on legacy Sprout / trial accounts)[23](https://flitstack.ai/migrations/helpdesk/freshdesk#source-23). Larger files use the Dropbox or OneDrive integration to hotlink rather than uploading directly. During migration, attachments are downloaded from the source as binaries and re-uploaded into Freshdesk attached to the migrated ticket or note.

Attachments count against the account's overall storage allowance, which is tier-dependent. For large estates, the common pattern is: re-upload only attachments newer than 12 months, and store deep links to S3 or the original provider in a custom URL property on older tickets.

### Audit trail, ownership and original timestamps

`created_at` and `updated_at` are managed by Freshdesk — but Freshdesk allows backdating `created_at` on tickets during import so the timeline shows the original date[21](https://flitstack.ai/migrations/helpdesk/freshdesk#source-21). Freshdesk stamps the import day on most updates but preserves the original `created_at`, which means a `first_responded_at` that predates `created_at` is possible and benign[24](https://flitstack.ai/migrations/helpdesk/freshdesk#source-24).

Agent assignment during import works only if the agent email exists at the moment of import; rows whose `responder_id` cannot be resolved are imported with no agent set, which silently breaks downstream agent-based reporting. The audit log under Admin → Account → Audit Log tracks configuration changes (agent creation, automation edits, KB edits) but not granular per-field changes on individual tickets[25](https://flitstack.ai/migrations/helpdesk/freshdesk#source-25).

## The pitfalls that derail Freshdesk migrations

*Nine specific failure modes — ranked by impact, each tied to the exact Freshdesk mechanism that breaks.*

**high Automations left enabled during import**

Dispatch'r, Observer, Supervisor and Scenario Automations all fire on imported tickets if left enabled. Every historical ticket triggers its full automation chain — agent assignment emails, SLA breach alerts, escalation notifications go out to customers and agents for tickets that closed two years ago. Disable every automation rule and email notification under Admin → Workflows and Admin → Email Notifications before the first row lands, and re-enable after reconciliation.

**high Dropdown values rejected on case mismatch**

Freshdesk dropdown fields are case-sensitive. Source value `High` against destination option `high` is rejected; `Tech Support` against `Tech support` is rejected. The CSV importer aborts the row with an unclear error; programmatic loaders return `value not in available choices`. Normalise every dropdown column in the export to exactly match the destination option strings, including capitalisation, spacing and special characters[12](https://flitstack.ai/migrations/helpdesk/freshdesk#source-12).

**high Date fields require YYYY-MM-DD and abort on anything else**

Freshdesk's date custom fields accept exactly `YYYY-MM-DD`. CSV imports with `01/15/2025`, `15-Jan-2025` or ISO datetime strings fail with `Invalid date format` and the row is rejected[16](https://flitstack.ai/migrations/helpdesk/freshdesk#source-16). The error is clear when you read it but easy to miss because the importer keeps going on other rows. Rewrite every date column to `YYYY-MM-DD` in the export, and explicitly choose the date format in the import-mapping step.

**high created\_at on tickets can be backdated, but not on contacts and companies**

Tickets accept a `created_at` override during import — historical tickets show on the timeline at their original date. Contacts and Companies do not — every imported contact and company shows a `created_at` of import day in reports filtered by creation date[21](https://flitstack.ai/migrations/helpdesk/freshdesk#source-21). The mitigation is to add a `legacy_created_date` custom datetime field on Contacts and Companies, populate it from the source export, and rewrite every historical contact-cohort report to filter on the legacy field.

**medium Custom Objects cap at 20 per account with 5 associations each**

Custom Objects are Enterprise-only and capped at 20 per account, 100 fields per object, and 5 associations per object[11](https://flitstack.ai/migrations/helpdesk/freshdesk#source-11). Tickets only support one custom-object lookup field per ticket — so a many-to-many model between tickets and a custom object requires an intermediate object and complex routing rather than a clean junction table. Detect this in advance and either collapse the model or push the secondary association into a contact-level custom field.

**medium Custom field type cannot be changed after data is written**

Once a Freshdesk custom field has data in it — even one row — you cannot change its type from text to dropdown, or dropdown to text. The field has to be archived and a new field created with the right type, then data copied across via Workflow Automator or a backfill script. Teams discover this on day two when they realise a free-text product code should have been a dropdown for reporting. Lock the schema before the first import[12](https://flitstack.ai/migrations/helpdesk/freshdesk#source-12).

**medium Email channel reconnect creates duplicate tickets**

When you connect a support email channel to Freshdesk after the import, Freshdesk fetches the last 48–72 hours of messages from that inbox by default and creates tickets for each — duplicating tickets you already imported for that window[21](https://flitstack.ai/migrations/helpdesk/freshdesk#source-21). The mitigation is to either delete the over-fetched tickets created during the reconnect, or schedule the email connection to happen after the source mailbox is fully drained.

**low Sandbox is plan-gated and changes sync one-way only**

Sandbox is available on Estate / Forest legacy and Pro / Enterprise current plans, not on Growth or Free[17](https://flitstack.ai/migrations/helpdesk/freshdesk#source-17). Even on supported tiers, you build the Sandbox once as a replica, then test changes — and syncing back to production goes one direction (Sandbox → live) with conflict resolution required when a config changed on both sides. Plan for the Sandbox copy to drift if production keeps changing during migration prep.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and agents being allowed in. The reliable pattern is a three-stage approach: a demo / sample load of about 100 random tickets with stakeholder spot-checks, the full load with real-time monitoring of record counts and error rates, then a delta migration that captures everything that changed in the source during the full load.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before agents get login access.

- Total tickets imported vs source — minus deliberately excluded rows (spam, test tickets, rows older than the agreed history horizon).
- Tickets per status (Open, Pending, Resolved, Closed) vs source — a non-trivial mismatch usually signals a status integer-code mapping error.
- Tickets per priority and per source channel vs source — confirms the priority and source integer-code mappings round-tripped correctly.
- Conversation count per ticket for a 100-ticket sample vs source — confirms public and private notes attached to the right parent.
- Total contacts and companies imported vs source — checking that email-based collapse did not over-merge two distinct people sharing an inbox.
- Attachments per ticket for a 50-ticket sample — confirms the binary re-upload completed and inline images render.
- Solutions categories, folders and articles counted by hierarchy — confirms the KB tree round-tripped.
- Agent and group assignments — `GROUP BY responder_id` and confirm no ticket landed unassigned that should not have.
- CSAT scores if historical Satisfaction Ratings were loaded — confirms historical scores attached to the right tickets.

On top of reconciliation, run a manual spot-check: pick 30 random tickets across statuses and verify each against the source UI — subject, body, full conversation thread, attachments, requester, agent, status, tags. Pick five VIP tickets and trace the full conversation graph. If three or more of the 30 show non-trivial discrepancies, halt the load, fix the root cause, and re-import affected tickets by source ID.

Freshdesk does not have a native bulk-undo for imports. The real rollback strategy is: export every record to a tagged S3 bucket before the import starts, stamp every imported ticket with a `migration_batch_id` custom field, and if catastrophe strikes, bulk-delete by that batch ID and re-import from the cleaned source. Soft-deleted tickets in Freshdesk's trash retain for 30 days, providing a brief recovery window for accidental deletions[25](https://flitstack.ai/migrations/helpdesk/freshdesk#source-25).

Cutover sequencing: (1) source goes read-only; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported via the same loader; (4) reconciliation runs; (5) email forwarding repoints from source to Freshdesk support addresses; (6) automations and email notifications re-enable; (7) agents get login access and a 48-hour hyper-care window; (8) source decommission is scheduled 30 to 90 days out.

## Migration partners and tools

*Freshworks Marketplace apps, managed-migration vendors and iPaaS — what each is good for and how to choose.*

The Freshworks ecosystem has a smaller set of specialist migration vendors than Zendesk or Salesforce, but the tools that exist are mature. Wizard-driven managed-migration apps on the Freshworks Marketplace install into your Freshdesk account and walk through field mapping in a UI[5](https://flitstack.ai/migrations/helpdesk/freshdesk#source-5) [29](https://flitstack.ai/migrations/helpdesk/freshdesk#source-29) — covering Zendesk, Intercom, Help Scout, Jira Service Management, ServiceNow, Gorgias and shared inboxes as common sources.

A second band of long-running managed-migration vendors in the Freshdesk corner offers free sample migrations of around 100 tickets with associated organisations and contacts, then quotes the full migration based on record count and complexity. These tools handle ticket-by-ticket loading, conversation threading, attachment transfer and a follow-up delta migration to catch records that changed during the main load.

On the ETL and iPaaS side, Airbyte and Fivetran both have Freshdesk connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts dropdown values and resolves agent IDs in SQL, and the ongoing-sync layer that takes over once the one-time migration is complete. Workato and Tray.io are common picks where the migration is bundled with workflow-automation rebuilds.

Managed-migration cost ranges vary widely. A clean Zendesk-to-Freshdesk move under 25,000 tickets with standard fields and no Solutions content often lands in the $1,500–$5,000 range. Larger migrations with full conversation history, attachments, KB content and SLA / automation rebuild typically run $5,000–$25,000, driven by ticket count, custom-field complexity, historical depth and the integrations that need rebuilding rather than re-pointed[29](https://flitstack.ai/migrations/helpdesk/freshdesk#source-29).

For teams that want to outsource the migration end-to-end, FlitStack specialises in Freshdesk migrations and handles the field mapping, ticket-history preservation, Dispatch'r / Observer / Supervisor rebuild, Solutions KB import and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on ticket count and source platform, with separate line items for Custom Objects and SLA / automation rebuild depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Marketplace app they can drive themselves, a managed vendor handling the full project, an iPaaS-first approach, or a specialist migration partner. \[Explore FlitStack →]\(/contact)

In this guide

## Freshdesk migration checklist

An exhaustive 8-phase punch list for migrating tickets, contacts, companies, agents, knowledge base, and automations into Freshdesk without losing history or breaking SLAs. Typical timeline: 5–14 weeks.

0\. Decide & Plan 10 tasks

- **Confirm the Freshdesk plan tier and Omnichannel variant.** Free, Growth, Pro, and Enterprise gate features differently. Sandbox requires Enterprise. Custom Objects require Enterprise (20 objects, 100 fields, 5 associations cap).*If skipped: A plan-tier surprise mid-migration forces a contract amendment or strips features like sandbox testing and custom objects from scope.*
- **Decide whether Workspaces or multi-product is required.** Newer Freshdesk accounts use Workspaces to isolate brands; legacy Estate/Forest tiers used multi-product. Pick one model before configuration begins; conversion mid-flight is painful.*If skipped: Configuring single-workspace then discovering a second brand needs isolation requires rebuilding ticket fields, SLAs, and automations.*
- **Define migration scope by object.** Document explicitly which objects move: Tickets, Contacts, Companies, Agents, Groups, Solutions articles, Custom Objects, Time entries, Satisfaction ratings, Scenario Automations, Dispatch'r/Observer/Supervisor rules.*If skipped: Scope ambiguity around Custom Objects or time entries surfaces during cutover and forces emergency mapping work.*
- **Decide the historical-data window for tickets.** Two to five years of ticket history is common. Document an explicit cutoff (e.g. tickets created on or after 2022-01-01). Closed tickets older than the window stay in archived source exports.*If skipped: Pulling all-time history balloons run time; pulling too little erodes agent context for long-tail accounts.*
- **Confirm the Freshdesk data center region.** Freshworks hosts in US, EU, AU, and IN regions. Region is set at account creation and cannot be changed. Match to data-residency obligations (GDPR, regional contracts) before provisioning.*If skipped: Provisioning in the wrong region requires opening a new account and reloading every byte.*
- **Capture GDPR, HIPAA, and SOC2 obligations.** If PHI is in scope, execute a Business Associate Agreement with Freshworks before any health data lands. Document retention-policy changes that take effect at cutover.*If skipped: Loading PHI without a signed BAA creates a notifiable HIPAA breach.*
- **Assign a single accountable migration owner (DRI).** One named person owns scope, schedule, and sign-off. Multiple stakeholders may contribute, but only one person decides.
- **Document explicit out-of-scope items.** List what is NOT migrating: spam tickets, archived inactive end users, deleted KB articles, voicemails older than X months. Get sponsor sign-off on the exclusion list.*If skipped: Unwritten exclusions become user complaints in the first week after cutover.*
- **Set the cutover window and source-system freeze date.** Pick a low-ticket-volume window. Freeze must include source-system writes, automations, and integration triggers. Communicate the date to agents at least two weeks ahead.
- **Define written success criteria.** Concrete pass/fail thresholds: ticket count delta < 0.1%, KB article count exact match, attachment availability > 99.5%, zero failed agent imports, custom field coverage 100% on a 50-record sample.*If skipped: Without numeric criteria the migration is never formally complete and the team keeps firefighting.*

1\. Pre-Migration Prep 25 tasks

- **Export current source record counts as a baseline.** Capture counts for tickets (open, pending, resolved, closed), contacts, companies, agents, groups, KB categories/folders/articles, and automation rules.*If skipped: Without a baseline you cannot prove the migration was complete during Phase 6 reconciliation.*
- **Run deduplication on source contacts using email as the match key.** Normalize email case to lowercase before deduping. Freshdesk will overwrite an existing contact when a CSV import row matches an existing email, so source duplicates create silent overwrites.*If skipped: Duplicate contacts in the source produce silent merges in Freshdesk, mixing ticket histories across distinct people.*
- **Standardize phone numbers to E.164 format.** Freshdesk's phone channel requires a country code prefix. Convert 4088481234 or 408-848-1234 to +14088481234 before import.*If skipped: Phone numbers without country codes are not recognized by Freshcaller and routing breaks for inbound calls.*
- **Identify contacts with more than one email address.** Freshdesk supports one primary plus up to nine secondary emails per contact (10 total). Source rows must use the correct multi-email format in the import CSV.*If skipped: Multi-email contacts collapse to a single email and the other addresses are lost, breaking inbound email matching.*
- **Resolve missing required-field records in the source.** Find tickets, contacts, and companies missing values for any field that will be required in Freshdesk. Decide: fix in source, default at transform, or drop.*If skipped: Required-field gaps surface mid-import and halt entire batches.*
- **Archive or exclude spam, test, and bot-generated tickets.** Filter out resolved tickets older than the chosen window, test tickets, spam, and bot pings before export. Less data means faster migration and a cleaner Freshdesk on day one.
- **Inventory inline images and embedded attachments per ticket.** Note which tickets carry inline images in the body (not just attachments). These often require special handling so the inline rendering survives in Freshdesk.*If skipped: Inline images converted to broken links produce unreadable historical tickets agents cannot escalate from.*
- **Provision the Freshdesk production account.** Sign up at the correct data center region, confirm timezone, business hours, and primary language at first login. These settings affect ticket timestamps and SLA clocks.
- **Provision the Freshdesk sandbox (Enterprise plan).** Go to Admin > Support Operations > Sandbox and click Build Sandbox. A replica of production configuration is created. Wait for the admin email before testing.*If skipped: Skipping sandbox testing puts every field-mapping bug into production where rollback is expensive.*
- **Create all agents and confirm seat counts.** Include inactive or legacy agents needed for ticket ownership history. Set agent type (occasional / full-time), roles, and group memberships.*If skipped: Tickets owned by agents who do not exist in Freshdesk fall back to a default owner and break historical workload reporting.*
- **Create all groups and assign agents.** Group names and IDs become the routing target for migrated tickets. Match source group names exactly to keep mapping simple.
- **Configure global account settings before any import.** Set timezone, business hours, default ticket language, currency, and date format (YYYY-MM-DD). These influence how migrated timestamps display.*If skipped: Changing timezone after import shifts every ticket timestamp and breaks SLA reporting.*
- **Recreate all ticket custom fields with matching types.** Build dropdowns with case-sensitive values that exactly match the source values. Build dependent fields. Lock the schema before importing data.*If skipped: Importing a value into a missing custom field silently drops it; importing a value with mismatched case fails validation.*
- **Recreate all contact and company custom fields.** Build the same field types (text, dropdown, multi-select, number, checkbox, date) on Contact and Company entities to mirror the source schema.
- **Create Custom Objects and associations (Enterprise only).** Up to 20 Custom Objects per account, 100 fields each, 5 associations per object. Native objects supported for associations: Tickets, Contacts, Companies.*If skipped: Creating Custom Object schema after data import means rebuilding lookup relationships row by row.*
- **Lock immutable field types before import.** Some Freshdesk field types cannot be changed after creation (e.g. dropdown to multi-select). Decide types up front; document the schema as the contract.*If skipped: A wrong field type discovered after import forces field deletion and re-import of every affected ticket.*
- **Disable all automation engines before import.** Turn off Dispatch'r (ticket creation rules), Observer (ticket update rules), Supervisor (time-based rules), Scenario Automations, and all email notifications. Re-enable in Phase 7.*If skipped: Active rules during import spam customers with status-change emails, trigger reassignments, and inflate Freshcaller call attempts.*
- **Disable outbound email notification triggers.** Confirm under Admin > Notifications that 'New ticket created' and 'Agent reply' notifications are off during the load window.*If skipped: Migration imports trigger thousands of stale notification emails to end users, generating immediate complaint tickets.*
- **Configure ticket fields, statuses, types, and priorities.** Match source ticket workflow values exactly. If source had 'Waiting on Customer', create that status in Freshdesk; do not assume defaults.
- **Connect support email channels and verify forwarding.** Add support\@yourdomain mailboxes, configure DNS forwarding, and verify each address routes to Freshdesk. Email channels are UI-only and cannot be imported.*If skipped: Email reconnect on a previously-connected mailbox can pull the last 48–72 hours of inbox history and create duplicate tickets in Freshdesk.*
- **Communicate the source-system freeze to all agents.** Announce the freeze date, time, and what 'frozen' means: no new tickets, no field edits, no automation changes. Pin the announcement in the team chat.
- **Schedule end-user training on Freshdesk basics.** Cover the agent inbox, ticket properties, canned responses, scenario automations, and how to find migrated history. Record sessions for absent agents.
- **Designate first-responder agents for the first 48 hours post-cutover.** Two named agents who will triage user-reported data issues and escalate them. Their tickets get expedited routing during the post-cutover window.*If skipped: Without a triage owner the first surface bug becomes a Slack thread with no resolution path.*
- **Provision an admin-rights user dedicated to the migration.** All bulk imports run under this user. Keeps the audit log clean and the migration identity revocable without affecting daily users.
- **Document the rollback plan and decision threshold.** Define what conditions trigger rollback (e.g. >5% record loss, agent-blocking field error). Name the person who decides. Document the source-system unfreeze procedure.*If skipped: Without a documented rollback plan, a bad cutover devolves into ad-hoc decisions made under pressure.*

2\. Source Export 14 tasks

- **Export tickets with all standard and custom fields.** Include ticket ID, requester, agent owner, group, status, priority, type, source channel, created\_at, updated\_at, resolved\_at, closed\_at, all custom field values, and tags.*If skipped: Missing the resolved\_at or closed\_at column means migrated tickets cannot be re-stamped to the right historical state.*
- **Export ticket conversations as a separate file.** Each conversation entry needs ticket ID, author, body (HTML), public/private flag, created\_at, and attachment references. Public notes become customer-visible replies; private notes become internal notes.*If skipped: Conversations exported without the public/private flag will all import as the same visibility, leaking internal discussion to customers.*
- **Export attachments as files plus a metadata index.** Index columns: source filename, MIME type, file size, ticket ID, conversation ID, inline-or-attached flag. Confirm total volume against the 20 MB per-conversation Freshdesk limit.*If skipped: Attachments exceeding 20 MB per conversation are silently rejected at import and the corresponding ticket loses evidence.*
- **Export inline images with rewritten body references.** Walk every ticket and conversation body, identify \<img> tags, download each binary, and add the file to the attachment index keyed to its parent message.*If skipped: Inline images become broken-image placeholders if not re-uploaded and rewritten with new URLs.*
- **Export contacts and companies as separate CSVs.** Contacts: include primary email, secondary emails, phone in E.164, company ID, custom fields. Companies: include company name, domain, custom fields. Record the company-contact association.
- **Export agents with roles, groups, and reporting structure.** Agent names, emails, roles, group memberships, and agent type (occasional / full-time) are needed to recreate the team in Freshdesk before any tickets land.
- **Export the knowledge base hierarchy.** Solutions in Freshdesk follow Category > Folder > Article. Export from source preserving that depth: categories with descriptions, folders with visibility settings, articles with HTML body, status, author, and tags.
- **Export article translations and language mappings.** If the source KB has multilingual articles, capture the primary article ID and each translation's locale, title, and body. Freshdesk supports per-folder language mapping via uploaded .yml files.*If skipped: Translated articles imported without a locale tag default to the primary language and the multilingual experience breaks.*
- **Export time entries linked to tickets.** If time tracking is in scope, export with agent ID, ticket ID, billable flag, duration, executed\_at timestamp, and notes.
- **Export Satisfaction (CSAT) ratings.** CSAT can be imported, but the source export needs ticket ID, rating value, feedback text, and rated\_at timestamp.
- **Capture screenshots and configs of source automations.** Source triggers, automations, SLAs, dispatch rules, and macros will be rebuilt manually in Freshdesk. Capture exact conditions and actions for each rule.*If skipped: Without captured automation configs, the team forgets edge-case rules and customer-facing behavior subtly changes after cutover.*
- **Export the canned response / macro library.** Macros and canned responses are rebuilt in Freshdesk as Scenario Automations or Canned Responses. Capture title, body, and folder assignment.
- **Export reports and dashboard definitions.** Native Freshdesk reports differ from source-platform reports. Capture filter logic, grouping, and chart type so analytics can be rebuilt in Phase 7.
- **Record the exact timestamp of each export job.** Note start and end time of every export. The delta between this timestamp and the cutover freeze is what the final delta export must cover.

3\. Transform & Map 30 tasks

- **Build a master field-mapping spreadsheet.** One row per source field with destination Freshdesk field, transformation rule, nullability, and required-on-import flag. This becomes the contract for the rest of the migration.*If skipped: Without a written mapping, field decisions get re-debated mid-import and waste cycles.*
- **Resolve all dropdown value mismatches.** Freshdesk dropdown values are case-sensitive. Source value 'Closed Won' will not match Freshdesk choice 'closed won'. Normalize every dropdown column before import.*If skipped: Case mismatches reject entire rows silently in batch with no partial save.*
- **Decide the upsert key per object.** Contacts: email (lowercased). Companies: name or external\_id. Tickets: external\_id (stored in a custom field) to allow idempotent re-runs.
- **Decide handling for source fields with no destination equivalent.** Per field: drop, concatenate into the ticket description, or create a new custom field. Document the decision in the mapping spreadsheet.
- **Map source statuses to Freshdesk's status set.** Freshdesk default statuses are Open, Pending, Resolved, Closed. Add custom statuses to match source before mapping; do not collapse 'Waiting on Customer' into 'Pending' unless agents agree.*If skipped: Status collapsing skews SLA and reopen-rate reports for years after cutover.*
- **Map source priorities to Freshdesk's Low / Medium / High / Urgent.** Document the exact source-value-to-Freshdesk-value table. Tickets without a priority should default consistently.
- **Map source agent IDs to Freshdesk agent IDs.** Build a lookup table from source agent email or ID to the Freshdesk agent\_id returned after Phase 1 provisioning. Use this table everywhere agent attribution appears.*If skipped: Missed agent mappings dump tickets onto a default agent and erase historical workload attribution.*
- **Convert all timestamps to Freshdesk's expected format.** Dates use YYYY-MM-DD; full timestamps use ISO-8601 with timezone (e.g. 2026-05-27T14:30:00Z). Confirm the destination account timezone before conversion.*If skipped: Mixed timezone strings produce ticket events where first\_responded\_at appears before created\_at, breaking SLA calculations.*
- **Lowercase and trim every email address column.** Freshdesk treats email as a contact match key. Mixed case or trailing whitespace causes duplicate contacts on import.
- **Re-encode all text fields as UTF-8.** Non-UTF-8 bytes in ticket bodies and notes break the import parser. Re-encode CSVs as UTF-8 with byte-order-mark if your loader expects one.*If skipped: Bad encoding causes silent character corruption (mojibake) across tens of thousands of records.*
- **Escape commas, quotes, and newlines inside fields.** Wrap fields containing commas in double quotes; escape embedded quotes by doubling them. Newlines inside ticket descriptions must be preserved with proper quoting.
- **Truncate fields that exceed Freshdesk character limits.** Walk every text field's max length in Freshdesk's schema. Truncate at a UTF-8-aware boundary to avoid mid-character cuts.*If skipped: Source rows exceeding Freshdesk text limits reject the entire row, not just the long field.*
- **Reformat phone numbers to E.164.** Strip all formatting characters, infer country code from contact metadata, and prefix the country code. Reject any number that still cannot be parsed.
- **Convert HTML in ticket bodies to Freshdesk-safe markup.** Strip \<script>, normalize \<a href> attributes, and ensure inline image src attributes point at re-uploaded Freshdesk URLs (assigned in Phase 5).
- **Validate every dropdown value against its destination picklist.** For every row, confirm the dropdown column's value exists in the Freshdesk field's choice list with matching case. Reject rows that fail before submission.*If skipped: A single bad dropdown value can reject the entire ticket and block the import batch.*
- **Decide strategy for original ticket timestamps.** Freshdesk stamps newly created and updated times on most objects automatically. Capture original created\_at, updated\_at, resolved\_at into a 'Source Timestamp' set of custom fields on Tickets to preserve audit history.*If skipped: Without preserved source timestamps, all migrated tickets look like they arrived on cutover day and historical reporting collapses.*
- **Lock in the contact and company created\_at strategy.** Freshdesk does not allow backdating contacts/companies created\_at; the field is system-managed. Store original creation date in a custom field 'Source Created At' for each contact and company.*If skipped: Teams that assume created\_at is overridable discover at validation that every contact looks brand-new and account-tenure reports are wrong.*
- **Decide ticket-ownership strategy for inactive agents.** Two options: assign original owner if the agent exists in Freshdesk, or assign to a single 'Data Migration' agent for departed staff. Document the choice and apply consistently.
- **Decide attachment migration strategy.** Re-upload binaries as Freshdesk attachments (counts against per-conversation 20 MB limit) or preserve as external storage links in a custom field. Pick based on total volume.
- **Decide how to preserve the source ticket ID.** Add a custom ticket field 'Source Ticket ID' and populate during import. This becomes the upsert key for re-runs and the audit anchor for the next decade.*If skipped: Without a source-ID custom field, idempotent re-runs become impossible and any retry duplicates tickets.*
- **Reassemble ticket conversations into Freshdesk's reply and note structure.** Split each thread into two sequences: public messages become customer-visible replies; internal notes become private notes. Preserve the original chronological order across both sequences.*If skipped: Mixing public and private into a single visibility exposes internal triage notes to customers via the portal.*
- **Build the Solutions Category > Folder > Article import payload.** Freshdesk Solutions enforces a three-level hierarchy. Create categories first, then folders nested under each category (with visibility = all\_users, logged\_in\_users, or selected\_companies), then articles nested under folders. Each article carries title, description, status, and seo\_data.
- **Prepare per-folder translation .yml files for multilingual KB.** Freshdesk supports article translations via uploaded YAML files. Build one .yml per language containing labels and picklist values; upload via the Manage Translations slider after the primary article exists.*If skipped: Uploading translations before the primary article exists drops the translation silently.*
- **Plan the three-engine automation rebuild.** Freshdesk has three separate automation engines that must each be rebuilt manually: Dispatch'r (ticket-creation rules), Observer (ticket-update rules), and Supervisor (hourly time-based rules). Source platforms typically conflate these into one trigger system.*If skipped: Treating all source triggers as a single Freshdesk rule type creates rules that never fire or fire on the wrong event.*
- **Convert source macros to Scenario Automations.** Freshdesk Scenario Automations are the macro equivalent: agent-invoked bundles of field updates and replies. Recreate each source macro as a Scenario Automation under Admin > Workflows > Scenario Automations.
- **Map SLA policies to Freshdesk's SLA model.** Recreate SLA policies under Admin > Workflows > SLA Policies. Match the source policy's conditions (priority, group, source) to Freshdesk's matching criteria. Re-create response and resolution targets per priority.*If skipped: Missing SLA policies break first-response and resolution clocks for migrated open tickets immediately at go-live.*
- **Configure business hours and holiday calendars.** Business hours are tied to SLA clock calculation. Replicate source business hours and holidays under Admin > Workflows > Business Hours before SLA testing.*If skipped: Default 24x7 business hours bypass source business hours and inflate SLA pass rates artificially.*
- **Set up multi-channel inbox connections.** Freshdesk supports email, Freshcaller, Freshchat, social channels, and WhatsApp. Each channel is configured separately under Admin > Channels. Plan the order of connection to avoid premature inbound traffic.*If skipped: Connecting Freshchat before agents are trained causes live customer chats to bounce around an empty queue.*
- **Recreate the CSAT survey configuration.** Freshdesk's Satisfaction Survey settings live under Admin > Workflows > Customer Satisfaction. Configure question, rating scale, and send-on-trigger conditions to match the source survey behavior.
- **Stage Freddy AI features for post-import enablement.** Freddy Copilot, Triage, and predictive prioritization need a representative ticket history before they perform well. Plan to enable Freddy AI in Phase 7 after data lands and indexes.*If skipped: Enabling Freddy AI mid-import causes the model to train on a partial dataset and gives bad recommendations for weeks.*

4\. Sandbox Test Migration 12 tasks

- **Load a 1–5% representative sample of tickets into sandbox.** Pull tickets across the full date range, all priorities, all sources, all custom field variants. A skewed sample misses bugs that only appear at the edges.*If skipped: A sample biased toward recent tickets misses encoding bugs in legacy threads that surface in production.*
- **Validate field-by-field on 10 random sandbox tickets.** Open each ticket in the agent UI and compare every standard and custom field to the source. Confirm dropdowns show the right case, dates show the right timezone, and tags survived.
- **Test long-string and special-character edge cases.** Include tickets with emoji in the subject, embedded quotes in descriptions, 8000+ character bodies, and HTML tables in conversations. These break the most parsers.
- **Test attachments at the 20 MB per-conversation ceiling.** Load a ticket with multiple attachments totaling near 20 MB to confirm Freshdesk's upload pipeline accepts the batch and renders thumbnails.*If skipped: Discovering the 20 MB ceiling on production cutover day forces emergency re-architecture of the attachment loader.*
- **Test private vs public note visibility.** Open a sandbox ticket as a customer in the portal. Confirm internal notes are not visible and public replies are. If visibility leaks, fix the public/private routing before production.*If skipped: Internal-note leakage exposes triage commentary, escalation discussion, or competitive analysis to customers.*
- **Test relationship preservation for contact-company links.** Verify that imported contacts are associated with the right company in the sandbox and that 'view all this company's tickets' permissions work as expected.
- **Test Custom Object lookups on tickets (Enterprise).** Open a ticket that should have a Custom Object lookup populated. Confirm the lookup shows the correct related record and the data displays in the ticket pane.
- **Time the sandbox loads against the production volume.** Freshdesk imports via managed-migration apps on the Freshworks Marketplace typically process around 2,000 tickets per hour. Extrapolate to the full source volume and confirm the cutover window is realistic.*If skipped: Discovering a 100k-ticket load needs 50 hours during cutover weekend leaves no buffer for diagnosis.*
- **Test Solutions article import including translations.** Load one full Category > Folder > Article chain in the sandbox, then upload a translation .yml and verify the localized labels appear for agents in that language.
- **Get a domain expert to spot-check sandbox data.** A long-tenured support manager (someone who knows what 'right' looks like) reviews 25–50 sandbox tickets and signs off on field-by-field accuracy.*If skipped: Without a domain expert's eye, subtle data wrongness ships to production.*
- **Sandbox throughput sign-off.** Record final sandbox numbers: rows/hour, total runtime, retry count. Confirm production can absorb the load at the chosen plan tier within the cutover window.
- **Sign off the sandbox test results in writing.** The DRI plus a sponsor email attestation that sandbox results meet the success criteria from Phase 0. Production cutover starts only after written sign-off.*If skipped: Without written sign-off, scope creep continues into production and the window slips.*

5\. Production Cutover 16 tasks

- **Confirm the source-system write freeze.** Verify no new tickets, no field edits, no automation changes in the last hour of the source system. Pause inbound email forwarding from any in-scope mailbox.*If skipped: A leaked write during freeze means the delta never matches and reconciliation runs forever.*
- **Take the final delta export from source.** Re-export everything created or updated since the Phase 2 export timestamps. This delta represents the gap between baseline export and freeze.
- **Confirm Dispatch'r, Observer, and Supervisor rules are disabled.** Re-verify under Admin > Workflows that all three engines are paused. Confirm Scenario Automations are not auto-triggered (they shouldn't, but double-check).
- **Confirm outbound notifications are off.** Under Admin > Notifications, verify 'New Ticket', 'Agent Reply', and 'Status Change' emails are suppressed. Customer email is the loudest failure mode of a bad cutover.*If skipped: One enabled notification rule emails thousands of customers about 3-year-old resolved tickets.*
- **Load agents first.** Agents are referenced by every other object via agent\_id. Confirm the full agent roster exists in production before any ticket lands.
- **Load companies, then contacts, in that order.** Contacts reference company\_id, so companies must exist first. Use idempotent upserts keyed by external\_id where available.
- **Load Custom Object records before tickets that reference them.** Tickets with Custom Object lookup fields need the target record to exist. Load Custom Object data immediately after companies/contacts and before tickets.
- **Load tickets next, in chronological order.** Create each ticket keyed on the Source Ticket ID custom field. Loading chronologically keeps conversation thread reassembly straightforward.
- **Load ticket conversations after tickets.** For each ticket, load public messages and internal notes in original chronological order. Preserve the author by mapping source agent\_id to Freshdesk agent\_id.*If skipped: Mixed-order conversation loads scramble the thread display and confuse agents reading historical context.*
- **Load attachments mapped to their parent conversation.** Upload binaries against the parent conversation. Rewrite inline image src attributes in conversation bodies to the new Freshdesk attachment URLs.
- **Load time entries and CSAT ratings last.** These reference tickets that must already exist. Load time entries against their parent tickets and CSAT ratings against the matching ticket IDs.
- **Load Solutions content category-by-folder-by-article.** Categories first, folders second, articles third. Upload translation .yml files only after each article exists.
- **Capture import job IDs, row counts, and error logs at every step.** Log each batch's response with timestamp, count submitted, count succeeded, and count failed. This is the audit trail for Phase 6.*If skipped: Lost error logs mean failures get rediscovered weeks later by users instead of caught in validation.*
- **Cross-check destination counts against source counts at each step.** After each object's load, compare the Freshdesk count to the source baseline. Investigate any delta > 0.1% immediately, not at end of cutover.
- **If a load step fails mid-batch, stop and diagnose.** Do not push through partial data. Fix the transform, re-run idempotently keyed off the Source Ticket ID custom field, and continue.*If skipped: Pushing through partial data creates orphan tickets, missing attachments, and a multi-week cleanup project.*
- **Re-enable automation engines and notifications after all loads complete.** Turn Dispatch'r, Observer, and Supervisor back on, re-enable notifications, and reconnect email channels and Freshcaller. Confirm the first inbound test ticket flows correctly.

6\. Validate 23 tasks

- **Compare total ticket count per status: source vs Freshdesk.** Counts of Open, Pending, Resolved, Closed must match the source within the agreed delta threshold from Phase 0.*If skipped: Count mismatch caught a week after cutover surfaces as 'where did my ticket go?' agent escalations.*
- **Compare contact and company counts.** Pull total counts of Contacts and Companies from Freshdesk and compare to source baseline. Investigate any delta.
- **Compare KB article counts per category and folder.** Walk Solutions in Freshdesk and produce per-folder article counts; compare to source. Article-level mismatches are easier to debug than aggregate ones.
- **Compare open-ticket count for current workload.** Operationally critical: confirm agents see the same Open + Pending ticket count in Freshdesk as they did in source. Any miss creates immediate workload distortion.*If skipped: An open-ticket count delta of even 1% breaks first-response SLA reporting from day one.*
- **Cross-check 25 randomly selected tickets field-by-field.** Pull a random sample stratified across priorities, sources, and date ranges. Compare subject, description, status, priority, type, source, every custom field, requester, agent, group, tags, resolved\_at.
- **Cross-check 25 randomly selected contacts field-by-field.** Verify primary email, secondary emails, phone (E.164), company association, custom fields, and 'view all company tickets' flag.
- **Verify Source Ticket ID custom field populated on 100% of tickets.** Query Freshdesk for tickets where Source Ticket ID is null. Any null result means an import batch failed silently and needs re-run.*If skipped: Tickets without a Source Ticket ID cannot be re-imported idempotently and orphan future delta runs.*
- **Verify contact-to-company associations.** Sample 25 companies and confirm the expected contacts roll up. Confirm the 'one contact, multiple companies' configuration matches source if used.
- **Verify conversation threads attach to the right ticket.** On a sample, confirm public replies and internal notes appear in chronological order under the parent ticket with correct author attribution.
- **Verify attachments open and render.** Sample 25 attachments across PDF, image, and Office formats. Confirm each downloads cleanly and inline images render inside conversation bodies.
- **Verify Custom Object lookups resolve (Enterprise).** Open tickets with Custom Object associations and confirm the related record displays in the ticket pane with all expected fields.
- **Verify Solutions visibility settings.** Log in as an end user via the portal and confirm logged-in-only folders, company-specific folders, and public folders are exposed correctly.*If skipped: A visibility misconfiguration exposes internal KB articles to the public portal.*
- **Verify Source Timestamp custom fields preserved original dates.** Sample 25 tickets and confirm Source Created At, Source Updated At, Source Resolved At match the values from the source export.
- **Confirm data residency obligations are met.** Verify the Freshdesk account is hosted in the agreed region (US/EU/AU/IN) and any DPA or contractual region requirements are satisfied.
- **Confirm HIPAA BAA execution if PHI is present.** Verify the executed BAA covers the Freshworks entity hosting the account and that PHI handling matches the BAA's terms.*If skipped: Discovering an unsigned BAA after PHI is loaded creates a notifiable breach.*
- **Capture audit-log evidence from Admin > Audit Log.** Export the Freshdesk audit log covering the import window. It captures agent creation, automation changes, and configuration edits as evidence for SOC2/ISO27001 controls.
- **Verify SLA clocks calculate correctly on a migrated open ticket.** Pick a migrated ticket in Open status, manually re-trigger SLA evaluation, and confirm the response/resolution clocks reflect the original created\_at against the business-hours calendar.*If skipped: Wrong SLA clocks mean SLA breach reports are wrong for the entire migrated cohort.*
- **Have 5 power-user agents validate their daily workflows.** Each agent runs through: open inbox, pick a ticket, reply with canned response, change status, add private note, log time. Capture issues in a shared doc.
- **Have a manager verify reports and views.** Confirm built-in reports (Helpdesk in-depth, Tickets, Agents) show the migrated data with sensible counts. Confirm any custom views from source are recreated.*If skipped: Without manager UAT, reporting gaps surface in the first board meeting after cutover.*
- **Test inbound email arrival end-to-end.** Send a test message to each support address and confirm a ticket lands in Freshdesk with the right group, agent, and product (if multi-product).
- **Test Freshcaller / Freshchat / WhatsApp inbound flows.** For each enabled channel, place a test inbound interaction and confirm it produces a Freshdesk ticket with correct attribution.
- **Document every UAT issue and assign owners.** Even minor issues (a missing tag on 10 tickets, a wrong CSAT rating) get logged with a fix owner and a due date.
- **Get written sign-off from the migration sponsor.** Sponsor confirms the Phase 0 success criteria are met and authorizes opening the account to end users. Document the sign-off email.*If skipped: Without sign-off, users get access while issues are still open and post-cutover firefighting begins immediately.*

7\. Post-Migration Cleanup 14 tasks

- **Communicate go-live to all agents and end users.** Send login instructions, the portal URL, a link to the where-to-get-help contact, and the top three workflow differences from the old system.
- **Run role-segmented training sessions.** Separate sessions for agents (ticket lifecycle), team leads (reports and Scenario Automations), and admins (Dispatch'r / Observer / Supervisor / SLAs). Record each.
- **Set the source system to read-only.** Revoke write permissions for all but two admins. Announce the read-only date and the planned full-decommission date.*If skipped: An accidental source-system write post-cutover muddies the historical record and confuses agents who still log in by habit.*
- **Rebuild reports and dashboards in Freshdesk.** Freshdesk Analytics does not import source reports. Recreate each report using Freshdesk's report builder, validated against source numbers for the last full month.
- **Re-enable and tune Dispatch'r rules.** Walk each rebuilt rule, enable it, and watch the first 24 hours of triggered tickets to confirm correctness. Disable any rule firing unexpectedly.
- **Re-enable and tune Observer rules.** Observer fires on ticket update events. Watch the first day of update-triggered actions (status change emails, group reassignments) for misfires.
- **Re-enable and tune Supervisor rules.** Supervisor runs hourly on all tickets. Confirm the first hourly pass does not bulk-update or close historical tickets that should stay in their migrated state.*If skipped: An over-broad Supervisor rule can bulk-close thousands of migrated open tickets in a single hour.*
- **Re-publish Scenario Automations for agents.** Confirm every macro from the source library has an equivalent Scenario Automation visible to the right agent groups.
- **Reconnect integrations to other systems.** Re-enable connectors to Freshsales, Slack, calendar sync, BI tools, and any custom apps from the Freshworks Marketplace. Test each end-to-end before declaring done.
- **Enable Freddy AI features now that data is loaded.** Freddy Copilot, Triage, and predictive prioritization need migrated history to train. Enable them after the data has settled (typically 48 hours after final load) and monitor the first week of suggestions.
- **Schedule a 30-day post-migration retrospective.** Capture what worked, what bit the team, and what would be done differently. Update internal runbooks for the next migration.
- **Document the source-system decommission date.** Typically 90 days post-cutover once the retention window has fully cleared. Confirm the legal team has approved the data-deletion plan.
- **Archive source exports to long-term storage.** Keep the Phase 2 baseline export, the Phase 5 delta export, attachment binaries, and the mapping spreadsheet in a versioned bucket. Useful for forensic queries and future migrations.*If skipped: Lost source archives mean any future audit or legal question about migrated data has no source-of-truth to consult.*
- **Close out the migration project formally.** Final status report, lessons-learned doc, archive the project channel, release the migration team back to BAU.

Questions, answered

## Migrating to Freshdesk: questions

How long does migration to Freshdesk take?

Managed-migration tools typically process around 2,000 tickets per hour into Freshdesk, so a 25,000-ticket move runs roughly 12 to 15 hours of active migration plus preparation and validation. End-to-end including Sandbox dry-runs, automation rebuild, training and a 48-hour hyper-care window, plan two to four weeks.

Can I migrate from Zendesk to Freshdesk?

Yes — Zendesk is the most common Freshdesk migration source. Tickets, contacts, organisations and KB articles map cleanly, but triggers, automations, macros, SLA policies and Guide content do not transfer and must be rebuilt in Freshdesk's Dispatch'r, Observer, Supervisor and Scenario Automations engines from source documentation.

Can I migrate from Intercom to Freshdesk?

Yes, and Intercom-to-Freshdesk is a common consolidation move when teams want one platform for tickets plus chat plus a knowledge base. Conversation history, contacts and articles transfer through managed-migration tools. Watch the channel mapping carefully — Intercom conversations should land as tickets with source set to chat.

Does Freshdesk preserve original timestamps on import?

Partially. Tickets accept a \`created\_at\` override so historical tickets appear on the contact timeline at the right date. Conversation notes also accept backdated \`created\_at\`. Contacts and Companies do not — their \`created\_at\` is import day, so add a \`legacy\_created\_date\` custom field if you need historical cohort reporting.

Can I migrate Custom Objects to Freshdesk?

Yes, but Custom Objects require an Enterprise subscription. Each account is capped at 20 Custom Objects, 100 fields per object, and 5 associations per object. Tickets only support one custom-object lookup per ticket, so many-to-many models need an intermediate object. Define the schema and associations before importing records.

What happens to ticket history and conversation threads during migration?

Each ticket is created with its first message as the description, then conversation notes load as private and public notes (or replies) with backdated \`created\_at\` so the thread reads chronologically. The public-versus-private flag is preserved on each note. Attachments re-upload as binary payloads attached to the ticket or note.

Is there an undo or rollback for Freshdesk imports?

Freshdesk does not offer a native bulk-undo. Soft-deleted tickets sit in trash for 30 days, providing a short recovery window for accidental deletions. The reliable rollback pattern is to stamp every imported ticket with a \`migration\_batch\_id\` custom field, bulk-delete by that batch ID, and re-import from the cleaned source.

## Sources

1. [Freshworks — Wikipedia](https://en.wikipedia.org/wiki/Freshworks)
2. [r/SaaS — Migrating from Zendesk + Intercom](https://www.reddit.com/r/SaaS/comments/1tadxgf/migrating_from_zendesk_intercom_anyone_using_ai/)
3. [Import to Freshdesk — Freshworks Marketplace](https://www.freshworks.com/apps/import_to_freshdesk/)
4. [Freshworks Community — FreshDesk company import process](https://community.freshworks.com/ticketing-agent-productivity-11362/quirky-freshdesk-company-import-process-30181)
5. [Import and export customers and company information — Freshdesk](https://support.freshdesk.com/support/solutions/articles/196491-importing-and-exporting-customer-data)
6. [Throughput and plan-tier limits — Freshdesk](https://support.freshdesk.com/support/solutions/articles/225439)
7. [Freshworks Developer Community — Custom Object limits](https://community.freshworks.dev/t/is-there-a-limit-of-custom-objects-records-that-can-be-created/6685)
8. [Zammad — Freshdesk custom field types that cannot be mapped abort import](https://github.com/zammad/zammad/issues/4342)
9. [Associating different object types in Freshdesk](https://support.freshdesk.com/support/solutions/articles/50000004226-understanding-associations-in-custom-objects)
10. [Freshworks — Offline Events common errors (date format)](https://crmsupport.freshworks.com/support/solutions/articles/50000003699-offline-events-common-error)
11. [Set up your Sandbox account — Freshdesk Support](https://support.freshdesk.com/support/solutions/articles/233591-set-up-your-sandbox-account)
12. [Freshdesk integration reference](https://developers.freshdesk.com/api/)
13. [Creating automation rules that run on hourly triggers — Freshdesk](https://support.freshdesk.com/support/solutions/articles/37615-setting-up-automation-rules-to-run-on-hourly-triggers)
14. [Converting Support Emails into tickets — Freshdesk Support](https://support.freshdesk.com/support/solutions/articles/37541-set-up-your-support-email)
15. [Ticket attachment size limit — Freshdesk Support](https://support.freshdesk.com/support/solutions/articles/196643-what-is-the-size-limit-for-attachments-to-a-ticket-reply-)
16. [Freshworks Community — first\_responded\_at before created\_at](https://community.freshworks.com/t/43605)
17. [Track helpdesk changes using Audit Log in Freshdesk](https://support.freshdesk.com/support/solutions/articles/235745-track-changes-using-audit-log)
18. [Freshdesk Sandbox — Freshworks](https://www.freshworks.com/freshdesk/sandbox/)
19. [Freshworks Data Import to Freshdesk — Marketplace](https://www.freshworks.com/apps/help_desk_migration__import_to_freshdesk/)

Get a quote

## Moving to Freshdesk?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Freshdesk setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
