Switch from Crisp to Opskeet

Import your Crisp operators, people, conversations, notes, files and help center into Opskeet. What you need and what moves.

Updated
On this page

You can import from Crisp in the app. It's free, and nothing imported is sent to anyone.

You need to be an owner or admin in Opskeet, and the owner of your Crisp workspace.

Get your Crisp keys

  1. In Crisp, open Settings → Workspace settings → Advanced configuration. Only a workspace owner can.
  2. Under REST API + MCP Server Tokens, click Create Token.
  3. Copy the API Identifier and API Key now: Crisp shows them once. If you lost the key, click Recreate Token. Other tools using the old one stop working.
  4. Find your Website ID in Workspace settings → Setup & Integrations.

Import

  1. In Opskeet, go to Settings → Import & export and click Crisp.
  2. Enter Website ID, API Identifier and API Key.
  3. Match teammates and choose options. See Switch to Opskeet.
  4. Click Start.

What moves

Operators, people (with their segments as tags), conversations with messages, notes and files, and help center folders and articles.

Doesn't move: Shortcuts, bot scenarios, campaigns and triggers. Crisp has no way to read Shortcuts: export them as CSV in Crisp and import that as canned replies.

Big inboxes take days

Crisp allows 10,000 requests a day. A large inbox pauses and continues on its own, so it can take a few days.

Your site's Crisp code

After you swap the snippet, $crisp.push([...]) calls keep working, including user:email with its signature once you save Crisp's identity verification secret. See Keep old sign-ins and links.

Finish

Follow the Switch over checklist: Switch to Opskeet.

Did this help?

Related articles