Migrate your ConSol data
German enterprise IT service desk and case management platform built on BPM, with cloud and on-premise deployments serving large organizations.
In its favor
Why people choose ConSol
The signal that keeps ConSol on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Full lifecycle management for IT support combining incident tracking, service requests, and change management in one platform according to Capterra descriptions.
ISO 27001 certification provides enterprise security credibility for organizations handling sensitive IT service data.
Cloud-based access allows support teams to log in from anywhere, a feature highlighted in G2 reviews as practical for distributed teams.
German domestic development and hosting appeals to organizations with strict data residency or GDPR compliance requirements.
Established customer base of large German enterprises including Daimler, Fraport, and public institutions validates enterprise readiness.
Limited integration with external CRM systems noted as a frustration in G2 reviews, with users unable to connect ConSol CM to their primary customer platforms.
Complex feature set and steep learning curve reported in G2 feedback, with users feeling overwhelmed by information density during onboarding.
Perpetual licensing and enterprise pricing structure makes the platform costly for smaller organizations evaluating alternatives.
Vendor lock-in concerns with proprietary German-developed platform motivating organizations to evaluate international alternatives with broader ecosystem support.
Reasons to switch
Why people leave ConSol
The recurring reasons buyers give for replacing ConSol. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where ConSol 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 pricing overview
ConSol CM offers both cloud subscription and on-premise licensing, with a Named User and Concurrent User model on each. Cloud subscription is €59/named user/month or €89/concurrent user/month plus a €149 monthly base; minimum 6 named or 4 concurrent users. On-premise perpetual licensing is €690 per named user or €1,190 per concurrent user, plus a one-time €9,900 server license. On-premise subscription is €275/user/month plus a monthly server fee of €19 (named) or €33 (concurrent). All tiers require direct sales engagement; no free trial or self-serve sign-up is published.
Cloud Subscription (Named User)
Tier 1 of 4
€59/named user/month + €149 monthly base (minimum 6 users)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on ConSol's schedule — see our quote-based pricing →
What gets migrated
ConSol object support
Object-by-object support for ConSol migrations. Per-pair details surface during scoping.
Requests
Mapping requiredRequests are the central case/ticket object. We export the full request record including status, priority, timestamps, and linked contacts. Custom request fields require field-level mapping at scoping.
Contacts
Fully supportedContact records export cleanly with standard fields. The ContactModels documentation confirms a stable schema for name, email, phone, and organizational links.
Organizations
Mapping requiredCompany/account-level records are supported. The organization-contact relationship must be preserved during import to maintain the hierarchy in the destination system.
Attachments
Mapping requiredRequest attachments export via the REST API but require a separate pass after the record import. File naming conventions and storage location mapping add a step to the migration sequence.
Scripts/Automations
Not in this platformCustom scripting and workflow automations are not exported via API. These are rebuilt manually on the destination platform post-migration.
SLA Configurations
Not in this platformSLA rules and escalation policies are not exposed in the public API. We document them as part of the requirements scope but cannot transfer them automatically.
Change Records
Mapping requiredChange management records linked to requests can be exported. These are mapped as linked objects to their parent Requests in the destination.
Users/Agents
Mapping requiredAgent accounts and team assignments export, but role and permission sets vary by ConSol edition and must be reviewed against the destination's access model.
| Object | Support | Notes |
|---|---|---|
| Requests | Mapping required | Requests are the central case/ticket object. We export the full request record including status, priority, timestamps, and linked contacts. Custom request fields require field-level mapping at scoping. |
| Contacts | Fully supported | Contact records export cleanly with standard fields. The ContactModels documentation confirms a stable schema for name, email, phone, and organizational links. |
| Organizations | Mapping required | Company/account-level records are supported. The organization-contact relationship must be preserved during import to maintain the hierarchy in the destination system. |
| Attachments | Mapping required | Request attachments export via the REST API but require a separate pass after the record import. File naming conventions and storage location mapping add a step to the migration sequence. |
| Scripts/Automations | Not in this platform | Custom scripting and workflow automations are not exported via API. These are rebuilt manually on the destination platform post-migration. |
| SLA Configurations | Not in this platform | SLA rules and escalation policies are not exposed in the public API. We document them as part of the requirements scope but cannot transfer them automatically. |
| Change Records | Mapping required | Change management records linked to requests can be exported. These are mapped as linked objects to their parent Requests in the destination. |
| Users/Agents | Mapping required | Agent accounts and team assignments export, but role and permission sets vary by ConSol edition and must be reviewed against the destination's access model. |
Gotchas
What to watch for in ConSol migrations
Issues we've hit on past ConSol migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
REST API documentation is fragmented across multiple moved URLs
Workflow automations and SLA rules are not API-accessible
Attachment extraction requires a secondary pipeline pass
| Severity | Issue |
|---|---|
| High | REST API documentation is fragmented across multiple moved URLs |
| High | Workflow automations and SLA rules are not API-accessible |
| Medium | Attachment extraction requires a secondary pipeline pass |
Leaving ConSol?
Where ConSol customers move next
12 destinations ConSol can migrate to.
How a ConSol migration works
Four steps, ConSol-specific
Connect
OpenID Connect (OIDC) via ConSol's bundled authentication applications; credentials can be sourced from the ConSol CM database, LDAP, or an external SSO service into ConSol. Scopes limited to read-only on the data we move.
Map
We translate ConSol-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate ConSol quirks before production.
Migrate
Full migration with ConSol rate-limit handling. Rollback available throughout.
FAQ
ConSol migration FAQ
Answers to the questions buyers ask most during ConSol migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your ConSol migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate ConSol.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your ConSol setup and destination — written quote back within a business day.