Migrate from Crisp

The Relay CLI can pull your contacts and conversations — with full message history — out of Crisp and push them into your Relay workspace, in one command.

Prerequisites

• The CLI installed and configured with a Relay API key that has the conversations:write and contacts:write scopes — see CLI → Configure.
• Crisp API credentials: a token identifier and token key from the Crisp Marketplace, plus your website ID from the Crisp dashboard.

1. Configure Crisp credentials

relay config \
  --crisp-identifier <token-identifier> \
  --crisp-key <token-key> \
  --crisp-website-id <website-id>

2. Preview, then migrate

Always do a dry run first — it fetches from Crisp and reports counts without writing anything to Relay.

relay migrate all --dry-run     # see what would happen, writes nothing
relay migrate all               # contacts, then conversations + messages

Granular variants if you'd rather run them separately:

relay migrate contacts          # Crisp people → Relay contacts
relay migrate conversations     # Crisp convos → Relay conversations + messages

Options

All migrate subcommands accept:

How data is mapped

• Contacts are de-duplicated by email against existing Relay contacts, so re-running the migration won't create duplicates. Crisp segments, phone number, and IDs are preserved in customAttributes (tagged source: "crisp").
• Messages keep their direction: a Crisp operator message becomes an outgoing (agent) message, a visitor message becomes incoming. File and attachment payloads are imported as text references; Crisp events are skipped.
• State maps resolved → resolved, pending → pending, and unresolved → open. Status is applied after the messages are replayed, so an imported message doesn't accidentally reopen a resolved thread.