Migrate your SupportSystem data
Lightweight help desk ticketing software built by the osTicket creators, targeting small to mid-market teams who need a simple, affordable ticket router with SLA tracking and CSV-based export.
In its favor
Why people choose SupportSystem
The signal that keeps SupportSystem on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lowest entry price of any structured help desk — $12/agent/month on Basic with a 30-day free trial lets small teams validate fit before committing.
Simple ticket routing based on Help Topics, Departments, and email routing rules requires minimal configuration compared to enterprise platforms.
Built-in SLA Management lets support managers set monitored response deadlines without purchasing a separate SLA add-on.
Self-Service Portal and Knowledge Base are included at every tier, providing basic customer-facing documentation infrastructure.
CSV-based export of ticket metadata and dashboard data lets technical teams extract data without needing API access.
No public REST API — teams requiring programmatic access for automation or integrations hit a hard ceiling and must migrate to platforms with documented APIs.
Limited scalability for enterprise workflows — teams outgrow the basic feature set as support volume grows beyond simple ticket routing.
Attachment storage limits tied to tier (2 MB Basic, 8 MB Standard, not specified on Premium) cause friction for teams handling large file uploads.
Integration ecosystem is not publicly documented, making third-party connectivity uncertain and driving teams to alternatives with clear marketplace apps.
The platform lacks advanced analytics and reporting depth, pushing data-driven support teams toward platforms with richer BI tooling.
Reasons to switch
Why people leave SupportSystem
The recurring reasons buyers give for replacing SupportSystem. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where SupportSystem 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
SupportSystem pricing overview
SupportSystem uses a per-agent monthly subscription model with three tiers ranging from $12 to $24 per agent per month. There are no published minimum seat requirements, onboarding fees, or per-feature add-ons. All tiers include a 30-day free trial for initial evaluation.
Basic
Tier 1 of 3
$12/agent/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on SupportSystem's schedule — see our quote-based pricing →
What gets migrated
SupportSystem object support
Object-by-object support for SupportSystem migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the primary object in SupportSystem. Ticket header information (ID, status, creation date, assigned user) exports via CSV from the Agent Panel or Dashboard. We can migrate Tickets 1:1 using the standard CSV column mapping. Advanced Search filters allow scoping by ticket data, user data, or form information before export.
Agents
Fully supportedAgents are listed in CSV exports as the assigned user on tickets. Agent metadata (name, email, department assignment) is exported as part of ticket header exports. We preserve the Agent-to-department assignment and map it to the destination's agent/user model.
Users (End Users)
Mapping requiredEnd Users create tickets via the Client Portal. User records export as part of ticket header data or can be filtered by User Information in Advanced Search. Where the destination has a separate Contact/End User object, we map User records accordingly and flag any duplicate detection required.
Organizations
Mapping requiredOrganizations are a distinct object referenced on tickets. Organization information can be filtered via Advanced Search under Organization Information. We map Organization records separately from User records and preserve any organization-level custom fields.
Custom Fields
Mapping requiredCustom Fields are configurable per ticket, user, or organization. The Data Extraction Guide confirms agents can customize which metadata fields appear in CSV exports. We map custom field names and values to the destination's equivalent custom field schema, handling type differences (dropdown vs. free text, etc.).
Custom Forms
Mapping requiredCustom Forms collect structured data at ticket creation. Form field data is included in ticket exports when the Export Picker is configured to include form fields. We extract form response data per ticket and map each form field to the destination's equivalent custom field.
Custom Lists
Mapping requiredCustom Lists are reusable data sets added to tickets or specific Help Topics. List values export as part of custom field data when form fields are included in the CSV export. We handle list-to-dropdown field mapping during schema transformation.
Help Topics
Mapping requiredHelp Topics drive ticket routing and can trigger specific Custom Forms. Help Topic assignment appears in ticket metadata. We preserve Help Topic-to-Department routing logic and map it to the destination's queue or category structure.
Departments
Fully supportedDepartments are used for ticket routing and agent assignment. Department data appears in ticket header exports. We preserve department names and map agents to the corresponding department in the destination system.
Email Templates
Mapping requiredStock and custom email templates exist per department but are configuration data rather than transactional records. We export template content as structured text and map them to the destination's email template format. Dynamic variable substitution requires field-level mapping.
Dashboard Data
Fully supportedDashboard exports provide a historical overview of ticket metadata filtered by date, department, help topic, or agent. This CSV serves as a secondary source for cross-checking migration completeness and is included in our standard migration package.
Attachments
Not in this platformAttachment files stored in SupportSystem are not exported via the CSV Data Extraction feature. The export includes ticket metadata and form field values only. We do not migrate attachment binary data via the CSV path. Customers must export attachments separately through the file system if required.
KB Articles
Mapping requiredKnowledge Base articles are part of the self-service portal. We extract article content and metadata from the platform and map them to the destination's KB object, preserving categories and internal links where possible.
Tags
Mapping requiredTags applied to tickets appear in ticket metadata exports. We preserve tag strings and map them to the destination's tagging or labeling system. Tag-to-category mapping may be required if the destination uses a hierarchical taxonomy.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the primary object in SupportSystem. Ticket header information (ID, status, creation date, assigned user) exports via CSV from the Agent Panel or Dashboard. We can migrate Tickets 1:1 using the standard CSV column mapping. Advanced Search filters allow scoping by ticket data, user data, or form information before export. |
| Agents | Fully supported | Agents are listed in CSV exports as the assigned user on tickets. Agent metadata (name, email, department assignment) is exported as part of ticket header exports. We preserve the Agent-to-department assignment and map it to the destination's agent/user model. |
| Users (End Users) | Mapping required | End Users create tickets via the Client Portal. User records export as part of ticket header data or can be filtered by User Information in Advanced Search. Where the destination has a separate Contact/End User object, we map User records accordingly and flag any duplicate detection required. |
| Organizations | Mapping required | Organizations are a distinct object referenced on tickets. Organization information can be filtered via Advanced Search under Organization Information. We map Organization records separately from User records and preserve any organization-level custom fields. |
| Custom Fields | Mapping required | Custom Fields are configurable per ticket, user, or organization. The Data Extraction Guide confirms agents can customize which metadata fields appear in CSV exports. We map custom field names and values to the destination's equivalent custom field schema, handling type differences (dropdown vs. free text, etc.). |
| Custom Forms | Mapping required | Custom Forms collect structured data at ticket creation. Form field data is included in ticket exports when the Export Picker is configured to include form fields. We extract form response data per ticket and map each form field to the destination's equivalent custom field. |
| Custom Lists | Mapping required | Custom Lists are reusable data sets added to tickets or specific Help Topics. List values export as part of custom field data when form fields are included in the CSV export. We handle list-to-dropdown field mapping during schema transformation. |
| Help Topics | Mapping required | Help Topics drive ticket routing and can trigger specific Custom Forms. Help Topic assignment appears in ticket metadata. We preserve Help Topic-to-Department routing logic and map it to the destination's queue or category structure. |
| Departments | Fully supported | Departments are used for ticket routing and agent assignment. Department data appears in ticket header exports. We preserve department names and map agents to the corresponding department in the destination system. |
| Email Templates | Mapping required | Stock and custom email templates exist per department but are configuration data rather than transactional records. We export template content as structured text and map them to the destination's email template format. Dynamic variable substitution requires field-level mapping. |
| Dashboard Data | Fully supported | Dashboard exports provide a historical overview of ticket metadata filtered by date, department, help topic, or agent. This CSV serves as a secondary source for cross-checking migration completeness and is included in our standard migration package. |
| Attachments | Not in this platform | Attachment files stored in SupportSystem are not exported via the CSV Data Extraction feature. The export includes ticket metadata and form field values only. We do not migrate attachment binary data via the CSV path. Customers must export attachments separately through the file system if required. |
| KB Articles | Mapping required | Knowledge Base articles are part of the self-service portal. We extract article content and metadata from the platform and map them to the destination's KB object, preserving categories and internal links where possible. |
| Tags | Mapping required | Tags applied to tickets appear in ticket metadata exports. We preserve tag strings and map them to the destination's tagging or labeling system. Tag-to-category mapping may be required if the destination uses a hierarchical taxonomy. |
Gotchas
What to watch for in SupportSystem migrations
Issues we've hit on past SupportSystem migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public REST API for automated data extraction
Attachment files are excluded from CSV exports
Custom Field export requires Export Picker configuration
Storage limits per tier affect attachment-heavy workflows
No documented API rate limits because no API exists
| Severity | Issue |
|---|---|
| High | No public REST API for automated data extraction |
| High | Attachment files are excluded from CSV exports |
| Medium | Custom Field export requires Export Picker configuration |
| Medium | Storage limits per tier affect attachment-heavy workflows |
| Low | No documented API rate limits because no API exists |
Leaving SupportSystem?
Where SupportSystem customers move next
7 destinations SupportSystem can migrate to.
How a SupportSystem migration works
Four steps, SupportSystem-specific
Connect
Not applicable into SupportSystem. Scopes limited to read-only on the data we move.
Map
We translate SupportSystem-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate SupportSystem quirks before production.
Migrate
Full migration with SupportSystem rate-limit handling. Rollback available throughout.
FAQ
SupportSystem migration FAQ
Answers to the questions buyers ask most during SupportSystem migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your SupportSystem 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 SupportSystem.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your SupportSystem setup and destination — written quote back within a business day.