Migrate from Tikit to HubSpot Service Hub

Tikit Tickets migrate to HubSpot Tickets with subject, description, status, priority, category, requester, assigned agent, and full conversation thread preserved. Custom ticket fields migrate as HubSpot Ticket properties. Tikit's conversation history (internal and external notes) maps to HubSpot Ticket conversations and the associated timeline on the Contact record. We resolve requester email against the migrated Contact record and assigned agent email against the migrated HubSpot User.

Tikit Agents are licensed named seats that map to HubSpot Users. We export agent profiles, display name, email, group assignments, and skill mappings. Note that Tikit's agent seat licensing model differs from HubSpot's per-seat Service Hub pricing, so the total agent count after migration affects the HubSpot subscription tier. We query agent count during scoping and model the billing impact before confirming the migration scope.

Tikit End Users (unlimited, unlicensable) map to HubSpot Contacts. We migrate display name, email address, and any contact properties from Tikit's End User profile. Teams presence data and Entra ID-linked profile fields (department, job title from Entra) do not have direct HubSpot equivalents and are flagged for manual enrichment post-migration if the organization maintains Entra ID integration.

Tikit's multi-department configuration (ticket routing, portal visibility, SLA assignments) maps to HubSpot Teams. We export the department structure, associated queues, and SLA policy bindings and configure HubSpot Teams with role-based Inbox assignments that replicate the routing logic. Department-specific SLA targets map to team-scoped SLA policies in HubSpot.

Tikit KB Articles (title, body content, category, publish status) migrate to HubSpot Knowledge Base Articles. Article category assignments map to HubSpot article category tags. Embedded file attachments stored in Tikit-managed storage migrate as HubSpot article file attachments. We document all external attachment URLs (SharePoint, OneDrive, third-party links) as a separate reference list because those links may break post-migration if source access is revoked.

Tikit article categorization structures migrate 1:1 to HubSpot Knowledge Base category hierarchies. The category tree maps without transformation unless HubSpot's portal visibility settings require flattening a deeply nested structure. We set article visibility to match the original Tikit portal-access configuration during migration.

SLA definitions tied to ticket priority and department migrate as configuration data. Tikit's SLA metric naming (First Response Time, Resolution Time, Business Hours settings) maps to HubSpot SLA response and resolution targets per ticket pipeline and team. We document the original SLA metric definitions and their thresholds in a configuration handoff sheet so the customer can verify SLA equivalence in HubSpot.

Ticket and KB article file attachments stored within Tikit migrate as HubSpot file attachments. Attachments linked via external URLs (SharePoint, OneDrive, third-party) are preserved as URL references only. If the source SharePoint site loses access post-migration, those links become broken. We document all external attachment sources during the pre-migration audit for the customer to verify access continuity before the cutover date.

Tikit's Microsoft Power Automate workflows do not export as portable logic. We produce a detailed workflow audit document during scoping that lists every active Power Automate flow, its trigger conditions, actions, and conditions. The customer uses this document to rebuild equivalent routing, approval, and notification logic in HubSpot Workflows post-migration. We do not rebuild workflows as code in the migration scope.

The Tikit Virtual Agent's trained intent classifications, knowledge base article associations, confidence thresholds, and fallback routing configuration export as a configuration summary document. This trained model is not transferable as a deployable artifact. The customer uses the configuration summary as the starting point for retraining HubSpot Breeze AI Agent with the migrated knowledge base content and ticket history. We include a KB article recommendation audit that maps Tikit deflection intents to HubSpot Breeze article suggestions.

Tikit asset records (device name, type, assigned user, Intune device relationship) migrate to HubSpot CRM assets where available. Note that HubSpot's asset management is available on Enterprise tier only and has a different data model from Tikit's Intune-linked asset tracking. Deep Intune device properties (compliance status, enrollment date, device management profile) do not have HubSpot equivalents and are documented as a separate asset reconciliation record for the customer's IT team.

Tikit ticket and article tags migrate as HubSpot Tags. We map tag associations to the migrated ticket and article records. If the customer's reporting requires tag-based segmentation in HubSpot, we recommend creating a tag-based contact or ticket property during post-migration configuration to enable filtering without relying on the Tags object alone.