Migrate your iService data
Multi-channel helpdesk and customer service platform built for teams managing tickets, live chat, and self-service portals.
In its favor
Why people choose iService
The signal that keeps iService on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
iService combines email, live chat, SMS (via Email-to-SMS), web forms, customer portal, and outbound mass mailing under one workflow engine, so support and marketing communications share a single customer record without bolting on a separate tool.
Per-agent pricing is published transparently at $55, $85, and $110/agent/month (annual billing) with no setup fees, cancellation fees, or hidden add-on charges — uncommon in enterprise-grade helpdesk software.
On-premises deployment is offered alongside cloud SaaS, which appeals to regulated industries needing data residency control or Microsoft-stack alignment for Windows Authentication and SSRS-style reporting.
AI-assisted response tools and custom AI prompts are bundled into the Professional tier rather than gated as a separate paid add-on, so teams test AI without renegotiating contracts.
Enterprise tier includes a dedicated success manager, weekly status calls, custom monitoring, and critical support, giving large-volume operations operational hand-holding without separate professional-services contracts.
iService publishes no public developer API or REST endpoint documentation — teams that need to push or pull ticket data programmatically face friction and may migrate to Zendesk, Freshdesk, or Intercom for self-serve API maturity.
Custom web forms, workflow builder, mass mailing, and payment integration are only in the Enterprise tier at $110/agent/month, which can push smaller teams to consolidate on platforms where these are in mid tiers.
Live chat and Knowledge Base are not in the entry Suite tier — teams expecting multi-channel from day one must start on Professional, narrowing the value gap versus Zendesk Suite Team or HubSpot Service Hub starter plans.
Workflow rules are tightly coupled to iService's internal engine and cannot be migrated to another platform later, creating switching cost when teams outgrow the product.
Documentation, marketing presence, and reviewer footprint are thin relative to Zendesk/Freshdesk/Intercom, so teams trying to hire experienced iService admins or find community answers face a smaller talent and resource pool.
Reasons to switch
Why people leave iService
The recurring reasons buyers give for replacing iService. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where iService 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
iService pricing overview
iService publishes three tiers on annual billing: Suite at $55/agent/month for email-centric small business support, Professional at $85/agent/month adding live chat, SMS, Knowledge Base, portals, business intelligence, Zapier, and custom AI prompts, and Enterprise at $110/agent/month adding custom web forms, mass mailing, workflow builder, payment integration, Google Calendar, dedicated success manager, weekly status calls, and critical support. No setup, cancellation, or hidden add-on fees. Free trials are offered without credit-card capture, but no permanent free tier exists. On-premises deployment is offered alongside SaaS.
Suite
Tier 1 of 3
$55/agent/month (annual billing)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on iService's schedule — see our quote-based pricing →
What gets migrated
iService object support
Object-by-object support for iService migrations. Per-pair details surface during scoping.
Tickets
Mapping requiredTickets are the core object in iService. Every ticket has a status, priority, owner, and associated customer. Custom ticket fields add complexity during migration because field names and data types must be mapped to the destination schema. We export all standard ticket fields and flag any custom fields for explicit mapping before import.
Customers
Fully supportedCustomer records are the end-user side of the platform. iService stores contact-level data including name, email, phone, and custom properties. We migrate Customers as Contacts in most destination systems with a standard field mapping.
Companies
Fully supportedCompany records represent organizations associated with multiple customer accounts. We map these to Companies or Accounts in the destination CRM. Company-level custom properties follow the same mapping logic as customer custom fields.
Conversations
Mapping requiredEach Ticket contains a threaded Conversation history. When migrating to another helpdesk, we map conversation messages to the destination's comment or reply structure. When migrating to a CRM, we synthesize conversation history into the customer record timeline.
Live Chat Sessions
Mapping requirediService supports real-time chat. Chat transcripts are stored as conversation records tied to a customer. We flag chat transcripts for explicit handling since not all destination platforms preserve full chat history in the same structure.
Knowledge Base Articles
Mapping requiredKB Articles in iService contain content, categories, and attachments. We export articles as HTML or markdown and map KB Categories to the destination's category hierarchy. Attachments within articles are migrated as file references.
Custom Ticket Fields
Mapping requirediService allows custom fields on tickets beyond the standard set. These fields vary by tenant configuration. We treat each custom field as requiring explicit mapping during scoping and flag any dependent workflows that reference them.
Workflows and Automations
Not in this platformWorkflow rules in iService define ticket routing, status changes, and notifications. We do not migrate Workflows directly because they are tightly coupled to the platform's internal engine and cannot be reliably reconstructed in a destination system.
Attachments
Mapping requiredFile attachments on tickets and KB articles are migrated as binary blobs referenced by the parent record. We preserve attachment filenames and link them to the correct ticket or article in the destination. Large attachment volumes may extend migration timelines.
Tags
Mapping requiredTags are used to label tickets and KB articles. We migrate tags as label or tag records in the destination and remap tag associations to the parent object. Tag naming conventions between source and destination are harmonized during the mapping phase.
Users and Agents
Mapping requiredAgent accounts in iService include email, name, role, and team assignment. We map agents to users in the destination platform. Role structures differ between systems, so we default to a standard agent role and flag for manual review after migration.
Customer Portal Settings
Not in this platformPortal configuration data including branding, domain settings, and portal visibility rules are platform-specific and cannot be meaningfully migrated to a different system.
| Object | Support | Notes |
|---|---|---|
| Tickets | Mapping required | Tickets are the core object in iService. Every ticket has a status, priority, owner, and associated customer. Custom ticket fields add complexity during migration because field names and data types must be mapped to the destination schema. We export all standard ticket fields and flag any custom fields for explicit mapping before import. |
| Customers | Fully supported | Customer records are the end-user side of the platform. iService stores contact-level data including name, email, phone, and custom properties. We migrate Customers as Contacts in most destination systems with a standard field mapping. |
| Companies | Fully supported | Company records represent organizations associated with multiple customer accounts. We map these to Companies or Accounts in the destination CRM. Company-level custom properties follow the same mapping logic as customer custom fields. |
| Conversations | Mapping required | Each Ticket contains a threaded Conversation history. When migrating to another helpdesk, we map conversation messages to the destination's comment or reply structure. When migrating to a CRM, we synthesize conversation history into the customer record timeline. |
| Live Chat Sessions | Mapping required | iService supports real-time chat. Chat transcripts are stored as conversation records tied to a customer. We flag chat transcripts for explicit handling since not all destination platforms preserve full chat history in the same structure. |
| Knowledge Base Articles | Mapping required | KB Articles in iService contain content, categories, and attachments. We export articles as HTML or markdown and map KB Categories to the destination's category hierarchy. Attachments within articles are migrated as file references. |
| Custom Ticket Fields | Mapping required | iService allows custom fields on tickets beyond the standard set. These fields vary by tenant configuration. We treat each custom field as requiring explicit mapping during scoping and flag any dependent workflows that reference them. |
| Workflows and Automations | Not in this platform | Workflow rules in iService define ticket routing, status changes, and notifications. We do not migrate Workflows directly because they are tightly coupled to the platform's internal engine and cannot be reliably reconstructed in a destination system. |
| Attachments | Mapping required | File attachments on tickets and KB articles are migrated as binary blobs referenced by the parent record. We preserve attachment filenames and link them to the correct ticket or article in the destination. Large attachment volumes may extend migration timelines. |
| Tags | Mapping required | Tags are used to label tickets and KB articles. We migrate tags as label or tag records in the destination and remap tag associations to the parent object. Tag naming conventions between source and destination are harmonized during the mapping phase. |
| Users and Agents | Mapping required | Agent accounts in iService include email, name, role, and team assignment. We map agents to users in the destination platform. Role structures differ between systems, so we default to a standard agent role and flag for manual review after migration. |
| Customer Portal Settings | Not in this platform | Portal configuration data including branding, domain settings, and portal visibility rules are platform-specific and cannot be meaningfully migrated to a different system. |
Gotchas
What to watch for in iService migrations
Issues we've hit on past iService migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API reference complicates automated export
Workflows cannot be migrated between platforms
Live chat transcript structure varies by configuration
| Severity | Issue |
|---|---|
| High | No public API reference complicates automated export |
| Medium | Workflows cannot be migrated between platforms |
| Low | Live chat transcript structure varies by configuration |
Leaving iService?
Where iService customers move next
7 destinations iService can migrate to.
How a iService migration works
Four steps, iService-specific
Connect
Not publicly documented into iService. Scopes limited to read-only on the data we move.
Map
We translate iService-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate iService quirks before production.
Migrate
Full migration with iService rate-limit handling. Rollback available throughout.
FAQ
iService migration FAQ
Answers to the questions buyers ask most during iService migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your iService 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 iService.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your iService setup and destination — written quote back within a business day.