> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Moving from Zendesk *Migrating from Zendesk to Crisp? This guide helps you move from a ticket-first setup to a conversation-first support workflow without losing structure.* Zendesk often becomes the operational backbone of a support team: queues, statuses, assignments, customer fields, macros, and ticket history. Crisp keeps that need for structure, but organizes daily work around conversations, inboxes, customer context, and Hugo, the AI Agent. __This migration guide covers:__ * [Moving from tickets to conversations](#1-moving-from-tickets-to-conversations) → how Crisp structures support differently * [How Zendesk maps to Crisp](#1-how-zendesk-maps-to-crisp) → the main feature equivalents to understand * [How AI fits into this support model](#1-how-ai-fits-into-this-support-model) → how Hugo handles and escalates conversations * [How to migrate step by step](#1-migration-step-by-step) → the recommended order for contacts, data, history, content, and AI * [Where to go next](#1-ready-to-make-the-switch) → useful resources before launch | You keep the structure your team depends on, but inside a more flexible conversation-first system. --- # ${color}[#0080dd](Moving from tickets to conversations) Zendesk is built around tickets. Each request becomes a separate unit that needs to be assigned, tracked, and resolved. Crisp starts from a different idea: the conversation is the main workspace, and context stays attached to the customer relationship over time. #### ${color}[#445055](A conversation-first workflow) In Crisp, agents work from conversations rather than isolated tickets by default. This makes it easier to see previous exchanges, understand the customer journey, and avoid splitting related context across too many separate cases. For known users, session continuity can help restore an existing chat session across visits or devices when implemented with the Web SDK. #### ${color}[#445055](Ticketing still exists when you need it) Crisp also provides a [ticketing layer](https://crisp.chat/en/ticket/), but it is not the foundation of the support workflow. It is better seen as an additional structure you can use when a request needs more formal tracking. __This gives your team a useful balance:__ * **Conversations** → keep support contextual and easy to follow * **Inboxes and filters** → organize the queue without forcing every exchange into a ticket object * **Ticketing** → add structure when a request needs dedicated tracking #### ${color}[#445055](Open APIs for custom migrations) If your Zendesk setup depends on custom logic, Crisp provides API and SDK options to recreate or extend your workflow. This can be useful for importing data, syncing users, pushing custom properties, restoring sessions, or connecting internal tools. Useful resources: [Crisp REST API](https://docs.crisp.chat/references/rest-api/v1/) and [Crisp Web SDK session continuity](https://docs.crisp.chat/guides/chatbox-sdks/web-sdk/session-continuity/). || In short: you are not losing structure. You are reorganizing it around conversations, with ticketing available when the workflow needs it. --- # ${color}[#0080dd](How Zendesk maps to Crisp) The core support needs are familiar: organize work, assign conversations, reuse replies, keep customer context visible, and automate what should not require a human. The difference is how these pieces fit together inside Crisp. ![Zendesk to Crisp inbox mapping](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/zendesk-to-crisp-inbox-mapping_1wu1akt.webp =1000xauto) #### ${color}[#445055](Conversation vs ticket) Zendesk is ticket-first. Crisp is conversation-first. Instead of creating isolated tickets as the default unit of work, Crisp lets agents handle customer exchanges in the Inbox while keeping contact details, history, and context nearby. Start here: [learn the Crisp Inbox](https://help.crisp.chat/en/article/getting-started-with-the-crisp-inbox-opv83/). #### ${color}[#445055](Inboxes and filters vs views) Zendesk agents often use **Views** to organize tickets. In Crisp, this logic is handled through **inboxes**, **sub-inboxes**, routing, assignments, and filters. You can separate work by team, topic, channel, priority, or ownership while keeping conversations easy to follow. Useful resources: [create sub-inboxes](https://help.crisp.chat/en/article/how-can-i-create-sub-inboxes-in-my-crisp-workspace-ke3xk7/), [routing and assignation](https://help.crisp.chat/en/article/how-does-routing-assign-work-qjl2d2/), and [custom filters](https://help.crisp.chat/en/article/how-can-i-create-custom-filters-for-my-conversations-19yv8eo/). #### ${color}[#445055](Message shortcuts vs macros) Zendesk macros are called **message shortcuts** in Crisp. They help agents send consistent replies quickly and are managed from [**Crisp**](https://app.crisp.chat) under **Settings → Inbox Settings → Message Shortcuts**. Useful resources: [use shortcut replies](https://help.crisp.chat/en/article/how-can-i-use-shortcut-replies-canned-messages-1bmff5q/) and [import or export message shortcuts](https://help.crisp.chat/en/article/how-to-import-export-message-shortcuts-197bubz/). #### ${color}[#445055](Conversation context vs ticket fields) Zendesk often relies on ticket fields and custom fields. Crisp displays context in the **right sidebar**, including contact details, segments, custom data, and previous conversations when available. If your workflow depends on custom customer attributes, recreate them as **custom data** or **segments** so agents and automations can keep using them. Useful resources: [segments](https://help.crisp.chat/en/article/what-is-a-segment-and-how-can-it-help-your-team-88hhzw/) and [custom data](https://help.crisp.chat/en/article/what-is-custom-data-and-why-is-it-powerful-43jgi3/). #### ${color}[#445055](Hugo vs Zendesk AI) Zendesk AI is usually connected to a ticket-first support model. In Crisp, AI is handled through **Hugo**, which works at the conversation level. Hugo can answer, route, escalate, and trigger workflows depending on your configuration. Start here: [navigate the Hugo interface](https://help.crisp.chat/en/article/navigating-the-hugo-interface-and-features-h1eatv/). --- # ${color}[#0080dd](How AI fits into this support model) Hugo is integrated directly into Crisp’s conversation workflow. Instead of waiting for a ticket to be manually processed, Hugo can act at the beginning of a conversation and decide what should happen next. #### ${color}[#445055](Hugo acts at the entry point) When a user sends a message, Hugo can analyze the request and generate a response using available knowledge, context, and instructions. Depending on your setup, Hugo can answer the customer, route the conversation, or escalate it to a human operator. Start here: [Getting started with Hugo AI Agent](https://help.crisp.chat/en/article/getting-started-with-hugo-ai-agent-w6gbux/). #### ${color}[#445055](The Automated Inbox separates AI-handled conversations) In many setups, new conversations first go through the **Automated Inbox**, where Hugo attempts to resolve them without notifying the support team. If the request needs human input, it is moved to the appropriate human inbox. Learn more: [Automated Inbox: how Hugo handles conversations automatically](https://help.crisp.chat/en/article/automated-inbox-how-hugo-handles-conversations-automatically-1hg5umu/). #### ${color}[#445055](Human agents keep the full context) When Hugo escalates a conversation, agents can review what happened, see the same customer context, and continue from the same exchange. This keeps AI handling and human handling inside one support flow. Useful resources: [configure escalation](https://help.crisp.chat/en/article/how-to-configure-escalation-with-hugo-ai-agent-sqbm34/) and [start workflows with Hugo routing](https://help.crisp.chat/en/article/how-to-start-workflows-situationally-with-hugo-ai-routing-yz715l/). --- # ${color}[#0080dd](Migration: step by step) A smooth Zendesk migration is usually progressive. Start by moving the data and processes your team needs to work every day, then import history and refine automation once the new workflow is stable. #### ${color}[#445055](Step 1: Import contacts) Import contacts first so your team can recognize customers immediately. Open [**Crisp**](https://app.crisp.chat), then go to **Contacts → Actions → Import Contact Profiles** to upload a CSV file and map your fields. Useful resource: [import user data](https://help.crisp.chat/en/article/how-to-import-my-user-data-dcukz8/). #### ${color}[#445055](Step 2: Reconnect business and customer data) If your Zendesk setup relies on ecommerce, CRM, backend, or internal data, reconnect that context inside Crisp. This is especially important when agents need order history, plan details, account status, lifecycle stage, or custom customer attributes. Depending on your stack, this can involve native integrations, the REST API, the Web SDK, Zapier, Make, n8n, or a custom backend connection. #### ${color}[#445055](Step 3: Import ticket and conversation history) If historical support data is important, import it after planning how much history your team truly needs inside Crisp. Imported history can help preserve customer context and make long-term relationships easier to support. Crisp provides a [conversation import script](https://github.com/crisp-im/crisp-import-conversations) that can be used for this migration flow. Imported history remains visible to your team in the Inbox, but users do not automatically see past imported exchanges in the chatbox. #### ${color}[#445055](Step 4: Import your knowledge base) Your Zendesk help center can be imported from [**Crisp**](https://app.crisp.chat) under **Knowledge Base → Import articles**. Enter the public help center URL, start the import, then review categories, images, formatting, and internal links. Useful resource: [import your Knowledge Base](https://help.crisp.chat/en/article/how-can-i-import-my-knowledge-base-from-a-previous-provider-rpa7tv/). #### ${color}[#445055](Step 5: Import reply templates) If your team relies on Zendesk macros, recreate or import them as **message shortcuts**. In [**Crisp**](https://app.crisp.chat), go to **Settings → Inbox Settings → Message Shortcuts**, then use the import option if you have a CSV file. Useful resource: [import or export message shortcuts](https://help.crisp.chat/en/article/how-to-import-export-message-shortcuts-197bubz/). #### ${color}[#445055](Step 6: Set up the Inbox and Hugo) Once data and content are in place, configure the workflow your team will use every day: the chatbox, inbox routing, sub-inboxes, filters, shortcuts, knowledge base, and Hugo. If Hugo needs to rely on customer or ecommerce context, make sure that data is connected before configuring AI instructions and routing. Useful resources: [Getting started with Crisp](https://help.crisp.chat/en/article/getting-started-with-crisp-for-customer-support-1ts8txn/) and [Getting started with Hugo AI Agent](https://help.crisp.chat/en/article/getting-started-with-hugo-ai-agent-w6gbux/). #### ${color}[#445055](Step 7: Test before going live) Before switching traffic, simulate real support cases. Check that Hugo answers common questions correctly, conversations route to the right inbox, shortcuts are available, customer context appears in the sidebar, and agents understand when to use **Open**, **Pending**, and **Resolved**. __Recommended launch order:__ * **Contacts** → identify users from day one * **Business and ecommerce data** → keep customer context available * **Knowledge base** → support self-service and Hugo answers * **Shortcuts** → keep common replies ready * **Inbox routing and Hugo** → organize and automate the new workflow * **Historical conversations** → import once the core setup is stable, unless history is critical immediately --- # ${color}[#0080dd](Ready to make the switch) Switching from Zendesk to Crisp does not mean giving up structure. It means moving that structure into a conversation-first workflow where customer context, AI, routing, and collaboration are easier to manage together. A good migration is not a copy-paste of every Zendesk view and field. It is a translation of the workflows your team actually needs into the simpler Crisp model. | You can compare both platforms here: [Crisp vs Zendesk](https://crisp.chat/en/alternatives/zendesk/). ||| Need help with your migration? Contact the Crisp team directly from your workspace or through the website so we can review your setup with you.