Migrate from Crisp to Gorgias

Crisp Conversations map to Gorgias Tickets. The primary transform maps Crisp conversation state (active, resolved, unread) to Gorgias ticket status (open, pending, resolved, closed). We preserve the Crisp conversation_id as an external_id field on the Gorgias ticket for cross-referencing. All nested Messages migrate as ticket conversation entries in chronological order, with author attribution (operator versus visitor) preserved as the ticket message author metadata.

Crisp Contacts (CRM module, Essentials tier or higher) map to Gorgias Customers. Standard fields (email, name, phone) map directly. All Crisp custom properties migrate as typed Gorgias Customer attributes (string, boolean, date, number). For accounts on Crisp Free or Mini tier without CRM UI access, we extract contacts via the REST API /contacts endpoint using an API key, which is accessible at any tier. Accounts exceeding 200,000 contacts require sequential API chunks with date or ID-range filters; we deduplicate on contact_id across passes and reassemble before loading.

Messages are nested inside Crisp Conversations and include text body, attachment references, and author metadata. Each message migrates as a ticket conversation entry in Gorgias, preserving the message body, author identity (operator or visitor), timestamp, and any inline attachment references. Attachment URLs pointing to Crisp file storage are re-hosted to Gorgias storage during migration so that inline images and files remain accessible in the ticket view.

Crisp Operators map to Gorgias Agents by email match. Display name, email, and role (admin versus operator) migrate. We flag any operator count that exceeds the destination Gorgias plan's seat allowance before migration, and the customer decides whether to deactivate operators in Crisp before migration or upgrade the destination plan.

Crisp Tags applied to Conversations migrate as Gorgias ticket tags. Tags are carried as label strings and associated with the migrated ticket threads. The customer reviews the resulting tag set in Gorgias post-migration to consolidate or rename any tags that do not map cleanly to the destination naming convention.

Crisp Segments are dynamic Contact filters defined by rule sets against Contact properties (Essentials tier and above). We preserve the segment rule definitions as structured metadata in the migration inventory. Gorgias does not have an equivalent dynamic segment object; customer filters are defined per-rule inside the platform. We deliver a written list of each Crisp Segment with its rule logic for the customer's admin to rebuild as Gorgias customer filters or as a basis for macro and automation triggers.

Crisp Canned Responses use %placeholder% variable syntax (for example, %session.nickname%). Gorgias Saved Replies use a different variable format. We export Canned Responses as plain text with placeholders intact and flag them for manual review in Gorgias so the customer's admin can adapt them to the destination variable format. This is a configuration inventory item, not an automated migration.

A Crisp Website represents a configured chat widget tied to a domain, holding widget settings, enabled channels, and routing rules. We extract Website configuration as a structured snapshot and deliver it as a written inventory. Chat widget theme, color, greeting message, and routing behavior do not migrate automatically to Gorgias; the customer's admin rebuilds these in Gorgias channel and inbox settings.

File attachments uploaded to Crisp Messages are stored as URLs referencing Crisp's file storage. We preserve attachment URLs and re-upload files to Gorgias storage during migration. All attachments land as ticket-level attachments on the corresponding migrated ticket, with the original filename and content type preserved.

Crisp chat widget has theme, color, greeting message, and behavior configuration tied to each Website. We extract widget settings as configuration snapshots. Gorgias channel settings for web chat (appearance, trigger rules, greeting) are configured separately inside the platform. We deliver a written widget configuration inventory for the customer's admin to reassign in Gorgias; this is not an automated configuration transfer.

Crisp operator roles (admin versus standard operator) map to Gorgias Agent roles. We preserve the role assignment on each agent record. Gorgias permission granularity (full access, ticket management, reporting only) may differ from Crisp's role model; the customer reviews role assignments post-migration.

Crisp Contact custom properties of any type (string, boolean, date, number, list) migrate as Gorgias Customer custom attributes of the corresponding type. We validate type compatibility during scoping and flag any Crisp property type that does not have a direct Gorgias equivalent for the customer's admin to review.