Migrate from Deskpro to HubSpot Service Hub

Deskpro Tickets map to HubSpot Tickets with status mapped to HubSpot ticket_pipeline_stage, priority mapped to hs_ticket_priority, and the Deskpro ticket subject preserved in the hs_subject property. Internal notes on Deskpro tickets migrate as private internal notes in HubSpot. Deskpro ticket channels (email, chat, social) map to HubSpot inbox source values. SLA breach timestamps from Deskpro migrate as custom datetime fields if the destination HubSpot tier supports SLA management. Stat Builder 2500-record chunking applies to historical ticket export; we paginate using ticket ID ranges for large histories.

Deskpro Agents map to HubSpot Users. We resolve by email address match. Agent-level settings including department assignment, language preference, and ticket routing preferences migrate as HubSpot User properties. Active and inactive agent status is preserved. Any Deskpro Agent without a matching HubSpot User is placed in a reconciliation queue for the customer's admin to provision before the production migration phase begins.

Deskpro Peoples (individual customers) merge into HubSpot Contact records. The mapping uses the Deskpro person ID as a reference anchor and preserves individual contact properties including name, email, phone, and address fields. Deskpro person-level custom fields migrate as HubSpot Contact properties. Because Deskpro Peoples and Organizations are separate objects, the Deskpro person-to-organization linkage (which Deskpro stores as a relationship property) is preserved by resolving the corresponding Organization-to-Company mapping after the Organizations phase completes.

Deskpro Organizations map to HubSpot Companies. Organization name, domain, address, and industry fields map directly. Organization-level custom fields migrate as HubSpot Company properties. The Deskpro Organization-People relationship is resolved at migration time: each merged Contact receives the HubSpot Company record as its primary company association, so the Deskpro organization contact hierarchy is preserved in HubSpot's Contact-Company data model.

Deskpro Knowledge Base articles migrate as HubSpot Knowledge Base articles with article body, publish status, author attribution, and multilingual variants preserved. Article URLs from Deskpro are noted but not replicated as HubSpot URLs (which are regenerated by HubSpot). Articles linked to parent Folders are re-linked to the corresponding HubSpot Knowledge Base category during migration. Article publish date and last-modified date are preserved as HubSpot article metadata.

Deskpro Folders (the container layer in the Categories > Folders > Articles hierarchy) map to HubSpot Knowledge Base categories. HubSpot does not support a two-tier folder structure natively. We collapse Deskpro Categories and Folders into HubSpot flat categories during migration and flag the collapse in the migration report so the customer can reorganize categories post-migration. Folder-level permissions from Deskpro do not transfer; we document them as a configuration recommendation for HubSpot Knowledge Base article-level permissions.

Deskpro custom fields on tickets are discovered via the Deskpro reports API with a custom field prefix, capturing field IDs, types, and label names. Custom field definitions are exported before data migration begins, and corresponding HubSpot ticket properties are pre-created via the HubSpot Properties API with matching field types (text, number, date, checkbox, dropdown). Active dropdown values in Deskpro map to HubSpot option array on the corresponding property. We flag any Deskpro field types without a native HubSpot equivalent for custom field type mapping during scoping.

Deskpro ticket tags migrate to HubSpot Ticket Tags. The full tag vocabulary is created in HubSpot during migration to match Deskpro naming. Tags stored as multi-checkbox custom properties on tickets (distinct from the native ticket tag object) migrate as HubSpot multi-select picklist properties on the ticket. We preserve the full tag assignment history on every imported ticket.

File attachments on Deskpro tickets are downloaded from Deskpro's attachment storage to a staging bucket, then uploaded to HubSpot via the HubSpot Files API. Each attachment is linked back to the corresponding HubSpot ticket as a ticket attachment or timeline attachment. Attachments exceeding 250 MB trigger a chunked upload via the HubSpot multipart file upload mechanism. The original filename and MIME type are preserved. Email inline images are handled as embedded ContentDocument records linked to the ticket timeline.

Deskpro Departments organize agents and ticket routing. We map department records to HubSpot Teams. Agent-to-department assignments are preserved as HubSpot Team membership. Deskpro department-level SLA rules are documented as HubSpot SLA configuration recommendations, as SLA management configuration does not transfer as data.

Deskpro automations including triggers, workflow rules, and SLA policies are not transferable to HubSpot because they use fundamentally different automation engines. We export a written inventory of every active Deskpro automation with its trigger conditions, actions, and timing as a CSV and Markdown specification. The customer's HubSpot admin uses this document to rebuild equivalent automations in HubSpot Workflows and SLA settings. SLA rules specifically map to HubSpot SLA policies in Service Hub Professional and Enterprise tiers.

Deskpro ticket internal notes migrate as HubSpot conversation internal notes on the ticket timeline. Internal notes are attributed to the original Deskpro agent by resolving the agent email to the HubSpot User record. Note timestamp is preserved as the timeline entry date. Internal notes are marked private in HubSpot and are not visible to the end customer.