Migrate from Tiflux to HubSpot Service Hub

Tiflux Tickets migrate to HubSpot Service Hub Tickets. The HubSpot ticket pipeline is configured during schema setup to match Tiflux board statuses. SLA deadline timestamps migrate to a custom SLA properties (hs_sla_next_renewal and a calculated SLA_elapsed_hours field). Apontamento hours total migrates to a custom numeric field tiflux_apontamento_hours__c on each ticket so IT consultancies preserve billing data. Child tickets and ticket groupings are sequenced in dependency order (parent tickets imported first) to preserve the hubspot_parent_ticket_id reference. Tiflux ticket status (Aberto, Em Atendimento, Resolvido, Fechado) maps to HubSpot ticket status values configured in the pipeline.

Tiflux Clientes map to HubSpot Companies. Client annotations (anotações), resource groups, and client-level knowledge base associations migrate as notes and custom company properties. Client is created before any linked Contact or Ticket import so that the hubspot_company_id reference resolves at insert time. Tiflux client-specific SLA rules are documented as a custom company property tiflux_sla_policy__c for the customer's admin to activate in HubSpot SLA settings.

Tiflux Contatos map to HubSpot Contacts. Contact records carry name, email, phone, and extension fields from the source. Where the destination uses HubSpot's unified contact model, contacts are imported with their parent Company resolved via the Tiflux client linkage. Tiflux contact-level SLA parameters migrate as custom contact properties if they differ from the account-level SLA.

Tiflux Contratos (service agreements with hours, billing terms, and SLA parameters) do not have a native HubSpot equivalent. We create a custom HubSpot object called Agreement with fields for contract hours remaining, billing period, SLA tier, and the linked Company. Contract hours migrate as a numeric field so support teams can track consumed hours against the contract cap. Contract status (Ativo, Expirado, Cancelado) maps to a HubSpot custom Agreement status picklist.

Tiflux Usuários map to HubSpot Users. Users are matched by email address during migration. Any Tiflux user without a matching HubSpot User account goes into a reconciliation queue; the customer's HubSpot admin provisions missing users before the ticket import phase so OwnerId references resolve. Tiflux permission groups are documented as a role mapping reference for the admin to configure in HubSpot's User permission settings post-migration.

Tiflux Entidades are customer-defined custom entities attached to tickets, clients, or other objects. Each Entidade type requires pre-creation in HubSpot with a stable ID before any dependent Ticket records can reference it. We identify all Entidade types during the discovery phase, create the corresponding HubSpot custom objects (for entity types with relationships) or multi-select picklist fields (for flat attribute sets), and resolve the new HubSpot IDs before beginning the ticket import. If the customer created Entidades manually in Tiflux without capturing their source IDs, we extract the full Entidade record set via the Tiflux v2 API and help establish the mapping before importing tickets that reference them.

Tiflux knowledge base articles with client-linked and catalog categorization migrate to HubSpot Knowledge Base articles. Category structure and visibility rules map to HubSpot article categories and team-based publishing permissions. Article content migrates with HTML preserved. Client-specific articles are linked to the corresponding HubSpot Company via a custom article property. Portuguese-language articles are preserved as-is; the customer decides whether to translate post-migration.

Tiflux Activities and scheduled calendar commitments tied to tickets migrate to HubSpot Tasks. Periodicidade, due dates, and assignee information transfer to Task properties. Activity records without a ticket linkage migrate as standalone Tasks. Calendar-based activities that require Outlook or Google Calendar sync are flagged for the customer to configure HubSpot's calendar integration post-migration.

Tiflux Arquivos attached to tickets migrate as HubSpot Files with the file URL preserved as a reference. HubSpot attaches files to tickets via the CRM associations API. File content transfer depends on whether the source URL remains accessible during migration; we download files before the Tiflux write freeze and re-upload to HubSpot. Files without a valid URL in the source are flagged for the customer to re-attach manually.

Tiflux Grupos (resource allocation and permission scoping) map to HubSpot Teams. Group membership and linking to users migrate as HubSpot Team membership records. Tiflux permission scoping tied to specific clients or entities is documented as a configuration note for the admin to implement via HubSpot's team-based visibility settings.

Tiflux ticket groupings and child-ticket relationships (ticket filho) are detected during data audit and resolved in dependency order during import. Parent tickets are created first, then child tickets reference the parent via HubSpot's sub-ticket association. Grouping metadata from Tiflux (group name, grouping type) is preserved as a custom ticket property for reporting in HubSpot.

Tiflux SLA timers (deadline timestamps, pause/resume state, escalation flags) migrate to HubSpot SLA Policies configured during schema setup. We preserve the raw SLA deadline timestamp as a custom ticket property so the customer's admin can configure HubSpot SLA Policies to match the original SLA business hours and countdown logic. SLA pause/resume state migrates as a custom ticket property; HubSpot's SLA feature does not natively replicate pause behavior, so the admin rebuilds pause logic using a HubSpot workflow if required.