Migrate from Help Desk Premier to HubSpot Service Hub

Help Desk Premier Tickets map directly to HubSpot Service Hub Tickets. We preserve status, priority, assignee, requester, created_at, updated_at, and closed_at timestamps. Custom Ticket Fields use a field-level mapping pass: picklist fields map to HubSpot dropdown or radio select, numeric fields map to HubSpot number properties, date fields map to HubSpot date properties, and boolean fields map to HubSpot checkbox properties. The original Help Desk Premier ticket ID is preserved in a custom property hd_ticket_id__c for audit and reconciliation.

Help Desk Premier Customer records map to HubSpot Contacts. The customer email becomes the Contact email and the dedupe key. Display name splits into firstname and lastname where available; when only a full name field is present we use it as the lastname value and flag it for post-migration review. Phone, company association, and any custom contact fields migrate to HubSpot Contact properties via the mapping pass. Duplicate detection runs on email before insert.

Help Desk Premier Company or organization records map to HubSpot Companies. Company name becomes the Company name, domain maps to Website, and custom company-level fields use the same type-mapped field pass as Contact custom fields. Companies are imported before Contacts so that the Company lookup is satisfied at Contact insert time. When Help Desk Premier edition does not include a Companies object we skip this object entirely and Contacts remain unassociated to a Company record.

Help Desk Premier Agent records carry display name, email, role, and group membership. We map agents to HubSpot Users by email match. Role terminology varies by Help Desk Premier edition; we detect the role field schema during the initial export scan and map it to HubSpot's Teams structure. Any agent without a matching HubSpot User is held in a reconciliation queue for the customer's admin to provision the destination User before record import resumes.

Help Desk Premier Teams or Groups map to HubSpot Teams. Team name and membership migrate directly. Some Help Desk Premier editions restrict team membership to a single agent; we detect this constraint during schema scan and flag it in the migration report. Multi-agent teams map to HubSpot Teams with all members added via the team membership API.

Help Desk Premier Conversations and ticket comments map to HubSpot Ticket Conversations. Each conversation record carries the comment body, author, privacy flag, created date, and any attachments. Comment author resolves to the corresponding HubSpot User or Contact record via email lookup. Private comments from Help Desk Premier migrate as internal ticket notes in HubSpot. We handle high-volume conversation imports with chunked reads to avoid memory exhaustion on large ticket histories.

Help Desk Premier Tags migrate to HubSpot Tags on Tickets and Contacts. Tag vocabularies vary in length and character composition; we normalize tag names during the mapping pass by stripping special characters that HubSpot's tag system does not support. The original tag string is preserved in a migration tag for admin reference.

Help Desk Premier Knowledge Base Articles and KB categories migrate as HubSpot Knowledge Base articles and category folders. We preserve article body content, category hierarchy, publication status, and article author. Category parent-child relationships are reconstructed in HubSpot as folder hierarchies. Article associations to specific tickets do not migrate as ticket-linked content; articles are published to the KB independently of any single ticket.

Help Desk Premier ticket attachments migrate as HubSpot Files attached to Tickets. The attachment path reference is preserved in the migration report. Files exceeding Help Desk Premier's 48 MB per-entity cap are flagged in the migration report and skipped during automated export; we offer a post-migration recovery script that downloads oversized attachments from the source directly into HubSpot's file storage. Attachment author and created date are preserved as metadata on the HubSpot file record.

Custom fields on Help Desk Premier Tickets may use picklist, text, numeric, date, or boolean types. We read the field schema via export parsing, map each field to the closest HubSpot property type, and create the property in HubSpot before migration begins. Any Help Desk Premier field types without a HubSpot equivalent (for example, a multi-select with more than 200 options exceeding HubSpot's picklist limit) are flagged in the mapping report for admin decision on how to handle: truncate, split into multiple fields, or store as a text property.

Custom fields on Help Desk Premier Customer records follow the same field-level mapping pass as Ticket custom fields. String fields map to HubSpot single-line text or multi-line text depending on character count. Boolean fields map to HubSpot checkboxes. Date fields map to HubSpot date properties. The mapping is applied before Contact import to ensure destination properties exist at insert time.

Custom fields on Help Desk Premier Company records map to HubSpot Company custom properties using the same type-mapped pass. These are created in HubSpot before Company import and before Contact import so that all properties are available at record insert time. When Help Desk Premier edition lacks a Companies object this mapping is skipped entirely.