Migrate from Deskero to HubSpot Service Hub

Deskero Tickets map directly to HubSpot Tickets. We map standard fields (subject, status, priority, assignee, created date) and preserve thread history as ticket comments. Channel origin (web, email, chat, social) maps to HubSpot ticket properties as a custom source field. Deskero's ticket ID is preserved in a custom property deskero_ticket_id__c for audit and cross-reference during the parallel-run window.

Deskero Customer records map to HubSpot Contacts. We map name, email, phone, and company associations. The Deskero Preferred Client flag maps to a boolean custom property deskero_preferred_client__c on the Contact. If Deskero stores company associations separately from the customer record, we map them to HubSpot Company records and create Contact-to-Company associations during import. Deskero's customer ID is preserved in deskero_customer_id__c.

When Deskero Customer records carry a company association, we map that to a HubSpot Company record. The company name becomes the Company Name field; the company domain (if present in Deskero) becomes the Website field. Company acts as the parent record for Contact association so that agents see the full account context when opening a ticket.

Deskero Knowledge Base articles map to HubSpot knowledge articles. We map article title, body content (as HTML), category assignments, and publish status. If the Deskero KB export includes view counts or last-updated timestamps, we store those in custom article properties. HubSpot's knowledge base requires category hierarchy to be rebuilt; we reconstruct the category tree from the exported content during import. We recommend using HubSpot's pre-built Knowledge Base importer for the article body pass and supplement with custom property values via our import pipeline.

Deskero Canned Answers map to HubSpot Saved Replies (available in Professional and Enterprise tiers). We map template name, content, and category grouping. Saved Replies in HubSpot are accessible from the inbox and can be inserted into ticket conversations. If the customer uses Canned Answers with conditional logic, we document that behavior for rebuild as HubSpot saved replies or macros.

Deskero Tags applied across tickets and customers map to HubSpot Labels on the Ticket object. We map all active tag strings and preserve their associations to records. Tag distribution counts are preserved during import. Labels in HubSpot appear on the ticket record and can be used for filtering and reporting.

Deskero custom fields on tickets map to HubSpot custom properties on the Ticket object. Since Deskero provides no public schema documentation, we request a manual field inventory from the customer's admin during scoping, identify each active custom field, and map it to a HubSpot property of the matching type (text, number, date, checkbox, dropdown). We pre-create the destination properties before migration begins.

Deskero custom fields on customers map to HubSpot custom properties on the Contact object. As with ticket custom fields, we request a manual field inventory during scoping since no public Deskero schema is documented. If a Deskero custom field has the same name as a ticket custom field, we ensure distinct property names in HubSpot to avoid collision on the Contact record.

Deskero agents map to HubSpot Users. We resolve agents by email match against the destination HubSpot portal's User table. Any Deskero agent without a matching HubSpot User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Agent permissions and roles do not migrate as configuration; they are set up in HubSpot by the admin post-migration.

Deskero social monitoring mentions that are linked to tickets migrate as ticket comments with the source channel noted in a custom property deskero_social_source__c. We extract the mention content, timestamp, and channel (Twitter, Facebook, etc.) and append it to the corresponding HubSpot Ticket as an internal or public comment depending on the customer's visibility preference. Unlinked mentions are flagged during scoping for customer decision: import as standalone tickets, merge into existing tickets, or exclude.

Unlinked Deskero social monitoring mentions that the customer chooses to preserve migrate as standalone HubSpot Tickets created with a social source tag and the original mention content. These do not have a contact association in Deskero, so they land as tickets without a Contact link unless the customer's admin opts to merge them into existing tickets during the reconciliation phase.

Deskero Canned Answer category groupings map to HubSpot Knowledge Base Topics. Topics in HubSpot are the organizational unit for knowledge articles and can be used to group related content for the customer portal. We map the category names from Deskero and create corresponding Topics in HubSpot before article import begins.

Deskero workflow rules, SLA settings, and escalation logic are platform-level configuration that cannot be exported as structured data. We do not migrate them. We deliver a written inventory of every active Deskero workflow with its trigger conditions, actions, and escalation rules, and the customer's HubSpot admin rebuilds equivalent logic using HubSpot Workflows post-migration. SLA enforcement in HubSpot is available at Professional tier and above.