Migrating from Freshdesk to Crisp? This guide helps you move the customer data, support history, knowledge, channels, automation, and AI your team still needs.

Freshdesk often becomes the operational backbone of a support team, with tickets, groups, views, fields, canned responses, automation rules, and Freddy AI connected together. Crisp keeps the structure that matters, but organizes daily support around a shared Inbox, customer context, workflows, and Hugo, the AI Agent. The goal is not to copy every old rule: it is to rebuild a cleaner support flow your team can understand from day one.

This guide covers the main parts of a Freshdesk migration:

• Understand what changes → move from a ticket-first setup to a conversation-first workflow
• Map Freshdesk features to Crisp → translate the tools your team already uses
• Migrate step by step → move contacts, history, knowledge, replies, automation, and integrations
• Test and switch over → launch without splitting customer traffic between two platforms
• Find answers → clarify the most common migration questions

What changes when moving from Freshdesk

Freshdesk is built primarily around tickets. Crisp starts from the conversation: agents work from a shared Inbox where messages, customer details, previous exchanges, segments, and custom data stay close together.

From tickets to conversations

In Crisp, a customer request normally arrives as a conversation rather than an isolated ticket object. Agents can reply, assign it, leave private notes, set reminders, move it between inboxes, and resolve it without losing the surrounding customer context.

Crisp uses Open, Pending, and Resolved conversation states. Pending is useful when a teammate is already handling the request but still needs to investigate, wait for another team, or follow up before resolving it.

When customers need formal case tracking through an authenticated portal, you can add the Ticket Center instead of forcing every support exchange into a ticket by default.

Keep structure without rebuilding every queue

Freshdesk groups and views often combine team ownership, queue visibility, priority, topic, and status.

In Crisp, those concerns are separated into clearer building blocks:

• Sub-inboxes → decide where a conversation belongs
• Operator Routing → assigns the right human operator or team
• Filters and custom views → help agents focus on the conversations they need
• Segments and custom data → preserve useful classifications and customer attributes
• Hugo Routing → routes by intent, topic, emotion, or another situation described in natural language

This keeps important structure without reproducing every legacy queue and exception.

AI and humans share the same workflow

Hugo works directly inside the Crisp conversation flow. It can answer common questions, use your support knowledge, route requests, trigger workflows, and escalate to a human when needed.

When Hugo handles incoming conversations in the Automated Inbox, your team can stay focused on requests that require human attention. Escalated conversations keep the existing exchange and customer context, so an operator can continue without asking the customer to start again.

How Freshdesk maps to Crisp

Most Freshdesk concepts have a practical Crisp equivalent, although the underlying model is not always one-to-one.

Migrate the fields agents, routing rules, automations, and reports actively use. Stable customer information usually belongs in contact details, company information, or custom data. Operational labels such as customer type, priority group, product area, or lifecycle stage can often become segments.

Translate automation by outcome

A Freshdesk rule should not be recreated simply because it exists. First identify what it is meant to achieve: assign billing requests, collect account details, escalate frustrated customers, send an acknowledgement, or trigger an internal action.

Once the outcome is clear, choose the simplest Crisp tool that can achieve it. Basic ownership belongs in routing, repeatable multi-step processes belong in workflows, and behavior expressed in natural language often belongs in Hugo Instructions or Routing.

Migration: step by step

A reliable migration is progressive. Move the information required for daily support first, then add historical context and advanced automation after the core workflow is stable.

Step 1 - Define the scope and prepare Crisp

Inventory the parts of Freshdesk your team still depends on: contacts and companies, active tickets, historical conversations, knowledge articles, canned responses, groups, views, fields, automation rules, Freddy AI behavior, integrations, and reports.

Sort them into three practical buckets:

• Needed for launch → operators, contacts, primary channels, knowledge articles, common replies, and core routing
• Useful after launch → deeper conversation history, advanced workflows, secondary integrations, and reporting refinements
• Archive only → obsolete tickets, unused fields, inactive rules, and historical reports that only need to remain accessible

Freshdesk lets you export contacts as CSV. Before cutover, also export any reports or account data required for retention, audits, or historical comparison.

Open Crisp, invite your operators from Settings → Workspace Settings → Operators & Teams, then create only the sub-inboxes your team genuinely needs from Settings → Inbox Settings → Sub-Inboxes. A simple starting structure might separate support, billing, sales, and technical requests.

Prepare your channels without switching live traffic yet. Configure email from Settings → Workspace Settings → Setup & Integrations → Email, and retrieve the website installation instructions from Settings → Workspace Settings → Setup & Integrations → Chatbox setup instructions.

Step 2 - Import contacts and reconnect customer data

Export your Freshdesk contacts as CSV, remove obvious duplicates, and decide which fields should remain standard profile information, segments, or custom data.

In Crisp, open Contacts → Actions → Import Contact Profiles, upload the CSV, and map the columns. An email address is required for each profile. You can also map names, phone numbers, company information, location, segments, creation dates, and your own customer attributes.

For custom attributes, use clear keys such as data.user_id, data.subscription_plan, or data.account_status. This makes the information easier to reuse in the Inbox, integrations, workflows, and Hugo.

A CSV is only the starting point. Reconnect the systems that keep customer context current, such as your CRM, ecommerce platform, subscription backend, order system, or internal tools. Depending on your stack, use native Crisp integrations, the REST API, the Web SDK, Zapier, Make, n8n, or a custom integration.

Prioritize reliable information that changes how support is handled: user ID, account link, company, plan, subscription state, enabled features, recent orders, and operational restrictions.

Step 3 - Import conversation history when useful

Not every team needs every historical ticket inside Crisp. Recent conversations, active cases, VIP customers, long-running technical issues, and accounts where previous context affects the answer usually provide the most value.

Freshdesk's normal ticket-list export can produce CSV or Excel files, but it does not include the complete ticket conversation or archived history. For full message content, use a Freshdesk account export from Admin → Account → Account Details → Export, or retrieve tickets and their conversations through the Freshdesk API.

Crisp provides an open-source conversation import library that can recreate historical conversations and messages from structured files. Freshdesk is not currently included as a ready-made adapter, so a developer must transform the export into the expected format or add a Freshdesk adapter before running the import.

Imported history is mainly there to give operators context in the Crisp Inbox. Keep Freshdesk accessible as a temporary archive until the history required by your team and retention policy is safely available.

Step 4 - Move the knowledge base and canned responses

If your Freshdesk Solutions portal is public, Crisp can import it directly. Open Knowledge Base → Actions → Import articles, paste the public Freshdesk knowledge base URL, and start the import. For multilingual portals, import each language from its matching public URL.

Afterwards, review categories, formatting, images, videos, tables, internal links, and article visibility. The knowledge base migration guide covers the checks to perform.

Freshdesk administrators can also export canned responses. Export them as CSV, remove replies your team no longer uses, then convert the useful entries to Crisp's shortcut format.

Prepare these columns before importing the file:

• bang → a short trigger such as !refund or !welcome
• text → the reply agents should insert
• tag → an optional category such as billing, onboarding, or technical

Import the file from Settings → Inbox Settings → Message Shortcuts → … → Import. Freshdesk exports may contain HTML in the response body, so review the formatting and convert anything that would not display cleanly in a Crisp message. See How to import or export message shortcuts for the expected CSV format.

Step 5 - Rebuild routing, automation, and AI

Document the trigger, expected result, exceptions, and human fallback for each Freshdesk rule that still matters, then rebuild it with the most suitable Crisp feature.

Translate each behavior by its intended outcome:

• Send work to a team or queue → use sub-inbox conditions and Operator Routing
• Detect an intent, topic, emotion, or special situation → use AI Agent → Guidance → Routing
• Run a repeatable multi-step process → use AI Agent → Automate → Workflow Builder
• Define tone, boundaries, policies, and escalation behavior → use AI Agent → Guidance → Instructions
• Provide factual answers → train Hugo with your knowledge base, website pages, Q&A snippets, and files
• Retrieve data or perform an action → connect a supported Hugo integration or build an MCP integration

The external Hugo Tools companion app can make this conversion easier. Use the Instruction Helper to turn existing support policies, tone guidance, and escalation rules into clearer Hugo Instructions. Use the Workflow Wizard to design or simplify the automations your team still needs.

Test Hugo from AI Agent → Evaluate → Playground. Verify its answers, routing, escalation, and workflow behavior before enabling it from AI Agent → Agent → Activation. The Hugo Tools guide provides a practical workflow for this process.

Test and switch over

The migration is ready when your team can complete representative support cases in Crisp without returning to Freshdesk for normal daily work.

Run a practical launch rehearsal

Create test conversations that reflect your real workload rather than testing only a generic greeting.

Before switching customer traffic, verify that:

• Contacts → imported profiles, companies, segments, and custom data are correct
• Email and chat → messages reach Crisp, replies use the expected sender, and the Crisp chatbox loads correctly
• Routing → conversations reach the right sub-inbox and operator
• Agent tools → message shortcuts, private notes, reminders, and knowledge articles are available
• Hugo → common questions, unknown questions, escalation cases, and workflow triggers behave as expected
• History → imported conversations are readable and do not generate customer notifications
• Integrations → agents and Hugo can access the customer information needed to resolve requests

Switch channels progressively

Choose a controlled cutover window and move one live channel at a time. After each switch, send a real test message, confirm that it appears in Crisp, reply from the Inbox, and verify the result from the customer's side.

For email, update the forwarding or mailbox configuration so new messages arrive in Crisp. For website chat, replace the Freshdesk widget with the Crisp chatbox. Reconnect social and messaging channels only after their ownership and routing are clear.

Leave Freshdesk accessible as an archive while the team becomes comfortable with Crisp and validates historical data, and avoid handling new conversations there. Record anything agents still need to look up: this will show whether you should import more history, recreate a missing field, reconnect another integration, or simply document a new Crisp workflow.

Ready to make the switch

Moving from Freshdesk to Crisp does not mean giving up the structure your support team relies on. It means translating that structure into a conversation-first setup where customer context, human collaboration, automation, and Hugo work together in one Inbox.

The strongest migrations preserve the information and processes that improve support, while leaving behind unused fields, duplicated queues, and brittle rules. Start with the essentials, test with real cases, and refine the workspace from actual team feedback.

You can review the broader product differences on Crisp vs Freshdesk and start preparing your workspace from Crisp. For a historical conversation import, contact the Crisp support team before running the migration library so the workspace can be prepared safely.

Frequently Asked Questions

Still have questions which were not covered in this article? Here is a collection of the most frequently asked questions on this topic.

Can Crisp import Freshdesk tickets automatically?

There is currently no one-click Freshdesk ticket importer. Contacts, public knowledge articles, and message shortcuts have straightforward import paths. Full ticket conversations require a Freshdesk account export or API extraction, followed by a transformation or custom Freshdesk adapter for the Crisp conversation import library.

Do I need to migrate every old Freshdesk ticket?

Usually not. Start with active, recent, or high-value conversations that agents are likely to consult. Keep Freshdesk available as an archive while you confirm whether older history is genuinely needed inside Crisp.

Can Freshdesk automations and Freddy AI settings be imported?

They should be translated rather than copied blindly. Use routing for ownership, workflows for structured processes, Hugo Instructions for behavior, Hugo Routing for intent-based decisions, and training resources for factual knowledge. Hugo Tools can help prepare the new instructions and workflow logic, but your team should review and test the result.

Can Crisp import a Freshdesk knowledge base?

Yes, when the Freshdesk knowledge base is publicly accessible. Paste its public URL into Knowledge Base → Actions → Import articles. Import each language URL separately for multilingual portals, then review the formatting, categories, media, and internal links.

Can I keep Freshdesk live while testing Crisp?

Yes, a staged transition is recommended. Keep Freshdesk available for reference while testing Crisp, but avoid directing the same live channel to both systems unless that duplication is intentional. At cutover, switch each channel individually and verify it from the customer's side.

Updated on: 09/08/2026