Skip to content
Get a quote

Chatwoot to Freshdesk migration

We migrate Conversations, Contacts, Messages, and Labels from Chatwoot into Freshdesk Tickets with full message thread chronology preserved, inbox channels remapped to Freshdesk product types, and every Custom Attribute recreated in the destination schema before any record import begins.

Short answer

FlitStack AI migrates tickets, contacts, conversations, products and agents from Chatwoot to Freshdesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-3 weeks.

By

Source Chatwoot
DestinationFreshdesk
TicketContactConversationProductAgent
Mapped field by field · sample run · one-click rollback

What moves from Chatwoot to Freshdesk?

Moving from Chatwoot to Freshdesk is a structural translation from Chatwoot's conversation-centric model to Freshdesk's ticket-centric model.

Read the full summary

Chatwoot organizes support around Inboxes and Conversations with a single message thread; Freshdesk organizes around Tickets with a structured conversation log that separates public replies from internal notes. We preserve message order using created_at timestamps, split Chatwoot's assignee and team model into Freshdesk's agent and group structure, and map Chatwoot Labels to Freshdesk Tags at the ticket level. We flag that Automation Rules, SLA Policies, Help Center Articles, and Teams require Business or Enterprise tier on the source and may not exist in the export; we document their existence and deliver a written reconstruction guide for each. Freshdesk's API access requires Blossom tier or higher, and rate limits cap at 3,000 calls per hour on Blossom, requiring batch chunking during migration. Workflows, canned responses logic, and reporting dashboards do not migrate; we deliver a written inventory for the customer's admin to rebuild in Freshdesk's automation builder.

1:1

Conversation → Ticket

Chatwoot Conversations map to Freshdesk Tickets.

How it maps

We preserve conversation status (open, resolved, pending) as Freshdesk Ticket status values, priority mapping from Chatwoot priority to Freshdesk priority (urgent, high, medium, low), assignee mapping from Chatwoot assignee_id to Freshdesk responder_id, and team-to-group resolution where Chatwoot Teams exist on Business+ source plans. Label taxonomy migrates to Freshdesk Tags on the ticket record. The conversation created_at timestamp becomes Ticket created_at; last_message_at becomes Ticket updated_at. Private notes from Chatwoot map to Freshdesk's internal notes using message_type = 'note' on the conversation_message.

1:1

Contact → Contact

Chatwoot Contact records (name, email, phone, custom_attributes) map directly to Freshdesk Contact.

How it maps

The Contact email field is the dedupe key. Chatwoot custom_attributes that attach to Contacts migrate to Freshdesk custom contact fields, which must be pre-created in the Freshdesk schema before import. Chatwoot Contact avatar URLs migrate as contact avatar URLs in Freshdesk if the destination plan supports avatar uploads.

1:N

Message → Conversation

Chatwoot Messages nest inside Conversations as conversation_message records.

How it maps

We flatten the message array and write each message as a Freshdesk Conversation entry (public reply or private note) using the message_type field (incoming/outgoing = public note; activity = internal note). Message created_at timestamps preserve chronological order in Freshdesk's conversation timeline. Attachments migrate as conversation attachment URLs linked to the Freshdesk conversation record. Chatwoot's sender_type (agent vs customer) maps to Freshdesk's body_text_type (reply vs note) to preserve agent-versus-customer attribution.

configuration

Inbox → Product

Chatwoot Inboxes (Website Live Chat, Email, WhatsApp, Facebook, Twitter, API) map to Freshdesk Products (channel configurations).

How it maps

Channel credentials (webhook URLs, page tokens, WhatsApp business account tokens, API keys) are credentials-bound and do not transfer between platforms. We document the inbox type and name from Chatwoot so the customer's admin can configure the corresponding Freshdesk Product with matching channel type at the destination. The live chat widget code snippet does not migrate; Freshdesk provides its own widget script that replaces Chatwoot's widget on the website.

1:1

Agent → Agent

Chatwoot Agents (user accounts with email, name, role, and availability status) map to Freshdesk Agents.

How it maps

We match by email address during import. Chatwoot role values (agent, administrator) map to Freshdesk Role permissions. Agent passwords do not transfer; Freshdesk sends invitation emails to migrated agents. If a Chatwoot agent account is inactive, we create the Freshdesk agent as inactive pending the customer's decision on provisioning.

1:1

Team → Group

Chatwoot Teams (Business tier and above) map to Freshdesk Groups.

How it maps

Teams group agents and route conversations in Chatwoot; Groups serve the same routing function in Freshdesk. If the source Chatwoot plan is Hacker or Startups, no Teams exist in the export and this mapping step is skipped. We create Freshdesk Groups using the Team names from Chatwoot and map agent memberships to Group membership. Team-level routing rules are documented separately as Freshdesk Group assignment automations for the customer's admin to rebuild.

What moves10 objects
ChatwootFreshdesk
  • ConversationTicket1:1
  • ContactContact1:1
  • MessageConversationtransformed
  • InboxProducttransformed
  • AgentAgent1:1
  • TeamGroup1:1

+ 4 more in the mapping below

How Chatwoot and Freshdesk differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionChatwootFreshdesk
Record modelConversations with full message thread and assigneeTickets with conversation log separating public and private notes
Agent groupingTeams (Business+) and individual agentsGroups and agents with role-based permissions
Channel modelInboxes (live chat, email, WhatsApp, API, Facebook, Twitter)Products (Channel-specific email, phone, chat, messaging, WhatsApp, Facebook, Twitter) with unified ticket queue
AI toolingCaptain AI credit model ($20/1,000 credits) with summarization and reply suggestionsFreddy AI Copilot with resolution assistance, agentic workflows, and no per-resolution credit charge on higher tiers
SLA managementEnterprise Edition onlyAvailable from Blossom tier with configurable first-response and resolution targets
Help CenterStartups+ tier requiredAvailable from Garden tier as Solutions with categories and folders
API availabilityAvailable on all cloud tiersNot available on Sprout (free); requires Blossom or higher

What to watch for in a Chatwoot to Freshdesk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Chatwoot Hacker plan 30-day data retention permanently deletes history

Chatwoot's free Hacker plan retains only 30 days of conversation data before permanent deletion.

How we handle it

Teams that have been running on Hacker for more than 30 days cannot export historical conversations regardless of the destination platform. We flag this during scoping and recommend either upgrading to a paid Chatwoot tier before export or accepting that conversations older than the retention window are unrecoverable. If the source account is active on Hacker and older than 30 days, we document which conversations are available and scope the migration to what exists, not what the team wishes existed.

high

Freshdesk API access requires Blossom tier or higher

Freshdesk's Sprout plan (free) does not include API access.

How we handle it

The platform requires an API key generated from the profile settings, which is only available on Blossom ($19/agent/month) and above. If the destination Freshdesk account is on Sprout, we cannot write migrated records via API and the customer must upgrade before migration proceeds. We confirm the destination Freshdesk plan during scoping and coordinate API key generation from the profile settings page before any data transfer begins.

medium

Freshdesk per-hour API rate limits require batch chunking

Freshdesk API rate limits are plan-dependent: Blossom and Garden cap at 3,000 calls per hour, Estate and Forest cap at 5,000 calls per hour.

How we handle it

Older plan tiers (Blossom, Garden, Estate, Forest) use per-minute limits (100-700 calls/minute). We monitor the X-RateLimit-Remaining and Retry-After headers from the Freshdesk API and implement batch chunking with exponential backoff to stay within limits. Without rate-limit-aware chunking, migrations exceed the hourly ceiling and receive 429 responses that stall the migration. We also warn that invalid requests count toward the limit, so a single malformed record can consume a quota slot without advancing migration progress.

medium

Chatwoot Help Center and SLA Policies may not exist on lower-tier sources

Help Center Articles require Chatwoot Startups tier or higher; SLA Policies require Enterprise Edition.

How we handle it

If the source account is on Hacker or Startups plan, these objects do not exist in the data export. We document which objects are absent based on the source plan during scoping, export what exists (Conversations, Contacts, Messages, Labels, Canned Responses), and deliver a written reconstruction plan for Help Center Articles and SLA Policies to be rebuilt manually in Freshdesk (where Help Center requires Garden tier and SLA Policies are available from Blossom). This gap is a plan-gating issue on the source, not a mapping limitation.

How the migration runs

  1. Discovery and plan verification

    We audit the source Chatwoot account across plan tier (Hacker/Startups/Business/Enterprise), data retention window, conversation volume, active inbox count, and which tier-gated objects exist (Teams, Automation Rules, Help Center Articles, SLA Policies).

    What this step covers

    We verify the destination Freshdesk plan and confirm API access is enabled (Blossom+ required). The discovery output is a written migration scope listing every object that will migrate, every object that will not migrate, and the reason for each exclusion. This document serves as the migration contract before any data extraction begins.

  2. Schema pre-creation in Freshdesk

    Before any record import, we pre-create the destination schema in Freshdesk.

    What this step covers

    This includes Freshdesk Groups (mapped from Chatwoot Teams if present), custom contact fields (mapped from Chatwoot contact custom_attributes), custom ticket fields (mapped from Chatwoot conversation custom_attributes), and product channel configurations (inbox types documented from Chatwoot for admin to configure). We cannot import records with custom field values until the custom fields exist in Freshdesk, so schema creation is a hard prerequisite step. We coordinate with the customer's Freshdesk admin to verify field types, dropdown options, and group structure before proceeding.

  3. Data extraction from Chatwoot

    We extract records from Chatwoot via the REST API using the conversations, contacts, messages, agents, teams, labels, and custom_attributes endpoints.

    What this step covers

    For conversations, we paginate using the created_at_after and created_at_before parameters to handle volume in chunks. We validate the export against Chatwoot's internal record counts and flag any records that fail to export due to schema bugs (documented in Chatwoot GitHub issues on v4.2-v4.4). If the source is on Hacker plan and older than 30 days, we document the conversation gap explicitly. We do not extract Captain AI state, report snapshots, or webhook configurations.

  4. Test migration and reconciliation

    We run a full migration into a Freshdesk sandbox or trial account using a subset of the exported data (typically 500-1,000 records per object type).

    What this step covers

    The customer's Freshdesk admin reconciles record counts, spot-checks 25-50 migrated tickets against the Chatwoot source for field accuracy, and verifies that message chronology, tag application, and assignee mapping are correct. We correct any mapping errors identified during test migration before running the production migration. Freshdesk API rate-limit behavior is validated against the destination plan tier during this phase so production chunk sizes are tuned correctly.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Agents (Users), Groups (from Teams), Contacts (with email dedupe key resolved), Conversations as Tickets (with Group assignment and assignee resolved), Messages as Conversation entries (preserving chronological order by created_at), Tags (applied to migrated tickets), Canned Responses as Templates, and Custom Field values on both Contact and Ticket records.

    What this step covers

    Each phase emits a row-count reconciliation report. We apply exponential backoff and batch chunking against the Freshdesk API based on the confirmed plan tier rate limits.

  6. Cutover, validation, and automation reconstruction handoff

    We freeze Chatwoot writes during cutover and run a final delta migration of any records modified during the migration window.

    What this step covers

    We deliver the written automation reconstruction guide for Chatwoot Automation Rules mapped to Freshdesk Scenario Automations, the Help Center reconstruction guide (if applicable), and the SLA Policy configuration guide. We do not rebuild automations, canned response logic, or SLA policies inside the migration scope. We support a three-day post-migration window to resolve data integrity issues; we do not provide ongoing admin support or training as standard scope.

Chatwoot Freshdesk
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · FreshdeskRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

2-3 weeksTypical, smaller accounts
4-6 weeksLarge or heavily customised accounts

A quote scales with conversation volume, custom attribute count, and whether Automation Rules and Help Center Articles exist on the source plan. Freshdesk subscription costs sit outside the migration fee. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Chatwoot to Freshdesk →

Why teams move from Chatwoot to Freshdesk

  • Teams outgrow Chatwoot's feature gating as they scale. Automation Rules require Business tier ($39/agent/month), Teams require Business tier, SLA Policies require Enterprise Edition ($99/agent/month), and SSO requires Enterprise. Reviewers on G2 and feature-base.app cite that the true cost at mid-market scale exceeds Chatwoot's headline price, whereas Freshdesk makes SLA management available from Blossom ($19/agent/month) and provides a larger marketplace of pre-built integrations without equivalent tier cliffs.
  • Freshdesk removes infrastructure management burden for teams that adopted Chatwoot for its self-hosting option but no longer have the engineering bandwidth to maintain Docker, PostgreSQL, and Redis. Eesel.ai and CompareTiers note that Freshdesk's managed cloud with built-in SLA support is a natural migration path for Chatwoot teams moving away from self-hosting to SaaS convenience without sacrificing enterprise features.
  • Freshdesk offers Freddy AI Copilot with agentic workflow capabilities and no per-resolution credit model, whereas Chatwoot's Captain AI charges $20 per 1,000 credits beyond the monthly allocation. Teams using AI heavily report unexpected billing on Chatwoot's credit model. Freshdesk's AI features are included at the product tier level rather than metered separately.
  • Freshdesk provides stronger SLA management, deeper reporting dashboards, and a more mature app marketplace. Helpdesk Picker and leadingbusinesstools.com note that teams requiring multi-dimensional support analytics, structured SLA policies, and enterprise-grade reporting move to Freshdesk because Chatwoot's reporting is derived from conversation data rather than native analytics objects.

Questions, answered

Chatwoot to Freshdesk migration questions

How long does a Chatwoot to Freshdesk migration take?

Most migrations land between two and three weeks for accounts under 10,000 conversations with no tier-gated objects (Help Center, Teams, Automation Rules) on the source. Migrations with Help Center Articles, large custom attribute schemas on both Conversations and Contacts, or conversation volumes exceeding 50,000 records move to four to six weeks because of article tree reconstruction, schema coordination, and extended batch chunking against Freshdesk API rate limits.

Do Chatwoot Automation Rules and SLA Policies migrate to Freshdesk?

No. Automation Rules and SLA Policies are platform-specific rule objects that do not transfer as executable code between Chatwoot and Freshdesk. We export the full rule definitions (trigger conditions, actions, and parameters) and deliver a written reconstruction guide mapping each Chatwoot Automation Rule to the equivalent Freshdesk Scenario Automation. SLA Policies require configuration in Freshdesk's SLA Policies section (available from Blossom tier); we document the source policy targets so the customer's admin can recreate them. Teams (Chatwoot Business+) map to Freshdesk Groups and do migrate as structural objects.

What happens to Chatwoot conversations if my source plan is on the Hacker free tier?

If the source Chatwoot account is on the Hacker plan and the account is older than 30 days, conversations beyond the 30-day retention window have been permanently deleted and cannot be recovered by any migration method. We confirm the account age and conversation date range during scoping. If historical conversations are critical and the account is over 30 days old, we recommend upgrading to a paid Chatwoot tier (Startups or Business) before export to access the longer retention windows (1 year or 2 years respectively). Migrating without upgrading results in a partial migration of only the last 30 days of data.

Can I migrate from Chatwoot to Freshdesk Sprout (free plan)?

No. Freshdesk Sprout does not include API access, which is required for any record-level migration via the Freshdesk API. The API key generation feature is available from Blossom tier ($19/agent/month) and above. We confirm the destination Freshdesk plan during scoping and recommend upgrading to Blossom before migration begins. The Sprout plan is suitable for evaluating Freshdesk manually but cannot receive automated migrated data.

What Chatwoot data does not migrate to Freshdesk?

Reports (CSAT, conversation metrics, agent performance) are derived analytics that Freshdesk recalculates from migrated ticket and conversation records; we do not export report snapshots. Captain AI state and credit balance do not migrate; Freshdesk starts with its own Freddy AI Copilot on applicable tiers. Integration credentials (webhook URLs, Slack channel mappings, bot tokens) are credentials-bound and do not transfer; we document the integration list for the customer's admin to reconfigure in Freshdesk. Workflows, Sequences, and Forms do not migrate as code; we deliver a written inventory for manual reconstruction.

How does FlitStack AI handle Freshdesk API rate limits during migration?

We implement batch chunking with exponential backoff against the Freshdesk API using the plan-tier rate limits confirmed during scoping. Blossom and Garden accounts are capped at 3,000 calls per hour; Estate and Forest accounts are capped at 5,000 calls per hour. We monitor the X-RateLimit-Remaining and Retry-After response headers and pause ingestion when the quota is exhausted, resuming after the Retry-After interval. Invalid requests count toward the limit, so we validate payload structure before submission to avoid consuming quota on malformed calls. Conversation volumes exceeding the hourly ceiling are chunked across multiple processing windows.

Do Chatwoot Help Center Articles migrate to Freshdesk?

Help Center Articles exist only on Chatwoot Startups tier and above. If the source Chatwoot plan is Startups or Business, we export the full article tree (title, body in markdown, category, locale) and deliver it as a written reconstruction guide for the customer's admin to rebuild in Freshdesk Solutions. Freshdesk Solutions requires Garden tier or higher at the destination. We do not have a direct article-to-article API migration path because Freshdesk's article import requires CSV upload with specific column formatting that differs from Chatwoot's article schema. SLA Policies (Enterprise Edition only on Chatwoot) are similarly documented for manual reconstruction in Freshdesk SLA Policies (Blossom+).

Get a quote

Moving from Chatwoot to Freshdesk?

Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.

Get a quote