Migrate from Tidio to HubSpot Service Hub

Tidio Contact records map to HubSpot Contact. Standard fields (email, firstname, lastname, phone, location) map directly. Any custom contact properties on Tidio are mapped to HubSpot custom contact properties, which we pre-create during schema design if they do not already exist in the destination. We resolve duplicate contacts by email address using HubSpot's deduplication rules before insert.

Tidio Conversation threads map to HubSpot Tickets. We preserve the full message history, channel origin (email, chat, WhatsApp, Messenger, Instagram) as a custom Ticket property tidio_channel__c, assigned agent as the Ticket owner, status (open, resolved, pending) as Ticket status, and the original conversation timestamp. Resolved conversations become resolved Tickets; open conversations become open Tickets.

Tidio flat string tags migrate to HubSpot Ticket Labels. We export the full tag list and attach the corresponding labels to the migrated Ticket records. Labels in HubSpot Service Hub appear on the Ticket record and are filterable in the shared inbox view.

Tidio channel configuration (email addresses, WhatsApp number, Messenger page, Instagram account) includes platform-specific tokens and webhook URLs. We export the channel list and connection metadata as a structured JSON document. The customer's admin re-authorizes these channels in HubSpot Service Hub using the same connection flow. Channel token migration is not supported because OAuth tokens cannot be transferred between platforms.

Tidio Agent records (name, email, role) map to HubSpot User records. We match agents by email address. On Tidio Starter and Growth plans, user permissions and department assignments may be limited or absent; we flag any agent records with missing permission fields so the customer can configure RBAC in HubSpot post-migration.

Tidio Departments (available on Plus plan only) map to HubSpot Teams. We export department names, agent-to-department assignments, and routing rules as structured data. If the source account is on Starter or Growth, no departments exist and this step is skipped. Teams in HubSpot control ticket assignment, inbox routing, and team-level reporting.

Tidio Operating Hours are configured per-channel and control when automated replies fire. We export the configured hours as structured data (timezone, days, start time, end time) and document them for manual re-entry in HubSpot Service Hub under Business Hours settings.

Tidio Macros (pre-written response templates with variable placeholders) cannot be exported as reusable templates. We enumerate all macro names and content as a structured JSON manifest so the customer's admin can recreate them as Snippets in HubSpot Service Hub. Variable placeholders in Tidio macros map to HubSpot Snippet token syntax.

Tidio Flows are built in the visual drag-and-drop builder and cannot be exported via API. There is no destination equivalent in HubSpot Service Hub. We enumerate all active Flows by name, trigger type, block count, and step descriptions as a JSON manifest. The customer's admin rebuilds these manually using HubSpot workflow automation or a third-party chatbot builder (such as Tidio's own Flow builder re-implemented at the destination if the team chooses to maintain a chatbot alongside Service Hub).

Lyro Q&A pairs, imported Help Center articles, Shopify product feeds, and web page crawls are stored within Tidio's proprietary AI infrastructure with no export mechanism. We document which data sources were connected, their last sync dates, and the approximate volume of Q&A pairs so the customer's admin knows what content to re-upload and retrain in HubSpot Breeze AI Agents or another AI platform post-migration.

Tidio Visitor records include location, viewed pages, and session duration. Historical visitor aggregates are captured from conversation context. We export visitor location and session summary data as a custom property on the corresponding Contact record in HubSpot. Full visitor session history is not available via API and cannot be fully reconstructed.

Custom contact properties on Tidio may use Tidio-specific field names and types that need renaming and type-mapping at the destination. We audit all custom properties during scoping, flag any that require new HubSpot custom properties to be created, and verify type compatibility (text, number, date, checkbox, dropdown) before import. Property dependencies on other systems (e.g., Shopify data synced into Tidio) are documented for manual reconnection in HubSpot.