Skip to content
Get a quote

Crisp to Zendesk migration

We migrate Conversations, Contacts, and Messages from Crisp into Zendesk Tickets with operator attribution preserved, message threading intact, and tag labels carried across as a structured handoff. The Crisp shared-inbox model becomes a Zendesk ticket queue with multi-channel routing and agent management that scales beyond the per-workspace seat model.

Short answer

FlitStack AI migrates tickets, comments, end-user or agents, agents and channel routing configurations from Crisp to Zendesk, 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: 3-5 weeks.

By

Source Crisp
DestinationZendesk
TicketCommentEnd-User or AgentAgentChannel Routing Configuration
Mapped field by field · sample run · one-click rollback

What moves from Crisp to Zendesk?

Moving from Crisp to Zendesk is a structural migration from a shared-inbox thread model to a ticket-centric helpdesk.

Read the full summary

Crisp Conversations map to Zendesk Tickets, with the Crisp website-to-channel mapping translated into Zendesk's channel routing configuration. We preserve operator attribution, message timestamps, and attachment URLs across the migration. Crisp's Contact CRM properties (available from the Essentials tier upward) map to Zendesk User fields and custom fields, while Tags carry as label strings on Tickets. Segments defined in the Crisp CRM have no Zendesk equivalent and are documented as a static reference list for the customer's admin to recreate as Zendesk Views or Saved Searches. Workflows, automations, and the chatbot builder do not migrate as code; we deliver a written inventory of routing rules and Crisp automation steps for the customer's Zendesk admin to rebuild as Triggers and Automations post-migration.

1:1

Conversation → Ticket

Crisp Conversations are the primary thread object and map directly to Zendesk Tickets.

How it maps

Each Conversation carries a website_id, a contact reference, a set of Messages, and operator assignments. We translate the Crisp created_at and updated_at timestamps to Zendesk Ticket created_at and updated_at, and map the Crisp resolve status to Zendesk Ticket status (Open, Pending, Solved, Closed). The Crisp conversation URL maps to a Zendesk external_id so the original thread remains referenceable.

1:1

Message → Comment

Crisp Messages are nested inside Conversations and include body text, attachment references, author metadata, and author_type (operator vs. visitor).

How it maps

We map Messages to Zendesk Ticket Comments preserving body content, author identity (operator emails resolve to Zendesk Agent User records), and timestamp. Public vs. private message visibility in Crisp maps to Zendesk public=true (Comment public=true) or public=false (Internal Comment).

1:1

Contact → End-User or Agent (User)

Crisp Contacts are stored in the CRM module (Essentials tier and above) with standard fields (email, name, phone) plus dynamic custom properties.

How it maps

We extract all Contact properties and map them to Zendesk User fields: standard fields map directly (email, name, phone), and custom properties map to Zendesk User Fields. Accounts on Free or Mini tiers with no CRM access may have limited Contact export capability; we confirm API key availability and use the /contacts endpoint as a workaround for lower-tier accounts.

1:1

Operator → Agent (User)

Crisp Operators map to Zendesk Agent User records.

How it maps

We resolve operators by email match against the Zendesk User table. Role-based permissions in Crisp (admin vs. standard operator) map to Zendesk roles (admin vs. agent). Any operator count that exceeds the destination Zendesk Suite plan seat allowance is flagged for the customer to resolve (deactivate or upgrade the destination plan) before migration.

configuration

Website → Channel Routing Configuration

A Crisp Website represents a configured chat widget tied to a domain, holding widget settings, enabled channels, and routing rules.

How it maps

Zendesk has no direct Website equivalent. We extract the Website configuration as a structured snapshot and translate enabled channel types (email, chat, WhatsApp, SMS) into Zendesk channel routing by setting the Ticket channel field and configuring corresponding Zendesk Views per channel. Widget theme and greeting settings do not migrate directly; these require manual reconfiguration in Zendesk Guide or the customer's web team.

1:1

Tag → Tag

Crisp Tags are applied to Conversations to categorize them (urgent, billing, onboarding).

How it maps

Tags carry as plain string labels across the migration. We associate the full tag set with migrated Zendesk Tickets. Note that Zendesk tag limits are enforced at the account level; very large tag sets (hundreds of unique tags) should be reviewed for consolidation during scoping.

What moves12 objects
CrispZendesk
  • ConversationTicket1:1
  • MessageComment1:1
  • ContactEnd-User or Agent1:1
  • OperatorAgent1:1
  • WebsiteChannel Routing Configurationtransformed
  • TagTag1:1

+ 6 more in the mapping below

How Crisp and Zendesk 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.

DimensionCrispZendesk
Core object modelConversations (thread) as primary, with Messages nested insideTickets as primary, with Comments nested inside
Contact CRM moduleGated behind Essentials tier ($95/workspace/mo); Free/Mini cannot export contacts via UIContacts as standard User/End-User objects at all Suite tiers
Channel routingEmail, chat, WhatsApp, SMS per Website configuration in a single shared inboxChannel routing via Ticket field, separate views per channel in Suite Professional+
Operator seat modelPer-workspace seat caps: 2 on Free, fixed on Mini, up to 5 on Essentials, expanded on PlusPer-agent pricing on Suite Suite Team ($29/agent) through Enterprise with explicit seat management
Automation builderChatbot and workflow builder included from Essentials, scoped to the workspaceTriggers and Automations from Suite Professional, with macros from Suite Team
AI feature modelAI Copilot and auto-reply via credit budget that does not roll overAdvanced AI add-on at $50/agent/mo on top of Suite plan; credits carry and scale
Reporting depthDashboard per workspace with limited cross-channel drill-downAdvanced analytics, custom reporting types, and Explore workspace at Suite Professional+

What to watch for in a Crisp to Zendesk 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 tier or API access

Crisp's UI-based CSV contact export is gated behind the Essentials plan ($95/workspace/mo).

How we handle it

Free and Mini tier accounts cannot trigger a bulk export from the UI even if Contact records exist. We work around this by pulling Contact data directly from the Crisp REST API /contacts endpoint, which is accessible with an API key regardless of tier. We confirm API key availability and scope during the discovery call and use the API export path for lower-tier accounts. If no API key exists, the customer must upgrade to Essentials or provision one before migration begins.

medium

Crisp Segments have no Zendesk equivalent

Crisp Segments are dynamic Contact filters defined by rule conditions (property-based rules) in the CRM module.

How we handle it

Zendesk does not have a dynamic segmentation object; Saved Searches and Views are static filters applied at query time. We preserve segment definitions as structured metadata in a written inventory, but these cannot be migrated as functional data structures. The customer rebuilds them in Zendesk as Views or through a third-party segmentation tool post-migration. This is a functional gap, not a data loss gap; the Contacts themselves migrate completely.

medium

Canned Response variable syntax does not map to Zendesk Macro variables

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

How we handle it

Zendesk Macros use {{ticket.requester.name}} and similar curly-brace variable formats. A direct migration of Canned Response templates would result in broken or literal placeholder text in Zendesk Tickets. We export all Canned Responses as plain-text structured records with the placeholders preserved as-is, then flag them for manual adaptation in Zendesk. Each template requires a manual review step to update the variable syntax to Zendesk's format. This adds planning time but prevents silent data corruption.

medium

Crisp API rate limits require controlled read throttling

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

How we handle it

The API global limit is the primary constraint for migration scripts pulling Conversations and Contacts in bulk. We implement exponential backoff and respect the Retry-After header on 429 responses. For large migrations we throttle reads to below the global limit to avoid disrupting live API access that the customer may still need for operational use during migration. This extends migration timelines but preserves production system availability.

low

Crisp contact export ceiling of 200,000 records

Crisp's documented contact export limit is 200,000 records per export operation.

How we handle it

Accounts with more than 200,000 Contacts require multiple export passes with date or ID-range filters. We sequence these exports as sequential chunks, deduplicating on contact_id across passes, then reassemble the full dataset before loading into Zendesk. This adds a modest amount of planning time but does not block migration. We verify the total contact count during discovery and plan the chunking strategy accordingly.

How the migration runs

  1. Discovery and API capability assessment

    We audit the source Crisp account across plan tier, enabled channels, Conversation volume, Contact count, operator roster, active Tags, Canned Responses, and Website configurations.

    What this step covers

    We confirm API key availability and scope (required for Free/Mini tier Contact exports). We assess whether the account uses the CRM module and whether Segments are in active use. The discovery output is a written migration scope document identifying every object to be migrated, the channel routing plan, the Canned Response review list, and any seat-count reconciliation items against the destination Zendesk Suite plan.

  2. Zendesk environment preparation

    We configure the destination Zendesk environment before any data moves: we provision User Fields for Crisp Contact custom properties, configure Ticket Fields for channel metadata and Conversation context (page_url, browser, website_id), create Views per enabled channel (email, chat, WhatsApp, SMS), and set up Zendesk Macros for the Canned Response review list.

    What this step covers

    We coordinate with the customer's Zendesk admin to ensure the migration user has the necessary API permissions and that validation rules will not block the incoming data.

  3. Pilot migration to Zendesk Sandbox

    We run a full migration into a Zendesk Sandbox using production-like data volume.

    What this step covers

    The customer reconciles record counts (Tickets in, Comments in, Users in), spot-checks 25-50 random Tickets against the Crisp source, and verifies that operator attribution, message threading, and tag associations look correct. Any mapping corrections, field type mismatches, or custom field schema changes happen in Sandbox before production migration begins.

  4. Operator and user reconciliation

    We extract every distinct Crisp Operator referenced on Conversations and Messages and match by email against the Zendesk destination User table.

    What this step covers

    Any Operator without a matching Zendesk User goes to a reconciliation queue. The customer's Zendesk admin provisions missing Users (active or inactive depending on whether the original Crisp operator is still active) before record import resumes. Migration cannot proceed past this step because AuthorId references on Comments require valid User records.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Users (provisioned and validated), Contacts (mapped to End-Users with custom fields), Conversations (mapped to Tickets with channel field set and external_id carrying the Crisp Conversation ID), Messages (mapped to Ticket Comments with author resolved to Zendesk User and public/internal visibility preserved), Attachments (re-uploaded and linked to Comments), Tags (applied to Tickets), and Canned Responses (delivered as a structured inventory document with variable syntax flagged).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, final delta, and automation handoff

    We freeze Crisp writes during the cutover window, run a final delta migration of any Conversations or Contacts modified during the migration period, then enable Zendesk as the system of record.

    What this step covers

    We deliver the Canned Response adaptation guide (with placeholder syntax updated to Zendesk format), the Segment inventory document (for manual Zendesk View recreation), and the Chat Widget configuration snapshot (for the customer's web team to reconfigure the Zendesk Web Widget). We support a one-week hypercare window to resolve reconciliation issues. We do not rebuild Crisp automations or chatbots as Zendesk Triggers and Automations inside the migration scope; that is a separate engagement.

Crisp Zendesk
  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 · ZendeskRollback 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

3-5 weeksTypical, smaller accounts
6-10 weeksLarge or heavily customised accounts

A quote scales with record volume, number of channels in use, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Crisp to Zendesk →

Why teams move from Crisp to Zendesk

  • Crisp's per-workspace seat caps create a scaling ceiling. Free is capped at 2 seats and Mini at a fixed small count, while Zendesk Suite Team starts at $29 per agent with explicit seat management that grows with the team. Growing support teams migrating from Crisp hit the seat wall and move to Zendesk because per-agent pricing scales predictably without the per-workspace constraint.
  • Zendesk's SLA management, multi-team routing, and advanced automation rules serve larger support organizations better than Crisp's workspace-scoped automation builder. Reddit discussions on helpdesk alternatives note that multi-team routing at scale, complex SLA policies, and reporting beyond ticket counts are the specific capabilities that differentiate Zendesk for teams managing more than 10 agents.
  • Crisp's credit-gated AI model ($Copilot and auto-reply) creates unpredictable monthly costs because unused credits do not roll over between billing cycles. Zendesk's Advanced AI add-on ($50/agent/mo on top of the Suite plan) scales with the team and provides consistent access to AI-assisted triage, agent assist, and macro generation without a monthly credit ceiling.
  • Customer support quality has declined in recent Crisp reviews, with users reporting delayed responses on technical issues and extended resolution times during critical migrations. Teams with high-urgency support requirements cite responsive vendor support as a factor in switching to Zendesk's professional services and documentation ecosystem.
  • Zendesk's platform maturity and ecosystem depth offer enterprise integrations, advanced reporting, and an established partner marketplace that Crisp's younger ecosystem has not yet matched. For companies with existing ERP, CRM, or analytics stacks, Zendesk's AppExchange-certified integrations reduce custom development overhead post-migration.

Questions, answered

Crisp to Zendesk migration questions

How long does a Crisp to Zendesk migration take?

Most Crisp to Zendesk migrations land between three and five weeks for accounts under 50,000 Conversations and 25,000 Contacts with no complex multi-Website configuration. Migrations with large conversation histories (over 200,000 messages), multiple active Websites requiring separate Zendesk channel Views, or operator rosters that exceed the destination Suite plan seat count move to six to ten weeks because of chunking strategy, View configuration scope, and seat reconciliation.

Do Crisp Workflows and Chatbots migrate to Zendesk Triggers and Automations?

No. Crisp's chatbot and workflow builder configurations are tied to the Crisp automation model and do not export in a form that maps to Zendesk Triggers and Automations. Zendesk Triggers use conditions on Ticket fields and actions that update Tickets, assign Agents, or send notifications; Crisp automations include routing, delays, and CRM actions that have different semantics. We do not migrate them as code. We deliver a written inventory of every active Crisp automation with its trigger conditions, actions, and recommended Zendesk Trigger and Automation equivalents. The customer's Zendesk admin rebuilds them post-migration.

We use Segments in Crisp. Do they migrate?

Crisp Segments are dynamic Contact filters defined by rules against CRM properties. Zendesk does not have a dynamic segmentation object, so Segments cannot migrate as functional data structures. We preserve the segment rule definitions as structured metadata in a written inventory document (rule conditions, operator logic, and target Contact count). The customer recreates them as Zendesk Saved Searches or Views post-migration. The underlying Contacts and their properties migrate completely; only the dynamic filter definitions require manual rebuild.

Our Canned Responses have variable placeholders. Do they migrate correctly?

Crisp Canned Responses use %placeholder% syntax (e.g., %session.nickname%), which does not match Zendesk's {{ticket.requester.name}} macro variable format. A direct template migration would result in literal placeholder text appearing in Zendesk Tickets. We export all Canned Responses as structured records with placeholders preserved as-is, flag each one for manual adaptation, and deliver a Canned Response adaptation guide with the equivalent Zendesk variable syntax for each placeholder type. This is a manual step but takes minutes per template rather than hours.

What happens to our Attachments in Conversations?

File attachments uploaded to Crisp Messages are stored as URLs referencing Crisp's file storage. We preserve the attachment URLs, download the files, and re-upload them to Zendesk's file storage during migration, attaching each file to the corresponding Ticket Comment. Attachment integrity is verified against the original file hash before and after upload. File size limits vary by Zendesk Suite plan; we confirm limits during discovery and flag any attachments that exceed the destination plan's threshold.

We are on Crisp Free or Mini tier. Can we still migrate Contacts?

Yes, but with an extra step. The UI-based CSV contact export is only available on the Essentials plan or higher. We work around this by using the Crisp REST API /contacts endpoint, which is accessible with an API key regardless of tier. If no API key exists, the customer creates one in Crisp Settings before migration begins. There is no data loss; the API exports the same Contact records as the UI export, just accessed through a different path. The contact count ceiling of 200,000 per export pass still applies and requires chunking for larger datasets.

Can FlitStack AI migrate data from multiple Crisp Websites into a single Zendesk instance?

Yes. Multi-Website migrations are common for companies that run separate Crisp configurations per brand or domain. We consolidate all Websites into a single Zendesk instance, mapping each Website's channel configuration to separate Zendesk Views. The Website context (website_id, domain) is preserved as a custom Ticket field so agents can identify which website the conversation originated from. This is configured during the pre-migration Zendesk setup phase and is scoped as part of the standard migration engagement.

Get a quote

Moving from Crisp to Zendesk?

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

Get a quote