Migrate from Folder HelpDesk to HubSpot Service Hub

Folder HelpDesk Tickets map to HubSpot Service Hub Tickets with subject, body, status, priority, assignee, created/updated timestamps, and full conversation history including internal notes. HubSpot Tickets require a linked Contact record, so we insert Contacts before Tickets and resolve the hs_ticket_contact_id lookup at migration time. Thread order is preserved by sequencing conversation events with their original timestamps as HubSpot Ticket-engagement associations.

End-user contact records in Folder HelpDesk map to HubSpot Contacts with first name, last name, email, phone, and any custom field values. HubSpot Contacts are the primary lookup target for Tickets, so this object must import before Ticket ingestion. We deduplicate by email address and flag duplicates for admin review before final insert.

Company-level records in Folder HelpDesk (grouping multiple customers under one organization) map to HubSpot Companies. We map the organization name, domain, and any custom fields. If Folder HelpDesk organization records contain multiple contacts, each contact's Contact record receives the resolved CompanyId lookup at migration time after Companies are inserted.

Support team members who own tickets map to HubSpot Users. We resolve by matching agent email against HubSpot destination Users. Agents without a matching HubSpot User are placed in a reconciliation queue; the customer's HubSpot admin provisions missing Users before record import resumes. Agent role and group membership in Folder HelpDesk map to HubSpot Teams and User role settings post-migration.

File attachments on Folder HelpDesk tickets migrate as HubSpot ContentDocument records linked via ContentDocumentLink to the parent Ticket. HubSpot's API enforces a 60 MB per-file limit; Folder HelpDesk may impose lower per-file limits on the export side. We chunk large attachment batches, flag files exceeding HubSpot's limit for manual retrieval, and retry individual failed uploads with exponential backoff.

Labels applied to tickets in Folder HelpDesk migrate to HubSpot Ticket Tags. HubSpot uses a flat tag model; if Folder HelpDesk uses hierarchical labels, we flatten the path using a separator strategy (e.g., priority/escalation/tier2) and apply the flattened string as the tag name. Tags used for categorization migrate as-is; the customer confirms tag strategy during scoping.

User-defined fields on tickets or contacts are inspected during the discovery phase and mapped to HubSpot custom properties on the Contact or Ticket object. Each Folder HelpDesk custom field requires type alignment: text to string, date to date, dropdown to select, checkbox to boolean. Fields available only on higher Folder HelpDesk pricing tiers are flagged during discovery and replaced with destination-native equivalents or dropped if no equivalent exists.

Public help articles in Folder HelpDesk export as title, body HTML, category/section placement, and attachments. HubSpot provides a native Knowledge Base importer for article migration, which we recommend for bulk knowledge base transfers. We perform content normalization (markdown-to-HTML conversion where needed) and import via the HubSpot Knowledge Base API. Customer confirms whether articles should land in the HubSpot knowledge base, CMS Hub blog-style pages, or both.

Folder HelpDesk macros and email templates export as text content with variable placeholders. Complex conditional logic, delay rules, and dynamic content in Folder HelpDesk macros cannot migrate as code to HubSpot's workflow model. We deliver a written inventory of every macro with its trigger conditions, body text, and placeholder list for manual recreation in HubSpot as Snippets or Service Hub Workflows.

Folder HelpDesk team-level routing assignments map to HubSpot Teams. HubSpot's migration API does not support direct group creation, so we document the group name, membership, and routing rules in a written specification for the customer's HubSpot admin to provision manually before or after migration. The admin creates Teams in HubSpot Settings and assigns users during the post-migration configuration phase.

Billable or tracking hours logged against tickets in Folder HelpDesk map to a HubSpot Ticket custom property (e.g., time_spent_hours__c) or a linked custom Time Entry object if the customer's Service Hub Professional plan includes custom objects. We map time value, agent reference, and ticket linkage. Where HubSpot does not have a native time-tracking object, we use a numeric custom field on the Ticket for manual time entry by agents post-migration.

SLA rules and breach timers are computed by Folder HelpDesk in real time and do not export as historical data. The running breach clock resets on migration day. We inspect the source account's SLA configuration during discovery and deliver a written specification for each SLA policy (name, business hours, first response target, resolution target, applicable pipeline/stages) for manual recreation in HubSpot Service Hub Enterprise. Teams should set SLA timers fresh on migration day and monitor breaches from day one.