Import Zendesk tickets, users, and organizations using the Universal Importer with auto-detection and smart merge.
cStar auto-detects Zendesk exports and maps fields for you. Tickets, users, organizations, full conversation history. It all comes over.
Step 1: Export from Zendesk
- JSON export (recommended): Admin Center > Account > Data Export. Request a full export.
- CSV export: use Views to filter tickets, then export to CSV.
Step 2: Upload to cStar
Go to Settings → Team → Import and drop your file. cStar detects the Zendesk format automatically.
Field Mappings
| Zendesk | cStar |
|---|---|
| subject | Title |
| description | Description |
| status | Status (auto-translated) |
| priority | Priority (auto-translated) |
| tags | Tags |
| assignee_email | Assigned Agent |
| requester | Customer |
| created_at | Created Date (preserved) |
Status Translation
cStar's ticket statuses are open, pending, resolved, closed. Zendesk statuses normalize as follows:
| Zendesk | cStar |
|---|---|
| new | open |
| open | open |
| pending | pending |
| hold | pending |
| solved | resolved |
| closed | closed |
(There's no separate "New" status in cStar. Zendesk new becomes open.)
Conversations
If your JSON includes the comments array, cStar imports full conversation history. Each comment preserves author, timestamp, visibility, and content.
Custom Fields
Zendesk custom fields appear as custom_fields.12345. Map them to cStar custom fields in the mapping step.
What Doesn't Transfer
- Macros, triggers, and automations (platform-specific logic)
- Attachment binaries (URLs are preserved as references)
- Agent accounts (invite your team separately in Settings → Team → Team Members)
Tips
- cStar handles up to 10,000 records per import. Zendesk's built-in CSV export caps at 2,000 rows.
- JSON exports carry more data than CSV (comments, custom fields).
- If you already have some data in cStar, use merge strategies to avoid duplicates.