Migrate your Crisp data

Conversations is the core thread object in Crisp. Each Conversation carries a website ID, a contact reference, a set of Messages, and operator assignments. We map Conversations to Tickets in most destination systems, preserving the full message history, timestamps, and channel origin.

Crisp Contacts are stored in the CRM module, available from Essentials tier upward. Contacts have standard fields (email, name, phone) plus a dynamic set of custom properties. We extract all properties and map them to equivalent custom fields in the destination, handling differences in property types (string vs. date vs. number). Contacts without CRM access (Free/Mini) cannot be exported via the UI but remain accessible through the REST API.

Messages are nested inside Conversations and include text content, attachment references, and author metadata (operator vs. visitor). We preserve the message body, author identity, timestamp, and attachment URLs during migration. Inline images and files are mapped to the destination's attachment model.

A Website in Crisp represents a configured chat widget tied to a domain. Websites hold widget settings, enabled channels, and routing rules. When migrating out of Crisp, we extract the Website configuration and translate routing preferences to the destination's inbox or queue settings. Website-to-website mapping requires a scoping decision about which domain(s) to reassign.

Operators are user accounts in Crisp, tied to seat counts per plan. We map Operator records to Users or Agents in the destination, preserving display name and email. Role-based permissions (admin vs. agent) are translated to equivalent permission schemas. The 2-seat limit on Free and the seat cap on Mini tiers means large teams may have multiple operator records that need explicit destination user creation.

Tags in Crisp are applied to Conversations to categorize them (e.g., 'urgent', 'billing', 'onboarding'). We carry all Tags as label strings and associate them with the migrated conversation threads in the destination, recreating the tagging taxonomy.

Segments are dynamic Contact filters defined in the Crisp CRM (Essentials+). They are defined by rules against Contact properties. We preserve the segment rule definitions as structured metadata and can recreate equivalent segments in the destination CRM if it supports dynamic audience rules.

Canned Responses are pre-written message templates used by operators. We export these as a structured list and map them to the destination's saved replies or template system. Placeholder variables (%customer_name%, %ticket_id%) are preserved as raw text and may require manual reconfiguration in the destination.

Crisp's chat widget has theme, color, greeting message, and behavior configuration tied to each Website. We extract widget settings as configuration snapshots and translate them to the destination's widget or embed settings where supported.

File attachments uploaded to Messages are stored as URLs referencing Crisp's file storage. We preserve attachment URLs and re-upload files to the destination's storage during migration, ensuring attachments remain accessible without dependency on Crisp's CDN.