Migrate your iSupport Software data
On-premise and cloud ITSM help desk software with two tiers — Incident Management and full Service Desk — for small to midsize IT teams that need customizable ticket workflows without the enterprise complexity.
In its favor
Why people choose iSupport Software
The signal that keeps iSupport Software on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Organizations on a tight budget choose iSupport because Gartner Peer Insights reviewers describe it as 'very cost effective' and 'designed for small and midsize companies' with a low barrier to entry.
Teams with specific ticket routing needs value iSupport's fully customizable forms, routing methods, business rules, and reporting dashboards that can be tailored without code-level changes.
Support managers appreciate the clear visibility into support requests and organizational workflow that comes from a purpose-built ITSM tool rather than a repurposed CRM or project tracker.
Teams migrating from spreadsheets or legacy systems pick iSupport because it generates unique 10-digit alphanumeric ticket IDs that make auditing and cross-referencing straightforward during transition periods.
Organizations wanting deployment flexibility choose iSupport because it offers both on-premise and cloud-hosted deployments under the same product with identical feature sets.
Administrators report the lack of advanced features and flexibility compared to modern ticketing systems, particularly around automation of routine administrative tasks that require manual intervention.
Users note the interface feels dated compared to newer platforms like Jira Service Management and Freshservice, with some describing a steep learning curve for the more complex features.
Teams that grow beyond basic ITSM find iSupport missing enterprise capabilities like sophisticated AI copilots, autonomous ticket resolution, and the broader integrations available in ServiceNow or BMC Helix.
Support managers cite difficulty scaling beyond basic incident and ticket management when they need ITIL-aligned problem and change workflows across larger IT organizations.
Reasons to switch
Why people leave iSupport Software
The recurring reasons buyers give for replacing iSupport Software. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where iSupport Software 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
iSupport Software pricing overview
iSupport uses a tiered pricing model based on user count with both subscription and perpetual licensing options. Additional fees apply for modules, customizations, and support services, and cloud-hosted and on-premise deployments have separate pricing structures. Volume discounts and academic pricing are available, with maintenance plans offered for ongoing support.
Incident Management
Tier 1 of 2
Not publicly listed — tiered by user count with subscription or perpetual options
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on iSupport Software's schedule — see our quote-based pricing →
What gets migrated
iSupport Software object support
Object-by-object support for iSupport Software migrations. Per-pair details surface during scoping.
Incidents (Tickets)
Fully supportedIncidents are the core object in iSupport — each receives a unique 10-digit alphanumeric ticket ID at creation. All standard fields (status, priority, category, assignee, requester) are well-documented and migrate 1:1. Custom fields on incidents are preserved as mapping work.
Customers
Fully supportedCustomers are the primary end-user contact records in iSupport. The system supports customer profiles with associated contact details. Standard fields and any mapped custom fields migrate cleanly between platforms.
Companies
Fully supportedCompanies represent organizational accounts in iSupport and can be associated with multiple Customers and Incidents. The company-to-customer linkage is preserved during migration by joining on the company ID field.
Knowledge Entries (KB Articles/FAQs)
Fully supportedKnowledge Entries are searchable FAQ and article records used for self-service and agent lookup. iSupport supports rich categorization and attachment linking. Both title/content and category structure are migrated.
Assets
Mapping requiredAssets track configuration items and hardware/software inventory. Migration requires mapping asset-to-incident relationships since the destination may represent CIs differently. Serial numbers, purchase dates, and assignment history are included in scope.
Custom Fields
Mapping requiredBoth editions support adding custom fields to key record types via the Custom Fields screen. Picklist values and field-level defaults require explicit mapping since naming conventions differ between iSupport and the destination schema.
Surveys
Mapping requiredSurveys in iSupport attach to incidents and capture post-resolution satisfaction data. Survey questions and answer schemas require mapping work as the destination ITSM tool may use a different survey engine or built-in CSAT model.
Change Records (Service Desk Edition)
Mapping requiredChange Records are only available in the Service Desk Edition. They include fields for change type, risk assessment, and approval workflow. These require schema mapping because the ITIL-aligned change model is not universal across destination platforms.
Configuration Items / CMDB (Service Desk Edition)
Mapping requiredThe Configuration Management Database holds CI relationships and dependency maps. This object is gated behind the Service Desk tier. Exporting CI relationships requires understanding the item-to-item linkage model, which varies significantly in destination systems.
Email Rules and Accounts
Mapping requirediSupport email functionality uses rule groups where each rule is evaluated by the Email Processing agent based on its position field. Email routing rules, account mappings, and auto-reply configurations require case-by-case analysis since they are deployment-specific.
| Object | Support | Notes |
|---|---|---|
| Incidents (Tickets) | Fully supported | Incidents are the core object in iSupport — each receives a unique 10-digit alphanumeric ticket ID at creation. All standard fields (status, priority, category, assignee, requester) are well-documented and migrate 1:1. Custom fields on incidents are preserved as mapping work. |
| Customers | Fully supported | Customers are the primary end-user contact records in iSupport. The system supports customer profiles with associated contact details. Standard fields and any mapped custom fields migrate cleanly between platforms. |
| Companies | Fully supported | Companies represent organizational accounts in iSupport and can be associated with multiple Customers and Incidents. The company-to-customer linkage is preserved during migration by joining on the company ID field. |
| Knowledge Entries (KB Articles/FAQs) | Fully supported | Knowledge Entries are searchable FAQ and article records used for self-service and agent lookup. iSupport supports rich categorization and attachment linking. Both title/content and category structure are migrated. |
| Assets | Mapping required | Assets track configuration items and hardware/software inventory. Migration requires mapping asset-to-incident relationships since the destination may represent CIs differently. Serial numbers, purchase dates, and assignment history are included in scope. |
| Custom Fields | Mapping required | Both editions support adding custom fields to key record types via the Custom Fields screen. Picklist values and field-level defaults require explicit mapping since naming conventions differ between iSupport and the destination schema. |
| Surveys | Mapping required | Surveys in iSupport attach to incidents and capture post-resolution satisfaction data. Survey questions and answer schemas require mapping work as the destination ITSM tool may use a different survey engine or built-in CSAT model. |
| Change Records (Service Desk Edition) | Mapping required | Change Records are only available in the Service Desk Edition. They include fields for change type, risk assessment, and approval workflow. These require schema mapping because the ITIL-aligned change model is not universal across destination platforms. |
| Configuration Items / CMDB (Service Desk Edition) | Mapping required | The Configuration Management Database holds CI relationships and dependency maps. This object is gated behind the Service Desk tier. Exporting CI relationships requires understanding the item-to-item linkage model, which varies significantly in destination systems. |
| Email Rules and Accounts | Mapping required | iSupport email functionality uses rule groups where each rule is evaluated by the Email Processing agent based on its position field. Email routing rules, account mappings, and auto-reply configurations require case-by-case analysis since they are deployment-specific. |
Gotchas
What to watch for in iSupport Software migrations
Issues we've hit on past iSupport Software migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Email rule export requires deployment-type awareness
Service Desk features absent in Incident Management edition
No public bulk API documented for automated export
Custom field picklist values may not export cleanly
Asset-to-incident linkage requires manual relationship mapping
| Severity | Issue |
|---|---|
| Medium | Email rule export requires deployment-type awareness |
| High | Service Desk features absent in Incident Management edition |
| High | No public bulk API documented for automated export |
| Medium | Custom field picklist values may not export cleanly |
| Low | Asset-to-incident linkage requires manual relationship mapping |
Leaving iSupport Software?
Where iSupport Software customers move next
7 destinations iSupport Software can migrate to.
How a iSupport Software migration works
Four steps, iSupport Software-specific
Connect
Not publicly documented into iSupport Software. Scopes limited to read-only on the data we move.
Map
We translate iSupport Software-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate iSupport Software quirks before production.
Migrate
Full migration with iSupport Software rate-limit handling. Rollback available throughout.
FAQ
iSupport Software migration FAQ
Answers to the questions buyers ask most during iSupport Software migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your iSupport Software 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 iSupport Software.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your iSupport Software setup and destination — written quote back within a business day.