Migrate your ConSol*CM data
Enterprise helpdesk and workflow management platform from German software company ConSol, designed for IT service desks and complaint-handling teams requiring deep process automation.
In its favor
Why people choose ConSol*CM
The signal that keeps ConSol*CM on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
ConSol CM is chosen for enterprise IT service management with deep workflow automation, including complex multi-step processes with conditions and decision branches.
The platform supports both Named User and Concurrent User pricing models, allowing large organizations to pay only for active seats rather than total registered users.
Customers use it for complaint handling and quality assurance tracking beyond basic ticket management, with integrated issue resolution workflows.
The German-origin product serves European enterprises requiring data residency compliance and local support infrastructure.
Its integrated dashboards and workflow-based automation features appeal to organizations with established ITSM processes seeking a structured ticketing solution.
Limited public API documentation makes integrations and automated workflows harder to maintain, especially for teams relying on third-party tools.
Smaller organizations report that the platform's enterprise complexity creates unnecessary overhead compared to simpler cloud-native helpdesk alternatives.
The platform lacks transparent public pricing with multiple quotes required, making cost comparisons and budget forecasting difficult for mid-market buyers.
General user reviews note that the interface and configuration require significant training investment before teams can operate independently.
The limited number of public reviews makes it difficult to assess real-world customer satisfaction trends and identify systemic issues.
Reasons to switch
Why people leave ConSol*CM
The recurring reasons buyers give for replacing ConSol*CM. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where ConSol*CM 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
ConSol*CM pricing overview
ConSol CM uses a Named User model starting at €59 per activated user per month plus a €149 monthly base fee, with a 6-user minimum. A Concurrent User model is available for organizations wanting to pay for peak simultaneous sessions rather than total registered users, with pricing requiring direct consultation with ConSol sales.
Named User
Tier 1 of 2
€59/user/month (activated user) + €149/month base price
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on ConSol*CM's schedule — see our quote-based pricing →
What gets migrated
ConSol*CM object support
Object-by-object support for ConSol*CM migrations. Per-pair details surface during scoping.
Requests (Tickets)
Fully supportedRequests are the primary ticket object in ConSol CM, supporting custom field groups and status workflows. We extract all Request fields, attachments, and conversation history via the REST API and map them to the destination's ticket schema.
Contacts
Mapping requiredConSol CM uses an extensible Contact model with field groups. Custom fields and contact models require explicit mapping to destination fields. The system documentation feature exports configuration that we cross-reference during schema mapping.
Resources
Mapping requiredResources represent internal staff or system entities. User assignments on Requests and workflows must be remapped to the destination's owner/user model, as naming conventions and ID structures differ between systems.
Workflows
Mapping requiredConSol CM workflows use activities, conditions, and decisions to model business processes. Workflow configurations are not directly transferable via API; we document the workflow logic and flag manual redeployment requirements during scoping.
Conversations
Fully supportedConversations linked to Requests are exported via the REST API and imported as message threads in the destination. We preserve timestamps, author attribution, and internal/external flags.
Attachments
Fully supportedFile attachments associated with Requests and Contacts are downloaded and re-uploaded to the destination. We handle filename deduplication and verify attachment size limits on the target system.
Field Groups
Mapping requiredField groups define custom property sets on Contacts and Requests. We extract the field group configuration via the system documentation export and map each field individually to the destination schema.
Tags
Mapping requiredTags on Requests and Contacts are exported as flat lists. We map them to the destination's tagging schema, flagging any tag naming conflicts during the import dry-run.
KB Articles
Mapping requiredKnowledge base articles can be exported from ConSol CM but the KB structure (categories, article hierarchy) requires manual mapping to the destination system. We extract article content and metadata for structured re-import.
Teams
Mapping requiredTeam structures in ConSol CM map to organizational units in the destination. We preserve team-to-agent assignments and flag any permission model differences that affect ticket routing.
Data Fields (empty/null values)
Fully supportedVersion 6.17.1 extended the REST API to search for records where specific data fields have no value set. We use this to identify incomplete records during the profiling phase and flag them for customer review before migration.
System Configuration (Export)
Mapping requiredConSol CM's system documentation feature exports system configuration to a file. We review this export to understand custom objects, field definitions, and workflow settings before scoping the migration scope.
| Object | Support | Notes |
|---|---|---|
| Requests (Tickets) | Fully supported | Requests are the primary ticket object in ConSol CM, supporting custom field groups and status workflows. We extract all Request fields, attachments, and conversation history via the REST API and map them to the destination's ticket schema. |
| Contacts | Mapping required | ConSol CM uses an extensible Contact model with field groups. Custom fields and contact models require explicit mapping to destination fields. The system documentation feature exports configuration that we cross-reference during schema mapping. |
| Resources | Mapping required | Resources represent internal staff or system entities. User assignments on Requests and workflows must be remapped to the destination's owner/user model, as naming conventions and ID structures differ between systems. |
| Workflows | Mapping required | ConSol CM workflows use activities, conditions, and decisions to model business processes. Workflow configurations are not directly transferable via API; we document the workflow logic and flag manual redeployment requirements during scoping. |
| Conversations | Fully supported | Conversations linked to Requests are exported via the REST API and imported as message threads in the destination. We preserve timestamps, author attribution, and internal/external flags. |
| Attachments | Fully supported | File attachments associated with Requests and Contacts are downloaded and re-uploaded to the destination. We handle filename deduplication and verify attachment size limits on the target system. |
| Field Groups | Mapping required | Field groups define custom property sets on Contacts and Requests. We extract the field group configuration via the system documentation export and map each field individually to the destination schema. |
| Tags | Mapping required | Tags on Requests and Contacts are exported as flat lists. We map them to the destination's tagging schema, flagging any tag naming conflicts during the import dry-run. |
| KB Articles | Mapping required | Knowledge base articles can be exported from ConSol CM but the KB structure (categories, article hierarchy) requires manual mapping to the destination system. We extract article content and metadata for structured re-import. |
| Teams | Mapping required | Team structures in ConSol CM map to organizational units in the destination. We preserve team-to-agent assignments and flag any permission model differences that affect ticket routing. |
| Data Fields (empty/null values) | Fully supported | Version 6.17.1 extended the REST API to search for records where specific data fields have no value set. We use this to identify incomplete records during the profiling phase and flag them for customer review before migration. |
| System Configuration (Export) | Mapping required | ConSol CM's system documentation feature exports system configuration to a file. We review this export to understand custom objects, field definitions, and workflow settings before scoping the migration scope. |
Gotchas
What to watch for in ConSol*CM migrations
Issues we've hit on past ConSol*CM migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Workflow configurations are not programmatically exportable
Limited public API documentation for rate limits and bulk operations
Custom field groups require manual field-level mapping
Concurrent User pricing requires usage analysis before scoping
| Severity | Issue |
|---|---|
| High | Workflow configurations are not programmatically exportable |
| Medium | Limited public API documentation for rate limits and bulk operations |
| Medium | Custom field groups require manual field-level mapping |
| Low | Concurrent User pricing requires usage analysis before scoping |
Leaving ConSol*CM?
Where ConSol*CM customers move next
7 destinations ConSol*CM can migrate to.
How a ConSol*CM migration works
Four steps, ConSol*CM-specific
Connect
REST API with authentication configured per ConSol CM installation; specific OAuth/Basic/JWT support depends on the version deployed and the customer's tecdoc configuration (commonly token-based for CM/Track and integration use) into ConSol*CM. Scopes limited to read-only on the data we move.
Map
We translate ConSol*CM-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate ConSol*CM quirks before production.
Migrate
Full migration with ConSol*CM rate-limit handling. Rollback available throughout.
FAQ
ConSol*CM migration FAQ
Answers to the questions buyers ask most during ConSol*CM migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your ConSol*CM 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 ConSol*CM.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your ConSol*CM setup and destination — written quote back within a business day.