Migrate your Tikit.Info data
Microsoft Teams-native IT ticketing and helpdesk system built by Cireson, extending M365 E3/E5 licenses with ITSM capabilities directly inside Teams.
In its favor
Why people choose Tikit.Info
The signal that keeps Tikit.Info on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Teams-first ticket creation lets users convert any Teams chat message into a ticket without leaving the application, removing friction for end users who already live in Microsoft 365.
Customer support receives consistent praise on G2 for responsiveness and deep familiarity with M365 integrations, particularly around Entra and Intune.
The per-agent license model at $26/month is straightforward compared to per-contact or per-seat models that surprise customers with unexpected billing after migration.
Organizations already invested in M365 E3 or E5 can extend those licenses with ITSM capabilities rather than purchasing a separate ITSM platform.
Flexible customization allows multi-department configurations with separate workflows and pipelines, appealing to enterprises with complex organizational structures.
Some users report missing features relative to mature ITSM platforms, with the product roadmap not yet covering all enterprise ITIL use cases.
The deep Microsoft dependency means organizations outside the Microsoft ecosystem face integration challenges when Tikit is the chosen ticketing system.
Smaller teams may find the per-agent pricing model expensive as headcount grows, prompting migration to platforms with per-request or free tiers.
Reasons to switch
Why people leave Tikit.Info
The recurring reasons buyers give for replacing Tikit.Info. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Tikit.Info 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
Tikit.Info pricing overview
Tikit uses a per-agent subscription model starting at $26 per agent per month, with billing managed through Stripe. The license count is determined by users who create, update, reassign, or otherwise manage tickets; read-only users do not require an agent license. Annual billing is required for the Professional and Enterprise tiers.
Starter
Tier 1 of 3
$26/agent/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Tikit.Info's schedule — see our quote-based pricing →
What gets migrated
Tikit.Info object support
Object-by-object support for Tikit.Info migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the primary object in Tikit. We migrate ticket title, description, status, priority, category, subcategory, assignee, requester, created/updated/resolved dates, and internal notes. Custom ticket fields are mapped individually.
Agents
Fully supportedAgent records include name, email, role, team assignment, and license status. We map agent identities to the destination system's user object and flag which records represent active versus inactive agents for license reconciliation.
Requesters
Fully supportedRequesters are end users who submit tickets. We migrate their display name, email address, department, and organization membership. Entra-sourced identity fields are preserved separately from locally-stored profile data.
Teams
Mapping requiredTeams in Tikit map to Microsoft 365 Groups in Entra. Where the destination does not mirror this M365 dependency, we create standalone team records and reassign agent memberships during migration.
Departments
Mapping requiredDepartments define organizational hierarchy for routing and reporting. Multi-department configurations in Tikit require field-level mapping to match the destination's org structure, which may use different terminology such as Business Units or Cost Centers.
Knowledge Articles
Mapping requiredKB articles include title, body content, category, publish status, view count, and related ticket associations. We preserve article-to-ticket relationships by mapping article IDs to destination ticket IDs and flag any articles that reference tickets not included in the migration scope.
Comments
Fully supportedTicket comments include the comment body, author, timestamp, and is-public flag. We migrate all comments preserving the chronological order and author attribution within each ticket.
Attachments
Mapping requiredFile attachments on tickets are downloaded from Azure blob storage and re-uploaded to the destination system. We flag attachments exceeding size limits in the target platform and handle filename encoding issues.
Custom Ticket Fields
Mapping requiredCustom fields vary by Tikit configuration and may include dropdowns, text fields, dates, or user references. We map each custom field by data type and flag fields with picklist values that require explicit value translation between systems.
SLA Policies
Mapping requiredSLA definitions include response time, resolution time, and business hours configuration. We map SLA policies to equivalent constructs in the destination, noting where SLA assignment rules differ.
Configuration Items
Mapping requiredCireson Configuration Items represent assets and related services. We map CI relationships and attributes, though mapping to the destination's asset or CI object requires custom field-level alignment.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the primary object in Tikit. We migrate ticket title, description, status, priority, category, subcategory, assignee, requester, created/updated/resolved dates, and internal notes. Custom ticket fields are mapped individually. |
| Agents | Fully supported | Agent records include name, email, role, team assignment, and license status. We map agent identities to the destination system's user object and flag which records represent active versus inactive agents for license reconciliation. |
| Requesters | Fully supported | Requesters are end users who submit tickets. We migrate their display name, email address, department, and organization membership. Entra-sourced identity fields are preserved separately from locally-stored profile data. |
| Teams | Mapping required | Teams in Tikit map to Microsoft 365 Groups in Entra. Where the destination does not mirror this M365 dependency, we create standalone team records and reassign agent memberships during migration. |
| Departments | Mapping required | Departments define organizational hierarchy for routing and reporting. Multi-department configurations in Tikit require field-level mapping to match the destination's org structure, which may use different terminology such as Business Units or Cost Centers. |
| Knowledge Articles | Mapping required | KB articles include title, body content, category, publish status, view count, and related ticket associations. We preserve article-to-ticket relationships by mapping article IDs to destination ticket IDs and flag any articles that reference tickets not included in the migration scope. |
| Comments | Fully supported | Ticket comments include the comment body, author, timestamp, and is-public flag. We migrate all comments preserving the chronological order and author attribution within each ticket. |
| Attachments | Mapping required | File attachments on tickets are downloaded from Azure blob storage and re-uploaded to the destination system. We flag attachments exceeding size limits in the target platform and handle filename encoding issues. |
| Custom Ticket Fields | Mapping required | Custom fields vary by Tikit configuration and may include dropdowns, text fields, dates, or user references. We map each custom field by data type and flag fields with picklist values that require explicit value translation between systems. |
| SLA Policies | Mapping required | SLA definitions include response time, resolution time, and business hours configuration. We map SLA policies to equivalent constructs in the destination, noting where SLA assignment rules differ. |
| Configuration Items | Mapping required | Cireson Configuration Items represent assets and related services. We map CI relationships and attributes, though mapping to the destination's asset or CI object requires custom field-level alignment. |
Gotchas
What to watch for in Tikit.Info migrations
Issues we've hit on past Tikit.Info migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Agent license billing model affects migration scope
No public REST API for bulk export
Teams dependency complicates user identity mapping
| Severity | Issue |
|---|---|
| High | Agent license billing model affects migration scope |
| High | No public REST API for bulk export |
| Medium | Teams dependency complicates user identity mapping |
Leaving Tikit.Info?
Where Tikit.Info customers move next
7 destinations Tikit.Info can migrate to.
How a Tikit.Info migration works
Four steps, Tikit.Info-specific
Connect
Not publicly documented into Tikit.Info. Scopes limited to read-only on the data we move.
Map
We translate Tikit.Info-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Tikit.Info quirks before production.
Migrate
Full migration with Tikit.Info rate-limit handling. Rollback available throughout.
FAQ
Tikit.Info migration FAQ
Answers to the questions buyers ask most during Tikit.Info migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Tikit.Info 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 Tikit.Info.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Tikit.Info setup and destination — written quote back within a business day.