Migrate your CDESK data
European helpdesk and service desk platform for standardizing request workflows, tracking work time, and enforcing SLA and SLO deadlines across departments.
In its favor
Why people choose CDESK
The signal that keeps CDESK on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Low entry price at €20 per month attracts small teams evaluating basic helpdesk functionality before committing to larger platforms like Freshservice or Jira Service Management.
Internal-facing request management across multiple departments appeals to organizations that need SLA tracking beyond just the IT helpdesk.
Custom Properties allow non-technical administrators to extend the data model without developer involvement, reducing customization overhead.
SLA and SLO deadline enforcement built into the core workflow satisfies compliance requirements in regulated industries without third-party plugins.
The Priority View provides at-a-glance visibility into pending versus overdue requests, which appeals to managers tracking team performance manually.
One reviewer noted the product felt "below starter level," suggesting feature gaps compared to established helpdesk competitors for teams with mature workflows.
Limited public documentation and community presence make it difficult for teams to self-serve troubleshooting and best-practice discovery.
Sparse third-party integrations beyond native channels means organizations with complex tool stacks face manual data re-entry or custom development costs.
No visible API documentation found in public research raises concerns for technical teams that require programmatic access for automation and reporting.
Reasons to switch
Why people leave CDESK
The recurring reasons buyers give for replacing CDESK. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where CDESK fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
CDESK pricing overview
CDESK is available starting at €20.00 per month as a single entry-level tier. No tier-specific feature breakdowns were found in public research, and pricing for additional users or enterprise features was not published at time of discovery.
Base Plan
Tier 1 of 1
€20.00 per month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on CDESK's schedule — see our quote-based pricing →
What gets migrated
CDESK object support
Object-by-object support for CDESK migrations. Per-pair details surface during scoping.
Requests
Fully supportedRequests are the primary ticket object in CDESK. We migrate Requests with their standard fields (title, description, status, priority, assignee, created/modified dates) and preserve any custom field values stored in Custom Properties attached to the request.
Custom Properties
Mapping requiredCDESK allows administrators to add arbitrary custom fields to Requests via Custom Properties. We extract these as key-value pairs and map them to the destination platform's equivalent custom field mechanism, preserving data types where possible.
Request Templates
Not in this platformRequest Templates define the structure for creating new Requests but do not hold instance data. These are configuration artifacts and are not migrated as data records. We document their existence so customers can recreate them in the target platform.
Regular Requests
Not in this platformRegular Requests are automated ticket generation rules configured within CDESK. These are scheduling rules, not data records, and cannot be directly migrated. We flag their existence and advise customers to reconfigure equivalent automation in the target platform.
Priority View
Mapping requiredPriority View is a filtering and sorting configuration for the request list, not a data object itself. We do not migrate it directly but preserve the priority and deadline values on each Request so the same view can be recreated in the destination platform.
Deals
Mapping requiredCDESK includes a Deals module for managing sales opportunities from registration through billing. We migrate Deal records including linked tasks, cost estimates, and documents. Task completion statuses require field-level mapping to the destination CRM's opportunity task model.
SLA/SLO Configurations
Mapping requiredSLA and SLO deadlines are attached to Requests and define response and resolution windows. We carry forward the configured SLA name and deadline timestamps. The actual SLA rule definitions may differ between platforms and require manual alignment post-migration.
Attachments
Mapping requiredFile attachments on Requests and Deals are migrated as binary blobs alongside their parent record. We preserve filenames and attachment order. Large attachments may require chunked transfer depending on the destination platform's file size limits.
| Object | Support | Notes |
|---|---|---|
| Requests | Fully supported | Requests are the primary ticket object in CDESK. We migrate Requests with their standard fields (title, description, status, priority, assignee, created/modified dates) and preserve any custom field values stored in Custom Properties attached to the request. |
| Custom Properties | Mapping required | CDESK allows administrators to add arbitrary custom fields to Requests via Custom Properties. We extract these as key-value pairs and map them to the destination platform's equivalent custom field mechanism, preserving data types where possible. |
| Request Templates | Not in this platform | Request Templates define the structure for creating new Requests but do not hold instance data. These are configuration artifacts and are not migrated as data records. We document their existence so customers can recreate them in the target platform. |
| Regular Requests | Not in this platform | Regular Requests are automated ticket generation rules configured within CDESK. These are scheduling rules, not data records, and cannot be directly migrated. We flag their existence and advise customers to reconfigure equivalent automation in the target platform. |
| Priority View | Mapping required | Priority View is a filtering and sorting configuration for the request list, not a data object itself. We do not migrate it directly but preserve the priority and deadline values on each Request so the same view can be recreated in the destination platform. |
| Deals | Mapping required | CDESK includes a Deals module for managing sales opportunities from registration through billing. We migrate Deal records including linked tasks, cost estimates, and documents. Task completion statuses require field-level mapping to the destination CRM's opportunity task model. |
| SLA/SLO Configurations | Mapping required | SLA and SLO deadlines are attached to Requests and define response and resolution windows. We carry forward the configured SLA name and deadline timestamps. The actual SLA rule definitions may differ between platforms and require manual alignment post-migration. |
| Attachments | Mapping required | File attachments on Requests and Deals are migrated as binary blobs alongside their parent record. We preserve filenames and attachment order. Large attachments may require chunked transfer depending on the destination platform's file size limits. |
Gotchas
What to watch for in CDESK migrations
Issues we've hit on past CDESK migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public API for bulk data extraction
Request Templates and Regular Requests do not migrate as data
SLA/SLO values migrate as data, not as rules
| Severity | Issue |
|---|---|
| High | No documented public API for bulk data extraction |
| Medium | Request Templates and Regular Requests do not migrate as data |
| Medium | SLA/SLO values migrate as data, not as rules |
Leaving CDESK?
Where CDESK customers move next
7 destinations CDESK can migrate to.
How a CDESK migration works
Four steps, CDESK-specific
Connect
Not publicly documented into CDESK. Scopes limited to read-only on the data we move.
Map
We translate CDESK-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate CDESK quirks before production.
Migrate
Full migration with CDESK rate-limit handling. Rollback available throughout.
FAQ
CDESK migration FAQ
Answers to the questions buyers ask most during CDESK migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your CDESK migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate CDESK.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your CDESK setup and destination — written quote back within a business day.