Migrate from TeamSupport to HubSpot Service Hub

TeamSupport Tickets migrate to HubSpot Service Hub Tickets 1:1, preserving ticket fields (Type, Status, Priority, Source), custom field values, assignee (resolved via email against pre-created HubSpot Users), team (mapped via the Groups pre-creation), and ticket timestamps (created_date, modified_date). Ticket thread chronology is preserved by sequencing conversation entries in chronological order during import. TeamSupport's ticket Source field (email, chat, portal, API) maps to HubSpot's Ticket Origin property.

TeamSupport Customer records (name, email, phone, company, and custom fields) migrate to HubSpot Contacts. The HubSpot Contact serves as the Ticket Requester. We perform email-based deduplication during import, flagging existing HubSpot Contacts with matching emails rather than creating duplicates. Customer custom fields on TeamSupport migrate to HubSpot Contact Properties, with dropdown fields receiving explicit value mapping to HubSpot picklist options.

TeamSupport stores a company name on each Customer record. We split this into a HubSpot Company record (from the Customer's company field) and a Contact record (from the Customer's individual fields). The Company-to-Contact association is created at import time. Company custom fields migrate to HubSpot Company Properties with the same picklist value mapping process applied to dropdown fields.

TeamSupport Agents (Users) cannot be created via API. We require the customer to manually create HubSpot Users with exact email and name matches before migration begins, with the System Admin checkbox checked on each User profile. We resolve the TeamSupport agent_id-to-HubSpot user_id mapping by email match and use that lookup to set Ticket assignee during import. Any TeamSupport agent without a matching HubSpot User is placed in a reconciliation queue.

TeamSupport Groups cannot be created via API. We require the customer to manually create HubSpot Teams with exact name matches before migration begins. The Group-to-Ticket association is resolved by matching the Team name. Group names must be identical between the pre-created HubSpot Teams and the source TeamSupport Groups for association mapping to succeed. We provide a naming guide during discovery to ensure consistency.

TeamSupport Products migrate to HubSpot CRM Products. Product name, version, product line, and custom fields transfer 1:1. Product-to-Ticket associations are preserved by creating a Ticket association to the corresponding CRM Product. TeamSupport's product-centric ticketing model maps to HubSpot's ticket associations with the CRM Product object. If the destination HubSpot portal does not have the CRM Products feature enabled, we flag this during discovery and coordinate enabling before migration.

TeamSupport Product Versions are associated with Products and linked to Tickets for version-specific bug tracking. We map versions to a HubSpot Product Version property on the CRM Product object. If the customer uses version data in reporting, we recommend creating a custom number or text property on the Product object to carry the version name, or a custom Ticket property if version context lives at the ticket level rather than the product level.

TeamSupport Product Lines group related Products. HubSpot CRM Products do not have a native Product Line field. We recommend creating a HubSpot custom property on the Product object (Product_Line__c as a picklist) and mapping TeamSupport Product Line values to it during import. Category filtering in HubSpot reports can then use the Product_Line__c property for product-line-level analysis.

TeamSupport Inventory Assets link Products and Tickets and carry custom fields. HubSpot Service Hub has no native Inventory object. We map Inventory Assets to either HubSpot CRM Products (if the asset is product-like) or a HubSpot custom object (if the asset tracks physical or contractual inventory with specific attributes). The customer chooses the strategy during scoping. Custom fields on assets migrate to the chosen destination object.

TeamSupport KB articles and categories migrate to HubSpot Knowledge Base articles and categories. Category hierarchy is preserved during import. Article-to-category assignments transfer. Article visibility settings (public, internal) map to HubSpot article visibility flags. We do not migrate article view counts or analytics data; these reset in HubSpot.

TeamSupport ticket tags migrate to HubSpot Ticket Labels. TeamSupport's nested tag hierarchies are flattened into a single-label array per ticket. The customer confirms during scoping whether all tags should map directly or whether a tag consolidation is preferred before migration to reduce label proliferation in HubSpot.

TeamSupport internal notes and public replies on tickets are preserved as HubSpot Ticket conversation entries in chronological order. Agent vs. customer authorship is flagged so the destination applies the correct display logic (internal notes appear as private, replies appear as customer-facing). We preserve the original timestamp on each conversation entry to maintain thread chronology.

TeamSupport ticket attachments are downloaded individually via the API (no bulk export endpoint) and re-uploaded to HubSpot as Files associated with the corresponding Ticket. We chunk attachment batches to avoid source-side rate limits and implement retry logic with exponential backoff for both download and upload. Files over 50MB may require direct file-transfer coordination with the customer. Original filenames and MIME types are preserved. We do not migrate attachment view counts or comment threads.

TeamSupport dropdown custom fields on Tickets, Contacts, Companies, and Products require explicit value mapping to HubSpot picklist options. We audit all dropdown custom fields during discovery, produce a value-mapping table for customer review, and apply the mapping during import. Any TeamSupport dropdown value without a mapped HubSpot option defaults to null; we flag these in the mapping table before migration begins so the customer can decide whether to create the missing options in HubSpot or accept null values.