---
title: "Crisp to Freshdesk Migration: Field Mapping & Rollback"
description: "Migrate Crisp to Freshdesk with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/crisp/to/freshdesk"
---

# Crisp to Freshdesk migration

We migrate Conversations, Contacts, Messages, and Operators from Crisp into Freshdesk Tickets with channel metadata preserved, operator attribution resolved, and every Crisp Tag carried as a Freshdesk label so your team picks up without starting over.

Short answer

FlitStack AI migrates tickets, ticket comments, contacts, companies and agents from Crisp 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-4 weeks.

![](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 what moves →](https://flitstack.ai/migrations/helpdesk/crisp/to/freshdesk#what-moves)

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

Source Crisp ![](https://flitstack.ai/platforms-trim/crisp.webp)

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

Ticket Ticket Comment Contact Company Agent

Mapped field by field · sample run · one-click rollback

## What moves from Crisp to Freshdesk?

The structural difference between Crisp and Freshdesk shapes the entire migration.

Read the full summary

Crisp organizes support around Conversations—linked message threads tied to a Contact and a Website. Freshdesk uses Tickets—a structured record type with status, priority, type, and source fields that must all be populated at import time. We resolve the schema difference by using Crisp Conversation attributes (state, channel, created\_at) to populate Freshdesk Ticket fields (status, priority, type, source), and by using the Crisp contact reference to resolve the Freshdesk requester. Operators map to Freshdesk Agents with role mapping documented separately. Crisp Tags move as Ticket labels; Canned Responses move as Freshdesk Saved Replies with placeholder syntax flagged for manual review. Automation logic, chatbot flows, and website widget configuration do not migrate; we deliver a written inventory of these for the admin to rebuild in Freshdesk.

1:1

### Conversation → Ticket

Crisp Conversations map to Freshdesk Tickets.

How it maps

The Crisp state field (open, pending, resolved, closed) maps to Freshdesk status values (open, pending, resolved, closed). The Crisp channel (chat, email, WhatsApp) maps to Freshdesk type or source field depending on the customer's naming convention. The Crisp created\_at timestamp preserves as the Freshdesk created\_at. Operator assignments migrate as Freshdesk agent assignments via email-matched resolution.

1:1

### Message → Ticket Comment

Crisp Messages nested inside Conversations map to Freshdesk Ticket Comments in chronological order.

How it maps

The author metadata (operator vs visitor) maps to comment type (reply vs note) in Freshdesk. Attachment URLs preserve and we re-upload files to Freshdesk's attachment storage during migration so that inline images and file links remain functional after cutover.

1:1

### Contact → Contact

Crisp Contacts (available from Essentials tier upward) map directly to Freshdesk Contacts.

How it maps

Standard fields (email, name, phone) migrate to Freshdesk equivalents. Crisp custom properties map to Freshdesk custom contact fields, which must be pre-created in Freshdesk before migration. API-based export from Crisp is used for Free/Mini accounts where the UI export is not available. Contact deduplication uses email as the unique key.

1:1

### Company → Company

Crisp Companies stored in the CRM module map to Freshdesk Companies.

How it maps

The Crisp company name becomes Freshdesk Company name, domain becomes the website field, and any custom properties map to Freshdesk custom company fields. Company-Contact relationships are preserved as Freshdesk Company-Contact lookups at migration time.

1:1

### Operator → Agent

Crisp Operators map to Freshdesk Agents resolved by email match.

How it maps

The Crisp operator role (admin, normal) maps to Freshdesk agent groups and permissions. If the Crisp operator count exceeds the destination Freshdesk plan seat limit, we flag the discrepancy and the customer decides whether to deactivate operators before migration or upgrade the destination plan.

1:1

### Tag → Ticket Tags

Crisp Tags applied to Conversations carry over as Freshdesk Ticket Tags.

How it maps

We extract the full tag list from Crisp and bulk-associate them with migrated Tickets. Tag normalization (lowercase, trim whitespace) is applied during migration to prevent duplicate tags from inconsistent casing.

******What moves 10 objects

Crisp Freshdesk

- Conversation Ticket 1:1
- Message Ticket Comment 1:1
- Contact Contact 1:1
- Company Company 1:1
- Operator Agent 1:1
- Tag Ticket Tags 1:1

\+ 4 more in the mapping below

## How Crisp 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.

| Dimension            | Crisp                                                            | Freshdesk                                                                                          |
| -------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Primary object model | Conversations as thread object with Messages nested inside       | Tickets as structured record with comments threaded separately                                     |
| Channel handling     | Chat, email, WhatsApp unified in single conversation via plugins | Freshdesk Omni (separate product) for chat; base product handles email and other channels natively |
| CRM module           | Gated behind Essentials tier (€95/workspace/month)               | Contact and Company objects available on all tiers; API access requires Blossom or above           |
| Pricing model        | Per-workspace flat pricing with seat tiers                       | Per-agent monthly pricing (Growth at $15/agent, Pro at $49/agent)                                  |
| Custom objects       | No equivalent to Freshdesk Custom Objects                        | Custom Objects with typed fields and lookup relationships available on Pro and higher              |
| Automation           | Chatbot builder and routing on Essentials+; limited workflow     | Automation rules and Freddy AI Copilot with separate add-on billing                                |

## What to watch for in a Crisp 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

### Contact export requires Essentials or API key on Crisp

The CSV contact export in Crisp's UI is only available on the Essentials plan or higher.

How we handle it

Teams on Free or Mini tiers cannot trigger a bulk export from the UI. We work around this by using the Crisp REST API /contacts endpoint, which is accessible with an API key regardless of tier. We confirm API key availability and scope during discovery and use the API export path for lower-tier accounts. If no API key exists, the customer must generate one from Crisp settings before migration begins.

medium

### Canned Response placeholders use incompatible syntax

Crisp Canned Responses use %placeholder% syntax (e.g., %contact.email%, %session.nickname%).

How we handle it

Freshdesk Saved Replies use Liquid-style {{ticket.sender.name}} and similar variables. We export Canned Responses as plain text with placeholders intact and document every instance that needs manual adaptation. This is not automated because the variable mappings are content-specific. The customer's admin reviews and updates Saved Replies in Freshdesk before activating them.

medium

### Segments are dynamic with no Freshdesk equivalent

Crisp Segments are dynamic Contact filters defined by rules (property conditions, combined with AND/OR logic).

How we handle it

Freshdesk has no equivalent dynamic segment object. We export the segment rule definitions as structured metadata and deliver a written map of each segment with its filter criteria. The customer's admin converts them to Freshdesk Saved Filters or Smart Views with equivalent criteria. Automation based on segment membership does not migrate.

medium

### Multi-level API rate limits on Crisp

Crisp enforces four tiers of rate limiting: load balancer, API global, API route, and plugin quota.

How we handle it

For large migrations pulling Conversations and Contacts in bulk, we implement exponential backoff and respect the Retry-After header on 429 responses. We throttle reads below the global limit to avoid disrupting live API access that the customer may still need for operational use during migration.

low

### Freshdesk API requires Blossom or above

Freshdesk's API is not available on the Sprout (free) plan.

How we handle it

If the customer provisions a Freshdesk Sprout account as the destination, API-based migration is blocked. We confirm the destination Freshdesk plan during scoping and recommend Blossom ($21/agent/month) or higher if API access is required. The customer must activate the API from their Freshdesk admin panel once the plan is confirmed.

## How the migration runs

1. ### Discovery and plan verification

   We audit the source Crisp account: plan tier (Free/Mini/Essentials/Plus), record volumes (Conversations, Contacts, Companies, Operators), active Tags, Segments, Canned Responses, and widget configuration.

   What this step covers

   We verify the destination Freshdesk plan tier and confirm API availability (Blossom or above required). The discovery output is a written migration scope with record counts per object, a list of objects requiring pre-creation in Freshdesk (custom fields, agent groups), and a confirmation of any plan-tier gaps.

2. ### Schema pre-creation in Freshdesk

   Before any data moves, we create custom contact fields and custom company fields in Freshdesk that match Crisp's custom properties.

   What this step covers

   We also configure Freshdesk Groups if the customer uses multiple Crisp Websites and wants to map them to team-based routing. Tags are pre-listed in Freshdesk so that the migration script can associate them at import time. Agent groups are created and the migration user is granted appropriate permissions for bulk record creation.

3. ### API-based data extraction from Crisp

   We pull Conversations, Messages, Contacts, Companies, Operators, Tags, Segments, and Canned Responses from Crisp using the REST API.

   What this step covers

   For Free and Mini tier accounts, the UI export is unavailable, so we use the /contacts endpoint with API key authentication. For accounts approaching 200K contacts, we chunk exports by ID range and deduplicate on contact\_id across passes. Rate limiting is handled with exponential backoff and Retry-After header compliance.

4. ### Transformation and schema mapping

   We transform extracted data according to the mapping schema: Conversation state maps to Ticket status, Message authors map to comment types (reply vs note), Crisp Tags normalize and associate with Tickets, and Canned Responses export with placeholders flagged.

   What this step covers

   For Contacts, we deduplicate by email and resolve any missing Company associations. Segments export as structured rule metadata. Attachments download from Crisp storage and prepare for re-upload to Freshdesk.

5. ### Pilot migration and reconciliation

   We run a pilot migration of 50-100 random Conversations and their linked Contacts into the destination Freshdesk account.

   What this step covers

   The customer reconciles the sample: checks Ticket status assignment, comment ordering, tag association, and contact-company linking. Any mapping errors are corrected before the full migration begins. This step also validates that Freshdesk API credentials and permissions are correctly configured.

6. ### Full migration and cutover

   We run the full migration in dependency order: custom fields and groups (pre-created, validated), Contacts and Companies, Operators (agent provisioning), Conversations (Tickets with resolved requester and agent), Messages (Comments), Tags (Ticket labels), Canned Responses (Saved Replies flagged for adaptation), and Attachments (re-uploaded to Freshdesk storage).

   What this step covers

   We freeze Crisp writes during the cutover window, run a delta migration of any records modified during migration, then hand off. We deliver a Canned Response adaptation guide and a Segment-to-Filter conversion map as written documents for the admin to implement post-migration.

![](https://flitstack.ai/platforms/crisp.png) Crisp ![](https://flitstack.ai/platforms/freshdesk.svg) Freshdesk

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Freshdesk Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**5-8 weeks** Large or heavily customised accounts

A quote scales with record volume and source tier. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Crisp to Freshdesk →](https://flitstack.ai/contact)

## Why teams move from Crisp to Freshdesk

- Crisp's CRM module is gated behind the Essentials tier at €95 per workspace per month, making the Contact export and custom property export inaccessible to teams on Free or Mini plans. Freshdesk provides Contact and Company objects on all tiers, and the API is available from Blossom upward ($21/agent/month). Teams wanting a full contact history export without upgrading the Crisp plan move to Freshdesk where the contact data model is included at no additional cost.
- Crisp's live chat-first model scores 9.5 on G2 for chat but 8.9 for email, reflecting its origin as a chat widget vendor. Freshdesk's email support scores 9.2 on G2 and its ticketing UX scores 8.9, reflecting its origin as a structured helpdesk. Teams that receive more email tickets than chat volume move to Freshdesk because the ticketing workflow (status, priority, type, SLA) is native rather than bolted on.
- Crisp's AI Copilot and auto-reply consume a credit budget that resets monthly and does not roll over. Teams with high message volume report unpredictable billing when AI credits exhaust mid-month, triggering overage or degraded automation. Freshdesk's Freddy AI Copilot is a per-agent add-on ($29/agent/month) with clearer consumption models, and its Knowledge Base creation tools are available without per-action credit limits on higher tiers.
- Crisp's chatbot builder and website widget are chat-native and load in 1.6 seconds according to Crisp's own benchmarks. However, when a team grows to require multi-brand support centers, SLA management, and structured ticketing workflows, Freshdesk's Pro ($49/agent) and Enterprise tiers provide these natively rather than requiring third-party integrations. The per-agent pricing of Freshdesk also becomes more predictable at scale compared to Crisp's per-workspace model with escalating seat costs.
- Teams with existing Freshworks contracts cite the unified Freshdesk ecosystem as a reason to consolidate. When a company uses Freshservice for ITSM or Freshsales for CRM, adding Freshdesk for customer support creates a single Freshworks admin console and a single vendor relationship. Moving Crisp data into Freshdesk removes a separate vendor and consolidates billing.

Questions, answered

## Crisp to Freshdesk migration questions

How long does a Crisp to Freshdesk migration take?

Most Crisp to Freshdesk migrations complete in two to four weeks for accounts under 5,000 Conversations and 3,000 Contacts. Migrations exceeding 20,000 Conversations, 10,000 Contacts, or requiring multi-chunk export due to the 200K contact ceiling extend to five to eight weeks. Timeline also depends on whether custom contact properties, Segments, or Canned Responses require additional mapping work.

Do Crisp chatbot flows and automations migrate to Freshdesk?

No. Crisp chatbot flows are built in Crisp's proprietary automation builder and have no Freshdesk equivalent as a data artifact. Freshdesk automation rules (event-based and time-based) are a separate configuration model that the customer's admin rebuilds post-migration. We deliver a written inventory of every active Crisp chatbot flow and automation trigger with a recommended Freshdesk automation equivalent, but the rebuild itself is outside standard migration scope.

Can we migrate Crisp Contacts if we are on the Free or Mini plan?

Yes, with a workaround. The CSV contact export in Crisp's UI is only available on the Essentials plan or higher, but the REST API /contacts endpoint is accessible with an API key on any tier. We use the API export path for Free and Mini accounts. The customer must generate an API key from Crisp settings before migration begins. We confirm API key availability during discovery.

What happens to our Crisp Segments after migration?

Crisp Segments are dynamic Contact filters with rule-based membership. Freshdesk has no equivalent dynamic segment object. We export the segment rule definitions as structured metadata and deliver a written Segment-to-Filter conversion map. The customer's admin creates Freshdesk Saved Filters or Smart Views using equivalent filter criteria. Dynamic re-evaluation of segment membership does not carry over because it requires Crisp's rule engine.

How do we handle Crisp Canned Responses in Freshdesk?

Crisp Canned Responses use %placeholder% variable syntax. Freshdesk Saved Replies use Liquid-style {{ticket.sender.name}} variables. We export Canned Responses as plain text with placeholders intact and deliver an adaptation guide listing every Saved Reply and the variable substitutions needed. The customer's admin reviews and updates Saved Replies in Freshdesk before activating them. This is a manual step because variable mapping is content-specific.

What Freshdesk plan tier do we need for API-based migration?

Freshdesk's API is not available on the Sprout (free) plan. The destination account must be on Blossom ($21/agent/month) or higher. API activation requires the customer to enable it from the Freshdesk admin panel under Profile Settings > API key. We confirm the destination plan and API status during discovery before migration begins.

Can FlitStack AI migrate from Freshdesk back to Crisp?

Yes. We also handle Freshdesk to Crisp migrations. The schema direction reverses: Freshdesk Tickets map to Crisp Conversations, Freshdesk Contacts map to Crisp Contacts (available from Essentials tier upward), and Freshdesk Saved Replies map to Crisp Canned Responses with variable syntax adapted. The primary constraint on a Freshdesk-to-Crisp migration is that Crisp's free plan is limited to two operators, which may require plan upgrades for larger support teams.

## Related migrations

[![](https://flitstack.ai/platforms-trim/freshdesk.webp) Migrate to **Freshdesk** Every source we move into Freshdesk, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/freshdesk) [**Chatwoot to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/chatwoot/to/freshdesk) [**Help Scout to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/help-scout/to/freshdesk) [**Zendesk to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/freshdesk) [**SysAid to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/sysaid/to/freshdesk) [**Zoho Desk to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zoho-desk/to/freshdesk) [**Jira Service Management to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/freshdesk) [**Crisp to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/crisp/to/zendesk)

## Sources: official documentation

1. [Import to Freshdesk — Freshworks Marketplace](https://www.freshworks.com/apps/import_to_freshdesk/)
2. [Import and export customers and company information — Freshdesk](https://support.freshdesk.com/support/solutions/articles/196491-importing-and-exporting-customer-data)
3. [Throughput and plan-tier limits — Freshdesk](https://support.freshdesk.com/support/solutions/articles/225439)
4. [Associating different object types in Freshdesk](https://support.freshdesk.com/support/solutions/articles/50000004226-understanding-associations-in-custom-objects)
5. [Freshdesk integration reference](https://developers.freshdesk.com/api/)
6. [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-)
7. [Freshworks Data Import to Freshdesk — Marketplace](https://www.freshworks.com/apps/help_desk_migration__import_to_freshdesk/)

Get a quote

## Moving from Crisp 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](https://flitstack.ai/contact)
