Migrate your Issuetrak data
Issue-tracking platform with on-premises and cloud deployment options, priced per agent with unlimited free end-users. Strong for IT help desks but not ITIL-aligned.
In its favor
Why people choose Issuetrak
The signal that keeps Issuetrak on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Unlimited free end-users with up to 50 permissions each means Issuetrak scales across departments without per-submitter licensing costs
Quick Picks ticket templates and configurable User Defined Fields let support teams pre-fill issue submissions for consistent intake
Cloud or on-premises deployment options appeal to government, finance, and healthcare organizations with data-residency requirements
Tier-free straightforward pricing with a dedicated account manager provides predictability for IT budget owners
SLA and metrics configuration on a per-agent basis gives help desk managers measurable performance tracking
ITIL process support is weak — incidents cannot be linked to problem tickets or known error records, forcing teams to manage these relationships manually
Problem management workflows do not fit the platform's data model well, making it unsuitable for formal ITSM teams
Field visibility rules are inflexible — mandatory fields cannot be hidden from the issue view, creating unnecessary clutter
On-premises installations require manual SQL Server and IIS administration, increasing total cost of ownership over time
Customization requires administrator-level access and careful planning; casual users report the screens need more polish
Reasons to switch
Why people leave Issuetrak
The recurring reasons buyers give for replacing Issuetrak. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Issuetrak 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
Issuetrak pricing overview
Issuetrak charges per named Agent (paid support staff) with unlimited free end-users who can submit tickets. Starting price is approximately $478/month, with Enterprise tiers offering custom pricing that includes deployment flexibility, advanced automation, and a dedicated account manager.
Starting
Tier 1 of 2
$478/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Issuetrak's schedule — see our quote-based pricing →
What gets migrated
Issuetrak object support
Object-by-object support for Issuetrak migrations. Per-pair details surface during scoping.
Issues
Fully supportedIssues are the core ticket object in Issuetrak. Standard fields include Subject, Description, Issue Type, Subtype, Assigned To, Priority, Status, Substatus, and timestamps. We export all standard fields and handle the full lifecycle including Closed date and resolution details.
Issue Classes
Fully supportedIssue Classes provide categorical structure for tickets and drive dashboard filtering. We preserve the Class assignment on each Issue and map it to the destination system's category or tag model.
Issue Statuses and Substatuses
Fully supportedIssuetrak uses a two-level status hierarchy: Status (Open/Closed) and Substatus (e.g., Pending, In Progress, Resolved). We export both levels and create a combined Status_Substatus field for destination systems without a substatus concept.
User Defined Fields (UDFs)
Mapping requiredUDFs are Issuetrak's primary customization mechanism and support text, number, date, list (single and multi-select), and task-associated types. We export field definitions alongside values but list-type UDFs require value-mapping when the destination system does not share the same picklist options.
Task Groups
Mapping requiredTask Groups are collections of predefined tasks associated with UDF list selections via the Task-Associated UDF feature. We export the Task Group linkage and recreate tasks on the destination side, noting that task automation triggers do not transfer.
Solutions
Mapping requiredSolutions are text templates used to close or respond to issues. We export them as a separate artifact and map them to the destination system's knowledge base or canned response feature, preserving categorization.
Knowledge Base Articles
Fully supportedIssuetrak supports a Knowledge Base with embedded images and rich text. We export articles with their full HTML content, attachments, and category assignments. The rich-text format is preserved during transfer.
Global Issues
Mapping requiredGlobal Issues link multiple related Issues together for collective management. We export the linkage table and the parent-child relationships so the grouping is visible in the destination system, though not all platforms support this concept natively.
Scheduled Issues
Not in this platformScheduled Issues are auto-submitted on a recurring timeline with pre-defined fields and attachments. The scheduling engine does not export; we document the recurrence pattern and advise the customer to re-create schedules post-migration.
Auto-Assignment Rules
Mapping requiredAuto-Assignment Rules route issues to agents or groups based on criteria. We export the rule definitions but note that the routing logic requires re-implementation in the destination system, as rule engines vary significantly between platforms.
Survey Responses
Mapping requiredSurveys can be exported as CSV via the reporting interface with AND-logic filtering applied. We pull the raw response data and map questions to the destination system's feedback object. Filter configurations are not transferable.
Attachments
Fully supportedAttachments on Issues and Knowledge Base articles are stored and exported as binary files. We preserve filenames and associate them with the correct parent record in the destination system.
Audit Records
Mapping requiredIssue Auditing captures field-level change history. We export the audit trail as a supplementary dataset. Admin Auditing of configuration changes is exported separately and is useful for compliance review in the new system.
| Object | Support | Notes |
|---|---|---|
| Issues | Fully supported | Issues are the core ticket object in Issuetrak. Standard fields include Subject, Description, Issue Type, Subtype, Assigned To, Priority, Status, Substatus, and timestamps. We export all standard fields and handle the full lifecycle including Closed date and resolution details. |
| Issue Classes | Fully supported | Issue Classes provide categorical structure for tickets and drive dashboard filtering. We preserve the Class assignment on each Issue and map it to the destination system's category or tag model. |
| Issue Statuses and Substatuses | Fully supported | Issuetrak uses a two-level status hierarchy: Status (Open/Closed) and Substatus (e.g., Pending, In Progress, Resolved). We export both levels and create a combined Status_Substatus field for destination systems without a substatus concept. |
| User Defined Fields (UDFs) | Mapping required | UDFs are Issuetrak's primary customization mechanism and support text, number, date, list (single and multi-select), and task-associated types. We export field definitions alongside values but list-type UDFs require value-mapping when the destination system does not share the same picklist options. |
| Task Groups | Mapping required | Task Groups are collections of predefined tasks associated with UDF list selections via the Task-Associated UDF feature. We export the Task Group linkage and recreate tasks on the destination side, noting that task automation triggers do not transfer. |
| Solutions | Mapping required | Solutions are text templates used to close or respond to issues. We export them as a separate artifact and map them to the destination system's knowledge base or canned response feature, preserving categorization. |
| Knowledge Base Articles | Fully supported | Issuetrak supports a Knowledge Base with embedded images and rich text. We export articles with their full HTML content, attachments, and category assignments. The rich-text format is preserved during transfer. |
| Global Issues | Mapping required | Global Issues link multiple related Issues together for collective management. We export the linkage table and the parent-child relationships so the grouping is visible in the destination system, though not all platforms support this concept natively. |
| Scheduled Issues | Not in this platform | Scheduled Issues are auto-submitted on a recurring timeline with pre-defined fields and attachments. The scheduling engine does not export; we document the recurrence pattern and advise the customer to re-create schedules post-migration. |
| Auto-Assignment Rules | Mapping required | Auto-Assignment Rules route issues to agents or groups based on criteria. We export the rule definitions but note that the routing logic requires re-implementation in the destination system, as rule engines vary significantly between platforms. |
| Survey Responses | Mapping required | Surveys can be exported as CSV via the reporting interface with AND-logic filtering applied. We pull the raw response data and map questions to the destination system's feedback object. Filter configurations are not transferable. |
| Attachments | Fully supported | Attachments on Issues and Knowledge Base articles are stored and exported as binary files. We preserve filenames and associate them with the correct parent record in the destination system. |
| Audit Records | Mapping required | Issue Auditing captures field-level change history. We export the audit trail as a supplementary dataset. Admin Auditing of configuration changes is exported separately and is useful for compliance review in the new system. |
Gotchas
What to watch for in Issuetrak migrations
Issues we've hit on past Issuetrak migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
On-premises vs cloud extraction requires different methods
User Defined Field types require schema discovery before mapping
Survey export applies active filters by default
Task-Associated UDF triggers do not transfer
API authorization tied to Agent account permissions
| Severity | Issue |
|---|---|
| High | On-premises vs cloud extraction requires different methods |
| Medium | User Defined Field types require schema discovery before mapping |
| Medium | Survey export applies active filters by default |
| Low | Task-Associated UDF triggers do not transfer |
| Medium | API authorization tied to Agent account permissions |
Leaving Issuetrak?
Where Issuetrak customers move next
7 destinations Issuetrak can migrate to.
How a Issuetrak migration works
Four steps, Issuetrak-specific
Connect
API token (HMAC-based, issued per Agent account) into Issuetrak. Scopes limited to read-only on the data we move.
Map
We translate Issuetrak-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Issuetrak quirks before production.
Migrate
Full migration with Issuetrak rate-limit handling. Rollback available throughout.
FAQ
Issuetrak migration FAQ
Answers to the questions buyers ask most during Issuetrak migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Issuetrak 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 Issuetrak.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Issuetrak setup and destination — written quote back within a business day.