Migrate your Tikit data
AI-powered IT ticketing system for Microsoft Teams, built by Cireson as a modern ITSM layer on top of M365 E3/E5 licenses.
In its favor
Why people choose Tikit
The signal that keeps Tikit on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Tikit extends M365 E3/E5 licenses with ITSM capabilities, eliminating the need for a separate ITSM tool and reducing per-seat costs for Teams-native organizations.
The Virtual Agent provides AI-powered ticket deflection and self-service resolution, reducing inbound ticket volume without requiring third-party chatbot integration.
ITIL-aligned workflows and SLA tracking are available out of the box, giving organizations a structured ITSM foundation without heavy customization.
Multi-department support brings separate IT and non-IT support teams into a single platform with role-based privacy and portal separation.
The Cireson free setup program promises configuration completion in under 90 minutes, reducing time-to-value compared to traditional ITSM implementations.
Some organizations outgrow the Teams-centric UX and need the project management flexibility or advanced reporting that standalone ITSM platforms provide.
Missing features on the product roadmap create friction for teams with complex approval workflows or specialized asset management requirements.
Steep learning curve for non-Microsoft-native staff who are unfamiliar with Teams-based workflows and Power Automate dependency chains.
Teams-only ticket creation creates a usability gap for organizations where end users prefer email or a dedicated web portal over in-app submission.
Reasons to switch
Why people leave Tikit
The recurring reasons buyers give for replacing Tikit. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Tikit 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 pricing overview
Tikit publishes three annual plan tiers (Starter, ITSM Pro, and Enterprise) but does not display public pricing on its website. A 14-day fully functional trial of the ITSM Pro plan is available with no credit card required. The free Cireson setup program covers initial configuration regardless of plan tier, with setup promised in under 90 minutes.
ITSM Starter
Tier 1 of 3
Not publicly listed
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Tikit's schedule — see our quote-based pricing →
What gets migrated
Tikit object support
Object-by-object support for Tikit migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the core object in Tikit. We migrate ticket subject, description, status, priority, category, requester, assigned agent, and full conversation history. Custom ticket fields are migrated as mapping-type fields requiring value translation at the destination.
Agents
Fully supportedAgents are licensed seats in Tikit. We export agent profiles, group assignments, and skill mappings. Note that destination ITSM platforms may have different seat licensing models, so agent count scoping is required before migration.
End Users
Mapping requiredEnd Users are unlicensable and represent ticket submitters. We migrate their display names and email addresses, but Teams presence data and Entra ID-linked profile fields require field-level mapping to the destination's user object.
Knowledge Base Articles
Fully supportedKB Articles are structured around title, body content, category, and publish status. We migrate articles and their category assignments. Links to attached files are preserved as URL references where the destination supports article attachments.
Departments
Mapping requiredMulti-department configuration controls ticket routing, portal visibility, and SLA assignments. We export department structures and their associated queues, then map them to the destination's organizational or team objects, which may use different naming conventions.
KB Categories
Fully supportedArticle categorization structures are migrated 1:1. Tikit's category hierarchy maps to most destination knowledge base category trees without transformation unless the destination enforces a flat structure.
Attachments
Mapping requiredTickets and KB Articles can have file attachments. We migrate attachments stored within Tikit's managed storage. Attachments linked via external URLs are preserved as references. Total attachment volume and file size limits must be verified against the destination platform's storage constraints.
SLA Policies
Mapping requiredSLA definitions tied to ticket priority and department are migrated as configuration data. The destination platform may use different SLA metric naming (First Response vs. Initial Response, Resolution vs. Closure), requiring policy remapping during migration.
Automation Workflows
Mapping requiredTikit leverages Microsoft Power Automate for workflow automation. We export workflow logic as documented configuration, but Power Automate flows are platform-bound and must be rebuilt in the destination ITSM or workflow engine. We provide a workflow audit document to guide the rebuild.
Virtual Agent Configuration
Mapping requiredThe AI Virtual Agent handles initial ticket triage and self-service resolution. Its training data, intent mappings, and fallback configurations are exported as a configuration package. The destination AI agent (if any) requires re-training on the imported ticket corpus.
Asset Records
Mapping requiredAsset management in Tikit includes device records linked to Intune and Entra ID. We export asset name, type, assigned user, and relationship data. Deep integration with Intune device properties does not export as standalone data and requires re-association in the destination CMDB.
Tags
Mapping requiredTickets and articles can be tagged for categorization. We export tag names and associations. Destination platforms with flat label systems will receive a comma-separated tag string; platforms with hierarchical tagging receive a structure-compatible mapping.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the core object in Tikit. We migrate ticket subject, description, status, priority, category, requester, assigned agent, and full conversation history. Custom ticket fields are migrated as mapping-type fields requiring value translation at the destination. |
| Agents | Fully supported | Agents are licensed seats in Tikit. We export agent profiles, group assignments, and skill mappings. Note that destination ITSM platforms may have different seat licensing models, so agent count scoping is required before migration. |
| End Users | Mapping required | End Users are unlicensable and represent ticket submitters. We migrate their display names and email addresses, but Teams presence data and Entra ID-linked profile fields require field-level mapping to the destination's user object. |
| Knowledge Base Articles | Fully supported | KB Articles are structured around title, body content, category, and publish status. We migrate articles and their category assignments. Links to attached files are preserved as URL references where the destination supports article attachments. |
| Departments | Mapping required | Multi-department configuration controls ticket routing, portal visibility, and SLA assignments. We export department structures and their associated queues, then map them to the destination's organizational or team objects, which may use different naming conventions. |
| KB Categories | Fully supported | Article categorization structures are migrated 1:1. Tikit's category hierarchy maps to most destination knowledge base category trees without transformation unless the destination enforces a flat structure. |
| Attachments | Mapping required | Tickets and KB Articles can have file attachments. We migrate attachments stored within Tikit's managed storage. Attachments linked via external URLs are preserved as references. Total attachment volume and file size limits must be verified against the destination platform's storage constraints. |
| SLA Policies | Mapping required | SLA definitions tied to ticket priority and department are migrated as configuration data. The destination platform may use different SLA metric naming (First Response vs. Initial Response, Resolution vs. Closure), requiring policy remapping during migration. |
| Automation Workflows | Mapping required | Tikit leverages Microsoft Power Automate for workflow automation. We export workflow logic as documented configuration, but Power Automate flows are platform-bound and must be rebuilt in the destination ITSM or workflow engine. We provide a workflow audit document to guide the rebuild. |
| Virtual Agent Configuration | Mapping required | The AI Virtual Agent handles initial ticket triage and self-service resolution. Its training data, intent mappings, and fallback configurations are exported as a configuration package. The destination AI agent (if any) requires re-training on the imported ticket corpus. |
| Asset Records | Mapping required | Asset management in Tikit includes device records linked to Intune and Entra ID. We export asset name, type, assigned user, and relationship data. Deep integration with Intune device properties does not export as standalone data and requires re-association in the destination CMDB. |
| Tags | Mapping required | Tickets and articles can be tagged for categorization. We export tag names and associations. Destination platforms with flat label systems will receive a comma-separated tag string; platforms with hierarchical tagging receive a structure-compatible mapping. |
Gotchas
What to watch for in Tikit migrations
Issues we've hit on past Tikit migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Power Automate workflows do not migrate automatically
Virtual Agent training does not transfer to the destination
Agent seat count scoping requires pre-migration planning
KB article attachments stored outside Tikit require manual retrieval
| Severity | Issue |
|---|---|
| High | Power Automate workflows do not migrate automatically |
| High | Virtual Agent training does not transfer to the destination |
| Medium | Agent seat count scoping requires pre-migration planning |
| Medium | KB article attachments stored outside Tikit require manual retrieval |
Leaving Tikit?
Where Tikit customers move next
7 destinations Tikit can migrate to.
How a Tikit migration works
Four steps, Tikit-specific
Connect
Not publicly documented into Tikit. Scopes limited to read-only on the data we move.
Map
We translate Tikit-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Tikit quirks before production.
Migrate
Full migration with Tikit rate-limit handling. Rollback available throughout.
FAQ
Tikit migration FAQ
Answers to the questions buyers ask most during Tikit migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Tikit 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.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Tikit setup and destination — written quote back within a business day.