What Data Maps Where

How data from Crisp and Sleekplan is mapped into Convot's data model.

Updated June 11, 2026

This page explains how Convot maps source data into its own data model so you know what to expect after an import.

Crisp to Convot

Contacts (People)

💡

Crisp field	Convot field
Email	Email
Name	Name
Phone	Phone
Custom attributes	Stored on the contact

Contacts are scoped to your Organization in Convot, so the same person is recognized across all your apps. If a contact with the same email already exists, the importer updates their fields rather than creating a duplicate.

Conversations

💡

Crisp field	Convot field
Conversation thread	Conversation
Incoming message	Incoming message
Outgoing message	Outgoing message
Operator (agent)	Agent attribution on the message
Conversation created/updated timestamps	Preserved

Conversations are scoped to the specific Convot app you import into. The importer maps Crisp operators to Convot agents by email. If a Crisp operator’s email matches a Convot team member, their messages are attributed to that person. Otherwise messages are attributed to a system account.

Help center articles

💡

Crisp field	Convot field
Helpdesk locale	Language in the helpdesk
Article category	Article category
Article title	Article title
Article body (HTML)	Article body (markdown, converted)

After all articles are imported, Convot rewrites internal cross-links so relative article links in the body keep working correctly.

Sleekplan to Convot

Feature feedback (roadmap)

💡

Sleekplan field	Convot field
Post title	Roadmap item title
Post description	Roadmap item description
Post status	Roadmap item status
Submitter	Contact (created lazily if not already in Convot)
Votes	Votes on the roadmap item

Changelog

💡

Sleekplan field	Convot field
Entry title	Changelog entry title
Entry body	Changelog entry body
Published date	Published date

Comments

💡

Sleekplan field	Convot field
Comment body	Roadmap item comment
Commenter	Contact (created lazily)
Comment date	Comment date

Notes on contact deduplication

Both importers deduplicate contacts by email. A contact with the same email as an existing Convot contact is linked to that existing record rather than creating a new one.

For Sleekplan, contacts are created only for users who actually interacted with something (voted, submitted, commented). The full Sleekplan user base is not imported.

What is not imported

Crisp: operator passwords, Crisp billing data, and plugin configurations.
Sleekplan: user account passwords, private internal comments (if any), and scheduling or meeting data.

If something important isn’t covered, contact Convot support and we’ll see if we can add it.

Was this article helpful?

Importing from Crisp Importing from Sleekplan