Migrate from Plumsail HelpDesk to HubSpot Service Hub

Plumsail Tickets map directly to HubSpot Tickets. We preserve Plumsail ticket status (New, Open, Pending, Resolved, Closed), priority (Low, Normal, High, Urgent), assignee (resolved to HubSpot User), created date, and updated date as native HubSpot Ticket properties. Plumsail ticket ID is stored in a custom property hs_original_ticket_id__c for reconciliation. Custom SharePoint columns on the ticket list migrate as custom Ticket properties, with field type mapped to the nearest HubSpot equivalent (text, number, date, single-select picklist).

Plumsail Contacts are SharePoint contacts list items linked to tickets by email or ID. We map contact name, email, phone, organization linkage, and any custom contact fields to HubSpot Contact properties. The Plumsail contact-to-organization linkage maps to a HubSpot Company association on the Contact. If a Plumsail contact has no matching HubSpot Contact (email dedupe), we create a new Contact record. HubSpot's unified contact model means every support ticket lands on the same contact record that sales and marketing teams use.

Plumsail Organizations (companies) are a distinct SharePoint list linked to Contacts and Tickets. We map organization name, domain, address, phone, and any custom organization properties to HubSpot Company records. Plumsail organization ID is stored in a custom property hs_original_org_id__c for reconciliation. Company is created before Contact import so that the Company-to-Contact association is satisfied at insert time.

Plumsail Agents are SharePoint users with the HelpDesk Agent role. We map agent email, name, and active status to HubSpot User records. Ticket assignee fields are resolved by matching Plumsail agent email to HubSpot User email and writing the HubSpot OwnerId. Plumsail's admin-agent role distinction maps to HubSpot Super Admin vs regular User roles. If a Plumsail agent has no HubSpot User account, we flag them for admin provisioning before the ticket migration phase begins.

Plumsail Comments (both public customer-visible messages and private agent-only notes) are SharePoint list rows on the ticket. We map each comment to a HubSpot Ticket timeline entry, preserving author (resolved to HubSpot User or Contact), body content, and timestamp. Private Plumsail comments map to internal HubSpot ticket notes with isPrivate=true. Public comments map to external timeline entries. We flag the estimated comment count during scoping against the customer's Plumsail plan limit ($49 tier: 2,000/month; $99 tier: 5,000/month) and recommend ingestion pacing to avoid billing spikes.

Plumsail Tags are SharePoint taxonomy or choice-field keywords applied to tickets. We map tag strings to HubSpot Ticket Tags, preserving tag names and counts exactly. HubSpot's native tag model supports adding and removing tags per ticket after migration. Tags with special characters or naming conventions that conflict with HubSpot tag rules are flagged during scoping for manual renaming before import.

Plumsail Categories are choice or lookup field values for structured ticket classification. HubSpot does not have a native Category object on Tickets, so we map categories to a HubSpot custom Ticket property of type multi-select picklist named OriginalCategory__c. Category values not already present in HubSpot's picklist options are added during the schema preparation phase. If a Plumsail ticket has multiple category assignments, all values migrate as multi-select entries on the same field.

Plumsail Knowledge Base articles are SharePoint pages in the HelpDesk site. We migrate article title, body content, category associations, and publication status to HubSpot knowledge base articles. Rich formatting, embedded images, and hyperlinks may require post-migration validation and cleanup. HubSpot knowledge base article IDs are stored in a custom property plumsail_article_id__c on the HubSpot article for reference. The HubSpot knowledge base requires a HubSpot CMS subscription or Knowledge Base add-on.

Plumsail SLA rules define response and resolution time targets by ticket priority or type. We map SLA configurations as rule definitions in an SLA handoff document covering trigger conditions, time targets, and escalation actions. HubSpot Service Hub does not natively enforce time-based SLA breach alerts in Starter or Professional tiers; SLA enforcement at the destination requires a HubSpot workflow, a Service Hub Enterprise SLA configuration, or a third-party SLA app from the HubSpot Marketplace. We document the gap and provide the rebuild recommendation.

Plumsail file attachments on tickets are stored in SharePoint document libraries linked to ticket items. We migrate attachment files and associate them with the corresponding HubSpot Ticket record. Large attachment volumes (hundreds of MBs or GBs) stress SharePoint's API during read and require staged ingestion with HubSpot file upload pacing. We flag the estimated attachment storage volume during scoping. HubSpot file storage counts against the customer's HubSpot file storage quota.

Plumsail Views are saved SharePoint list views with filters, groupings, and column ordering. Views are SharePoint-specific configuration and do not migrate as reusable HubSpot artifacts. We document each view's filter criteria, sort order, and column selection as a reference table for the customer's admin to recreate in HubSpot using saved filters, custom reports, or the HubSpot reporting builder.

Plumsail's embedded support widget is a portal component configured in the Plumsail admin. We inventory widget settings including branding, ticket form fields, submission rules, and CSP script source. Due to March 2026 SharePoint CSP enforcement, the Plumsail widget may fail to load after the deadline. We include a widget replacement plan recommending HubSpot's native chat widget and customer portal setup as the replacement, with a step-by-step handoff checklist.