Migrate from Thread to HubSpot Service Hub

Thread Review records (source platform, star rating, review text, response status, linked ticket reference) map to HubSpot Customer Feedback with the submission source preserved in a custom property. HubSpot does not have a native review-aggregation object, so we store the full review body, rating, and original review URL in custom properties on the Feedback record. Response history migrates as a linked conversation thread attached to the Feedback record. Review-source attribution (Google, Trustpilot, etc.) migrates as a custom picklist property to allow filtering by origin platform.

Thread review responses map to HubSpot Conversation records attached to the parent Customer Feedback. We enforce a dependency check: review responses are held in a migration queue until their parent review record is confirmed written to HubSpot. Without this check, responses migrate as orphaned text with no link back to the original review, which breaks the audit trail that customer support managers rely on. Response timestamps and agent attribution migrate directly.

Thread Conversations (message chains with timestamps, author attribution, and channel metadata) map to HubSpot Tickets with a linked Conversation thread in the HubSpot inbox. We flatten chronological message chains into a sequential Conversation record, preserving the original timestamp on each message entry. Channel metadata (email, chat, review channel) maps to HubSpot's ticket source field. Agent assignment from Thread Conversation becomes the Ticket's owner in HubSpot.

Thread Tickets with PSA-linked fields (from the ConnectWise or other PSA integration) map to HubSpot Tickets. We preserve Ticket status, priority, assignee, and any external PSA reference number in custom properties on the HubSpot Ticket. If Thread's PSA integration is active, we export the external reference as a read-only custom property and recommend the customer's admin establish a new PSA sync connection in HubSpot's integrations directory post-migration.

Thread User records (display name, email, role, team assignment) map to HubSpot User records. We resolve agents by email match against the destination HubSpot portal. Role assignments from Thread (admin, agent) map to HubSpot User roles, with the customer's HubSpot admin adjusting permissions post-import. Any Thread agent without a matching HubSpot User email is held in a reconciliation queue for the admin to provision before the migration phase resumes.

Thread Teams group agents and set basic routing rules. HubSpot separates Teams (for permissions) from Inboxes (for routing). We create a Team in HubSpot for each Thread team and configure an Inbox with the same routing target. Routing rules from Thread (which route by channel or tag) require manual rebuild in HubSpot's Inbox Settings under Routing Rules; we document the original routing logic in the automation inventory deliverable.

Thread Response Templates (canned replies with shortcut codes) map to HubSpot Canned Responses when the destination HubSpot portal is on Professional or Enterprise tier. Starter tier does not include Canned Responses, so we flag this gap and recommend either upgrading or using HubSpot's Snippets feature as a workaround. Template content and shortcut codes migrate as-is; the customer's admin assigns shortcut codes to keyboard shortcuts post-import.

Thread attachments stored on Thread's CDN require separate extraction and re-hosting. We download all file attachments, rename them with conversation identifiers, and upload them to HubSpot's file manager linked to the parent Ticket or Conversation record. File type and size limits follow HubSpot's attachment constraints (25 MB per file). Any attachment exceeding HubSpot's limit is flagged for the customer's admin to host externally and link via URL.

Thread Tags applied to tickets and reviews map to HubSpot Tags. We export the complete tag vocabulary and apply them to the migrated Ticket and Feedback records. Tags that exceed HubSpot's 50-character limit are truncated with a warning flag in the migration report. Tag-based reporting in Thread does not carry over; we recommend rebuilding reports in HubSpot's analytics builder post-migration.

Thread custom fields on Tickets and Conversations vary by account configuration. We export the complete custom property schema alongside the data and map each field to an equivalent HubSpot custom property. HubSpot property types (string, number, date, dropdown, checkbox) are matched to Thread field types during the mapping phase. Custom properties that have no HubSpot equivalent are created as text fields with a migration-note label so the admin knows the field originated from Thread.

Thread Integrations (HubSpot CRM, Mailchimp, Google Sheets, PSA platforms) expose connection metadata, API credentials, and sync state. We export integration configurations as reference data and flag which integrations have direct HubSpot Service Hub equivalents. HubSpot CRM sync connections must be re-established post-migration in HubSpot's integration settings; Mailchimp and Google Sheets connections migrate using HubSpot's native integrations. PSA sync connections (ConnectWise, etc.) require new OAuth setup in HubSpot's integrations directory.

Thread channels (review platforms, email, chat) carry metadata that does not have a dedicated HubSpot field. We map channel source to a custom HubSpot picklist property on Ticket named ticket_original_channel__c. This preserves the multi-channel context (Google Reviews, Trustpilot, direct email, etc.) for reporting without requiring the customer to cross-reference Thread's channel data manually.