Migrate your Incident IQ data
K-12 service management platform combining help desk ticketing, asset tracking, facilities, and HR workflows for school districts. Enrollment-based pricing with no seat or asset caps.
In its favor
Why people choose Incident IQ
The signal that keeps Incident IQ on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Purpose-built for K-12 means IT teams can track Chromebooks by student, search by asset tag or serial, and submit tickets on behalf of students directly from the teacher's attendance view.
Student enrollment-based pricing with no seat or asset limits removes unpredictable per-user costs as districts grow or contract year over year.
AI-powered ticket routing in IT Ticketing helps reduce resolution time, and the Ticket Wizard guides staff through submitting information-rich requests in under a minute.
Pre-built integrations with ClassLink, RevTrak, Vanco, and smart locker hardware from LocknCharge reduce manual data entry and synchronization overhead for districts already using these tools.
iiQ Academy provides structured video training and certification paths that help new IT staff ramp up without requiring extensive internal documentation.
Annual subscription price increases of 4-8% per year create budget unpredictability for districts operating under fixed technology spending allocations.
Some administrative restrictions limit customization—certain system-defined model categories cannot be modified or deleted, which frustrates districts with unique organizational structures.
K-12-specific design omits general-purpose ITSM capabilities available in broader platforms, which becomes limiting when districts try to expand use cases beyond initial scope.
Asset timeline history retention policies are not clearly documented, making compliance exports and long-term audit trails difficult to plan around.
Reasons to switch
Why people leave Incident IQ
The recurring reasons buyers give for replacing Incident IQ. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Incident IQ 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
Incident IQ pricing overview
Incident IQ uses district-level, enrollment-based pricing rather than per-seat or per-asset billing. Each module (IT Ticketing, Asset Management, Facilities, Events, HR) is priced as a separate tier, and full platform access requires a custom quote. Annual price increases of 4-8% are standard practice according to user reports.
IT Ticketing
Tier 1 of 6
$120/user/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Incident IQ's schedule — see our quote-based pricing →
What gets migrated
Incident IQ object support
Object-by-object support for Incident IQ migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets (Requests) are the core workflow object in Incident IQ. We map all standard ticket fields—status, priority, assignee, campus, category, and timestamps—1:1. Custom fields on tickets are preserved via mapping. Ticket attachments are migrated as linked files.
Assets
Fully supportedAssets represent every tracked device or equipment. We preserve the full asset record including serial number, asset tag, model, location, assigned user, and custom fields. Asset-to-user associations are preserved as relational links rather than embedded values.
Locations (Campuses)
Fully supportedIncident IQ organizes assets and tickets by campus location. We preserve the full location hierarchy so tickets and assets retain their campus assignments in the destination system.
Users
Fully supportedUsers include staff, students, and agents. We map the user record including name, email, role, and campus assignment. Bulk import of users requires correct role designation to maintain agent vs. requestor behavior in the destination.
Asset Model Categories
Mapping requiredAsset model categories (e.g., Chromebooks, Laptops, Projectors) define the device taxonomy. Some system-defined categories are locked and cannot be modified. We map existing categories and flag locked system categories that cannot be replicated in the destination.
Support Flows
Mapping requiredSupport Flows are automation chains that route tickets, assign agents, and trigger actions. We extract the flow logic and map it to equivalent automation rules in the destination, noting where trigger conditions have no direct equivalent.
Knowledge Base Articles
Mapping requiredKB articles store resolution guidance attached to tickets. We migrate article content, categories, and associations. We flag articles with embedded ticket links that will need redirect updates after migration.
Custom Ticket Fields
Mapping requiredDistricts can add custom fields to tickets. We map these as custom fields in the destination, applying value mappings where field types differ (e.g., dropdown vs. multi-select). System-locked fields are skipped.
Custom Asset Fields
Mapping requiredCustom fields on assets allow districts to track K-12-specific attributes beyond the standard schema. We map these fields and their values, applying type conversions where destination field types differ.
Facilities Work Orders
Fully supportedFacilities Management introduces Work Orders as a distinct object alongside tickets. We migrate Work Order records including status, priority, assignee, location, and description. The association between a work order and the originating ticket is preserved.
Events
Fully supportediiQ Events manages room reservations and event preparation workflows. We migrate event records including date, location, requestor, approval status, and associated resources.
HR Requests
Fully supportedHR Service Delivery handles employee-facing requests and workflows. We migrate HR request records, associated forms, and their completion statuses. Form field data is mapped to equivalent destination fields.
Forms
Mapping requiredForms Manager digitizes district-specific data collection workflows. We extract form definitions and submitted responses. Complex form logic, conditional fields, and embedded attachments require custom mapping to the destination's form builder.
Attachments
Mapping requiredTicket attachments, KB article files, and form uploads are migrated as file assets. We preserve file names and attach them to the correct parent record. Files over 25MB may require chunked transfer handling.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets (Requests) are the core workflow object in Incident IQ. We map all standard ticket fields—status, priority, assignee, campus, category, and timestamps—1:1. Custom fields on tickets are preserved via mapping. Ticket attachments are migrated as linked files. |
| Assets | Fully supported | Assets represent every tracked device or equipment. We preserve the full asset record including serial number, asset tag, model, location, assigned user, and custom fields. Asset-to-user associations are preserved as relational links rather than embedded values. |
| Locations (Campuses) | Fully supported | Incident IQ organizes assets and tickets by campus location. We preserve the full location hierarchy so tickets and assets retain their campus assignments in the destination system. |
| Users | Fully supported | Users include staff, students, and agents. We map the user record including name, email, role, and campus assignment. Bulk import of users requires correct role designation to maintain agent vs. requestor behavior in the destination. |
| Asset Model Categories | Mapping required | Asset model categories (e.g., Chromebooks, Laptops, Projectors) define the device taxonomy. Some system-defined categories are locked and cannot be modified. We map existing categories and flag locked system categories that cannot be replicated in the destination. |
| Support Flows | Mapping required | Support Flows are automation chains that route tickets, assign agents, and trigger actions. We extract the flow logic and map it to equivalent automation rules in the destination, noting where trigger conditions have no direct equivalent. |
| Knowledge Base Articles | Mapping required | KB articles store resolution guidance attached to tickets. We migrate article content, categories, and associations. We flag articles with embedded ticket links that will need redirect updates after migration. |
| Custom Ticket Fields | Mapping required | Districts can add custom fields to tickets. We map these as custom fields in the destination, applying value mappings where field types differ (e.g., dropdown vs. multi-select). System-locked fields are skipped. |
| Custom Asset Fields | Mapping required | Custom fields on assets allow districts to track K-12-specific attributes beyond the standard schema. We map these fields and their values, applying type conversions where destination field types differ. |
| Facilities Work Orders | Fully supported | Facilities Management introduces Work Orders as a distinct object alongside tickets. We migrate Work Order records including status, priority, assignee, location, and description. The association between a work order and the originating ticket is preserved. |
| Events | Fully supported | iiQ Events manages room reservations and event preparation workflows. We migrate event records including date, location, requestor, approval status, and associated resources. |
| HR Requests | Fully supported | HR Service Delivery handles employee-facing requests and workflows. We migrate HR request records, associated forms, and their completion statuses. Form field data is mapped to equivalent destination fields. |
| Forms | Mapping required | Forms Manager digitizes district-specific data collection workflows. We extract form definitions and submitted responses. Complex form logic, conditional fields, and embedded attachments require custom mapping to the destination's form builder. |
| Attachments | Mapping required | Ticket attachments, KB article files, and form uploads are migrated as file assets. We preserve file names and attach them to the correct parent record. Files over 25MB may require chunked transfer handling. |
Gotchas
What to watch for in Incident IQ migrations
Issues we've hit on past Incident IQ migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Enrollment-based pricing requires accurate student count
Locked system model categories cannot be migrated
Asset timeline history retention duration is undocumented
Bulk API is not publicly documented
Annual subscription price increases are non-negotiable for most districts
| Severity | Issue |
|---|---|
| High | Enrollment-based pricing requires accurate student count |
| Medium | Locked system model categories cannot be migrated |
| Medium | Asset timeline history retention duration is undocumented |
| Medium | Bulk API is not publicly documented |
| Low | Annual subscription price increases are non-negotiable for most districts |
Leaving Incident IQ?
Where Incident IQ customers move next
7 destinations Incident IQ can migrate to.
How a Incident IQ migration works
Four steps, Incident IQ-specific
Connect
API key (specific mechanism not publicly documented) into Incident IQ. Scopes limited to read-only on the data we move.
Map
We translate Incident IQ-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Incident IQ quirks before production.
Migrate
Full migration with Incident IQ rate-limit handling. Rollback available throughout.
FAQ
Incident IQ migration FAQ
Answers to the questions buyers ask most during Incident IQ migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Incident IQ 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 Incident IQ.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Incident IQ setup and destination — written quote back within a business day.