Migrate from C-Desk to HubSpot Service Hub

C-Desk tickets map to HubSpot Service Hub Tickets. We extract ticket subject, description, status, priority, and department/location metadata and write them to the corresponding HubSpot ticket properties. C-Desk department and location assignments map to custom ticket properties since HubSpot Service Hub Starter uses a single default pipeline. Teams on Professional tier can configure additional ticket pipelines to represent departments. Ticket creation timestamps preserve as hs_create_date for historical ordering. We flag any C-Desk ticket fields that cannot be directly mapped to HubSpot standard properties for custom property creation during schema setup.

C-Desk knowledge base articles migrate to HubSpot Knowledge Base articles, but HTML-mode content from C-Desk requires reformatting. We extract the article body and detect HTML elements (embedded styles, proprietary formatting, relative links). Articles with inline styles or non-standard markup are sanitized to plain text or clean HTML before import into HubSpot's knowledge base editor. HubSpot does not support raw HTML article content, so the reformatting step is required for all HTML-mode articles. We flag articles with broken links for the customer's admin to review post-migration.

C-Desk organizes knowledge base content into hierarchical topics and subtopics with cross-linking between nested structures. HubSpot Service Hub uses a flat category model without native subtopic nesting. We flatten the C-Desk topic hierarchy: top-level topics become HubSpot Knowledge Base categories, and subtopics become child categories. Cross-topic article links that point to subtopic-specific content are preserved as URL references and flagged for the customer's admin to update after migration since HubSpot does not support deep-linking into category hierarchies in the same way.

C-Desk email integration settings govern automated ticket creation from inbound email and acknowledgement notifications. We extract the email addresses and routing rules as configuration data and document them for the customer's admin to reconfigure in HubSpot's shared inbox settings. HubSpot's email-to-ticket routing is configured at the inbox level within Service Hub, not as standalone email integration settings. The admin rebuilds the routing rules (which address receives tickets, how routing assignment works) in HubSpot's inbox settings post-migration.

C-Desk user accounts map to HubSpot user records. We extract username, email address, display name, and role assignment. Role names from C-Desk (which may be custom-named per organization) are preserved in a custom property for manual remapping to HubSpot's built-in roles and permissions. Users who are inactive or deprovisioned in C-Desk migrate as inactive HubSpot users so that historical ticket assignments and activity records remain associated with the correct owner.

C-Desk role-based ticket access controls govern which users can view and modify tickets within specific departments and locations. HubSpot's permission model uses roles (built-in or custom) assigned at the account level, with private team views limiting ticket visibility. We map C-Desk department-based access rules to HubSpot private team views and document the translation. Any custom C-Desk role names are flagged as requiring manual remapping because HubSpot's role names follow a specific schema.

Ticket attachments and knowledge base article attachments are downloaded from C-Desk storage and uploaded to HubSpot's file management, then linked to the corresponding ticket or knowledge base article. We preserve the original filename and note the storage location in the migration log. C-Desk's storage location and access method must be confirmed during schema discovery; if C-Desk does not expose a direct download URL for attachments, manual extraction may be required and will extend the migration timeline.

C-Desk ticket comments and internal replies map to HubSpot Service Hub ticket conversation threads. We extract the comment body, author, timestamp, and visibility flag (internal vs. customer-facing). Internal comments from C-Desk map to HubSpot internal notes on the ticket; customer-visible replies map to the ticket conversation timeline. Author resolution uses the email-to-User lookup established during the user mapping phase.

C-Desk multi-department configuration routes tickets to different teams based on department assignment. On HubSpot Service Hub Starter tier, department maps to a custom ticket property. On Professional and Enterprise tiers, department maps to a separate ticket pipeline so each team has its own stages, SLA policies, and routing rules. We confirm the customer's HubSpot tier during scoping and design the department-to-pipeline or department-to-property mapping accordingly.

C-Desk supports multi-location service request routing. HubSpot Service Hub does not have a native location field on tickets. Location data migrates as a custom single-line text or dropdown property on the Ticket object. The customer chooses the property type during scoping, and we pre-create the property before migration begins.

C-Desk acknowledgement workflows are mentioned in product comparisons but no confirmed workflow builder or automation rule schema was found in research. We do not migrate workflow configurations as code. We extract and document the acknowledgement workflow behavior (which trigger creates acknowledgement, which email template fires, what delay applies) and deliver it as a written specification for the customer's admin to rebuild in HubSpot's workflow builder post-migration.

Research did not confirm support for custom fields or custom objects in C-Desk. We do not currently migrate custom fields for this platform. During schema discovery we request direct access to the C-Desk instance to verify whether any custom field schema exists. If custom fields are discovered during discovery, we will adjust the migration scope and mapping accordingly before presenting a final quote.