Importing from Crisp
How to migrate your support data from Crisp to Deskwoot
Updated September 30, 2026Also available in: Deutsch, Português
Bring conversations, contacts, operators (matched by email), shortcuts (become canned responses), knowledge base, and CSAT from Crisp. Connects via Crisp API — you supply Website ID + token Identifier + token Key. Chat widget customizations, routing rules, and Crisp plugins aren't imported. Read-only on Crisp side, so your Crisp account stays untouched during and after the migration.
Importing from Crisp into Deskwoot connects directly to the Crisp API and brings over conversations with full message history, contacts, and knowledge base articles in a few minutes, no CSV export needed. You can bring over your conversations, contacts, and knowledge base in just a few minutes. The built-in migration tool connects directly to the Crisp API, so there's no need to export CSV files or handle data manually.
What gets imported
- Conversations (sessions) with full message history and attachments
- Contacts (people) with email, phone, avatar, location, segments, and custom data
- Operators matched to existing Deskwoot users by email
- Shortcuts become Canned Responses
- Knowledge Base articles organized by locale and category
- CSAT Ratings (if available)
What is NOT imported
- Chat widget customizations and triggers
- Routing rules
- Crisp plugins and integrations
- Visitor analytics and device fingerprinting
Getting your API credentials
Before you begin, you'll need three values from your Crisp account:
- Go to your Crisp dashboard.
- Navigate to Settings > Website Settings > Setup Instructions to find your Website ID.
- Go to Crisp Token Settings and create a new API token. Make sure the token has read access to conversations, contacts, and knowledge base resources.
- Copy both the Identifier and Key. You will not be able to view the key again after leaving the page, so store it somewhere safe.
How to import
- In Deskwoot, go to Settings > Import / Migration.
- Select Crisp from the list of available sources.
- Enter your Website ID, Token Identifier, and Token Key.
- Click Start Import.
- Wait for the progress bar to complete. Larger accounts may take several minutes depending on the volume of conversations.
Best-practice tips
- Create your team first. Because operators are matched by email, make sure all relevant team members already have Deskwoot accounts before you start the import. Unmatched operators will still appear in conversation history, but they won't be linked to active user profiles.
- Run the import during off-peak hours. This avoids notification noise for your team while historical conversations are being created.
- Review your Canned Responses after import. Shortcut formatting may differ slightly between platforms, so a quick review ensures everything reads correctly.
Troubleshooting
- Authentication error: Double-check that you copied the Token Identifier and Key without extra spaces. Regenerate the token in Crisp if the error persists.
- Missing conversations: Confirm your API token has sufficient read permissions. Tokens with limited scope may skip certain data types.
- Import seems stuck: Large accounts with thousands of conversations can take a while. Refresh the page to check progress. If the import has truly stalled, try starting a new one,duplicate records are handled automatically.
Frequently asked questions
Can I run the import more than once?
Yes. The importer detects previously imported records and avoids creating duplicates, so it is safe to re-run if your first attempt was incomplete.
Will the import affect my live Deskwoot inbox?
Imported conversations are brought in with their original timestamps and statuses. They will not trigger new notifications or automation rules, so your day-to-day workflow stays uninterrupted.
Do I need to keep my Crisp account active after importing?
No. Once the import is complete, all transferred data lives entirely within Deskwoot. You can deactivate or close your Crisp account whenever you're ready.