Migrate from ProProfs Help Desk to HubSpot Service Hub

ProProfs Tickets map directly to HubSpot Tickets. The ProProfs ticket status (open, pending, resolved, closed) maps to HubSpot pipeline stage values that we configure before migration, defaulting to the standard Open / Pending / Closed statuses. Ticket priority from ProProfs migrates to the hs_ticket_priority property. The original ProProfs ticket ID is preserved in a custom field proprofs_ticket_id__c for audit and cross-reference.

ProProfs Customer records map to HubSpot Contacts. Email address is the dedupe key. First name, last name, phone, and address fields map to their HubSpot equivalents. ProProfs customer records that have no email (rare) are flagged for the customer's admin to resolve before import because HubSpot Contacts require an email as the primary identifier.

ProProfs Company records map to HubSpot Companies with domain, name, and address preserved. Company-customer associations migrate as Company associations on the HubSpot Contact record. If ProProfs company records have no domain name, we use company name as the dedupe key instead.

ProProfs Agent profiles (name, email, role) map to HubSpot Users by email match. ProProfs admin role maps to HubSpot Admin; ProProfs agent role maps to the most permissive non-admin HubSpot role. Team groupings from ProProfs do not map directly to HubSpot Teams (available at Professional+); we document team membership in a custom field proprofs_team__c for the admin to assign in HubSpot after migration.

ProProfs ticket thread messages migrate as HubSpot Ticket Comments. Each comment preserves author (agent or customer), body content, timestamp, and visibility. Public replies map to standard HubSpot ticket comments; private agent notes from ProProfs map to HubSpot internal ticket comments if the destination portal has the internal comments feature enabled. Attachments migrate as ContentDocumentLink records attached to the parent Ticket.

ProProfs labels are flat (no hierarchy) and migrate as HubSpot Tags on the Ticket object. All label-to-ticket associations are preserved by creating TagAssociation records during migration. If label count exceeds HubSpot's practical tag limit (thousands of tags are supported but management becomes unwieldy), we flag this during scoping for the customer to consolidate before migration.

ProProfs seven custom field types map to HubSpot custom properties of equivalent type: text to single-line text or multi-line text, number to number, dropdown to single-select, date to date, checkbox to single-checkbox (boolean), multi-select to multi-select, and user reference to a contact lookup property. Field values exceeding HubSpot type constraints (e.g., a text field storing a date that fails HubSpot date validation) are flagged in a pre-import validation report for customer review before the import phase begins.

ProProfs knowledge base articles exported as JSON or XML (page-level export) map to HubSpot knowledge base articles. Article title, body content, author, category, and status (draft/published) migrate directly. Article ordering and URL slugs are preserved. We use page-level JSON/XML export as the primary source; full-site PDF exports are flagged as fallback only because PDF content requires OCR or manual reconstruction and is not included in the standard migration scope.

ProProfs knowledge base categories (from the JSON export) map to HubSpot knowledge base categories. Category hierarchy (parent and child categories) migrates with the parent_id reference preserved. If the ProProfs export does not include category metadata, we request the full knowledge base content list from ProProfs support before migration.

Files attached to tickets or knowledge base articles are exported with their original filenames and MIME types. We transfer binary attachments via direct URL fetch when ProProfs provides accessible attachment URLs, or via the ProProfs API if available. Attachments land as ContentDocument records with ContentDocumentLink associations to the parent Ticket or knowledge base article. Files exceeding 25 MB are flagged because HubSpot ContentDocument has a 25 MB per-file upload limit via API.

ProProfs canned responses have no export API. We do not migrate them. During the scoping call we capture a screenshot and written specification of every canned response (name, shortcut, body content, merge fields) so the customer can recreate them manually in HubSpot using the Snippets feature (available in Conversations Inbox) or as a HubSpot Workflow action. This is documented in the migration plan as an explicit manual step.

ProProfs automation rules are stored server-side with no documented export endpoint. We do not migrate them. We capture the rule names, trigger conditions, filter criteria, and action sets as a written specification document during scoping. The customer rebuilds these in HubSpot Workflows (available from Starter tier at $9/seat) using the functional equivalent: ticket creation triggers, property-update actions, notification actions, and SLA milestone timers. SLA thresholds are documented separately for manual reconfiguration in HubSpot Service Hub Professional+ settings.