Migrate your Tiflux data
Brazilian ITSM and multichannel help desk platform built for IT service providers, with ticketing, SLA management, time tracking, and an AI agent layer.
In its favor
Why people choose Tiflux
The signal that keeps Tiflux on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Multichannel intake from email, WhatsApp, chat, and portals unified in a single ticket queue, reducing context-switching for support teams managing high volumes.
Built-in SLA tracking with deadline timers, pause functionality, and escalation rules that work out of the box without extensive configuration.
Time tracking (apontamento de horas) directly on tickets is native to the workflow, satisfying billing and consultancy firms that charge by the hour.
A Portuguese-language-first interface with strong presence in the Brazilian ITSM market, lowering adoption friction for local IT service providers.
The platform includes an AI agent layer that can be trained on company-specific processes, differentiating it from generic help desk tools.
Office integration is reported as weak, making it difficult to embed documents or trigger workflows tied to Microsoft productivity tools.
The platform is primarily documented and supported in Portuguese, creating a barrier for non-Portuguese-speaking teams evaluating it for global operations.
Limited public API documentation and lack of a developer community make custom integrations or automation extensions harder to build and maintain.
Reasons to switch
Why people leave Tiflux
The recurring reasons buyers give for replacing Tiflux. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Tiflux 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
Tiflux pricing overview
Tiflux does not publish pricing publicly. Quotes are handled through direct sales contact, with API access licensed as an add-on per user. A free demo is available without requiring a credit card.
Not publicly listed
Tier 1 of 1
Contact sales
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Tiflux's schedule — see our quote-based pricing →
What gets migrated
Tiflux object support
Object-by-object support for Tiflux migrations. Per-pair details surface during scoping.
Tickets
Fully supportedThe primary object in Tiflux. Tickets carry requester info, client linkage, SLA timers, apontamento hours, custom entities, child-ticket relationships, and board assignments. We migrate tickets 1:1, preserving status, priority, assignee, and timestamp fields. Child tickets and ticket grouping are mapped to the destination's hierarchy model.
Clients (Clientes)
Fully supportedClients are the organizational entities linked to tickets. We carry over client records with their associated annotations (anotações), resource groups, contracts, and contacts. Client-level knowledge base associations are preserved as relationships in the destination system.
Contacts (Contatos)
Fully supportedContacts belong to clients and are the requester entities on tickets. We map contact records with name, email, phone, and extension fields. Where the destination uses a unified contact model, we merge contact and requester data cleanly.
Contracts (Contratos)
Mapping requiredContracts link clients to service agreements and govern SLA parameters. We export contract records with their associated hours, billing terms, and SLA rules. Mapping to destination contract or agreement objects requires field-level alignment of terms and hour allocations.
Users (Usuários)
Mapping requiredUser records include name, email, role, and permission group membership. Tiflux permission groups do not map 1:1 to every destination's role model, so we map the most granular role assignment and flag any group-based permissions for manual review after migration.
Custom Entities (Entidades)
Mapping requiredEntidades are custom field groups attached to tickets, clients, or other objects. Each entity has a type, ID, and field values we collect via the API. Because entity schemas are customer-defined, we treat them as dynamic objects and map each field individually to the destination custom field model.
Knowledge Base (Base de Conhecimento)
Mapping requiredArticles are linked to clients and catalogs. We export article content, categorization, and client associations. Category structure and visibility rules require field-level mapping to the destination KB model.
Activities and Schedules (Atividades e Compromissos)
Mapping requiredActivities are scheduled tasks and calendar commitments tied to tickets or general workflows. We export activity records with periodicity, dates, and assignee. Mapping to destination calendar or task objects requires field alignment on recurrence patterns.
Attachments (Arquivos)
Mapping requiredFiles are attached to tickets at creation or during conversation threads. We export attachment URLs and metadata. File content transfer depends on whether the destination supports the same format and storage model; we flag large files or unsupported formats for manual handling.
Groups and Permissions (Grupos)
Mapping requiredGroups manage resource allocation and permission scoping. We export group membership and linking to users and clients. Destination permission models vary significantly, so we map group names and member lists as a reference dataset and flag for configuration review.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | The primary object in Tiflux. Tickets carry requester info, client linkage, SLA timers, apontamento hours, custom entities, child-ticket relationships, and board assignments. We migrate tickets 1:1, preserving status, priority, assignee, and timestamp fields. Child tickets and ticket grouping are mapped to the destination's hierarchy model. |
| Clients (Clientes) | Fully supported | Clients are the organizational entities linked to tickets. We carry over client records with their associated annotations (anotações), resource groups, contracts, and contacts. Client-level knowledge base associations are preserved as relationships in the destination system. |
| Contacts (Contatos) | Fully supported | Contacts belong to clients and are the requester entities on tickets. We map contact records with name, email, phone, and extension fields. Where the destination uses a unified contact model, we merge contact and requester data cleanly. |
| Contracts (Contratos) | Mapping required | Contracts link clients to service agreements and govern SLA parameters. We export contract records with their associated hours, billing terms, and SLA rules. Mapping to destination contract or agreement objects requires field-level alignment of terms and hour allocations. |
| Users (Usuários) | Mapping required | User records include name, email, role, and permission group membership. Tiflux permission groups do not map 1:1 to every destination's role model, so we map the most granular role assignment and flag any group-based permissions for manual review after migration. |
| Custom Entities (Entidades) | Mapping required | Entidades are custom field groups attached to tickets, clients, or other objects. Each entity has a type, ID, and field values we collect via the API. Because entity schemas are customer-defined, we treat them as dynamic objects and map each field individually to the destination custom field model. |
| Knowledge Base (Base de Conhecimento) | Mapping required | Articles are linked to clients and catalogs. We export article content, categorization, and client associations. Category structure and visibility rules require field-level mapping to the destination KB model. |
| Activities and Schedules (Atividades e Compromissos) | Mapping required | Activities are scheduled tasks and calendar commitments tied to tickets or general workflows. We export activity records with periodicity, dates, and assignee. Mapping to destination calendar or task objects requires field alignment on recurrence patterns. |
| Attachments (Arquivos) | Mapping required | Files are attached to tickets at creation or during conversation threads. We export attachment URLs and metadata. File content transfer depends on whether the destination supports the same format and storage model; we flag large files or unsupported formats for manual handling. |
| Groups and Permissions (Grupos) | Mapping required | Groups manage resource allocation and permission scoping. We export group membership and linking to users and clients. Destination permission models vary significantly, so we map group names and member lists as a reference dataset and flag for configuration review. |
Gotchas
What to watch for in Tiflux migrations
Issues we've hit on past Tiflux migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API v1 is discontinued; only v2 is active
API rate limit of 120 requests per minute per user license
Entidades require pre-existing IDs to link ticket records correctly
Child ticket and ticket grouping dependencies must be sequenced
| Severity | Issue |
|---|---|
| High | API v1 is discontinued; only v2 is active |
| Medium | API rate limit of 120 requests per minute per user license |
| Medium | Entidades require pre-existing IDs to link ticket records correctly |
| Medium | Child ticket and ticket grouping dependencies must be sequenced |
Leaving Tiflux?
Where Tiflux customers move next
7 destinations Tiflux can migrate to.
How a Tiflux migration works
Four steps, Tiflux-specific
Connect
Not publicly documented in available sources into Tiflux. Scopes limited to read-only on the data we move.
Map
We translate Tiflux-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Tiflux quirks before production.
Migrate
Full migration with Tiflux rate-limit handling. Rollback available throughout.
FAQ
Tiflux migration FAQ
Answers to the questions buyers ask most during Tiflux migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Tiflux 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 Tiflux.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Tiflux setup and destination — written quote back within a business day.