Migrate from Supportbench to HubSpot Service Hub

Supportbench Tickets map to HubSpot Tickets with full message history, timestamps, assignee, and SLA metadata preserved. The Supportbench ticket pipeline maps to HubSpot Ticket pipeline stages; multiple Supportbench pipelines map to multiple HubSpot Ticket pipelines available from Professional tier ($100/seat). Conversation threads migrate as Ticket replies with the original author preserved. Tag vocabularies from Supportbench migrate to HubSpot ticket properties or ticket topics depending on the customer's tagging strategy.

Supportbench Customers with a single associated Company record map to HubSpot Contact with a Company link via the contact-to-company association. Supportbench Customers that represent organizations (rather than individuals) map to HubSpot Companies directly. We resolve the split during scoping based on whether the Supportbench Customer has person-specific fields (name, email, phone) versus organizational fields (company name, domain, contract data). Health score migrates as a custom numeric field on Contact or Company respectively.

Supportbench Agent records map to HubSpot Users. We resolve agents by email match against the destination HubSpot portal. Role and team assignments map to HubSpot Teams and Permission Sets; Enterprise-tier unlimited custom roles from Supportbench may not have a direct HubSpot equivalent at the same tier and require manual reassignment during the admin rebuild phase.

Supportbench's internal Knowledge Base for agent use exports separately from the customer-facing external KB. Internal articles migrate to HubSpot Knowledge Base with the 'internal only' visibility flag applied. Article category hierarchy maps to HubSpot Knowledge Base section structure. Agent-facing articles without a customer-facing equivalent are flagged in the migration report for visibility review in HubSpot.

Supportbench's customer-facing Knowledge Base exports as a separate pass and maps to HubSpot Knowledge Base articles with public visibility enabled. Article attachments and embedded media migrate as HubSpot-hosted assets. Category and section taxonomy from Supportbench maps to HubSpot Knowledge Base sections with the same hierarchy depth preserved where possible.

Survey configuration (CSAT, NPS, CES question types, scoring rubrics) does not migrate structurally because HubSpot's Feedback Surveys use a different configuration model. We migrate historical survey response data as a custom object or as ticket properties tied to the original Supportbench ticket ID, preserving the score, response timestamp, and respondent reference. Survey widget configuration requires rebuild in HubSpot's Feedback Survey tool post-migration.

Supportbench tiered SLA policies with escalation stages, response targets, and resolution windows require reimplementation in HubSpot. Supportbench policies tied to customer tier and case context map to HubSpot Professional SLA policies (time-based targets) or Enterprise conditional SLA policies (with business hour rules and ticket property conditions) depending on the destination tier. We deliver a written mapping of every Supportbench SLA rule to its HubSpot equivalent during the migration scope phase.

Supportbench Company records holding licensing and contract data map to HubSpot Companies. The Salesforce linkage reference from Supportbench does not migrate as an active field; if the customer maintains Salesforce alongside HubSpot post-migration, a new native HubSpot-Salesforce sync is configured as a separate integration task. Contract and licensing metadata from Supportbench Company records migrates as custom properties on the HubSpot Company.

Supportbench custom fields on Tickets, Customers, and Companies map to HubSpot custom properties on the corresponding objects. We perform field-level type reconciliation: Supportbench date pickers become HubSpot date properties, dropdown fields become HubSpot single-select or multi-select picklists, and free-text fields become HubSpot text properties. Large custom field schemas require HubSpot Professional or Enterprise to accommodate all properties without hitting Starter-tier limits.

Customer health scores computed in Supportbench migrate as a static numeric custom property on the HubSpot Contact or Company record. The algorithm that produced the score is not transferable. Teams should establish a baseline score at cutover and plan to re-calibrate expectations against HubSpot's native customer success metrics (CSAT, NPS, CES surveys) or a third-party customer health tool integrated via HubSpot's API.

File attachments on Supportbench tickets are referenced by URL in the source system. We download the file content and re-associate it with the target HubSpot Ticket record. Large file batches (exceeding 100 attachments per ticket or files over 25 MB) require chunked migration passes to stay within HubSpot's file upload API limits. PDF and image attachments migrate with original filenames preserved.

Supportbench free-form ticket tag vocabularies export as flat lists and migrate to HubSpot as either Ticket Topics (for topic-based reporting) or multi-select picklist custom properties (for categorical filtering). The customer chooses the strategy during scoping. Tag deduplication happens during export to consolidate synonymous or duplicate labels before insertion into HubSpot.