Migrate your Deskhero data

Tickets are the primary object in Deskhero. We migrate tickets with their full conversation threads, status, priority, and timestamps. Custom ticket fields are preserved as key-value pairs. Deskhero does not cache Shopify live data inside tickets — product context is stored as references, so we migrate those references intact and flag them for destination-side Shopify reconnection.

Conversations are stored as nested message objects inside each Ticket. We preserve message authorship, timestamps, attachments references, and internal/external flags. Agent replies and customer messages are sequenced by timestamp during import.

Articles are standalone objects fed into the AI response engine. We migrate articles with their sections, categories, and attachment references. If the destination uses a different knowledge base schema, we flatten hierarchical articles into flat documents and preserve category assignments as tags.

Mailboxes represent connected Gmail or Outlook accounts with two-way sync. We migrate mailbox configurations and map them to the destination's inbox channel model. IMAP/SMTP credentials cannot be migrated — customers must re-authenticate their mailbox connection at the destination.

Deskhero supports up to 100 (Small) or 250 (Large) custom fields across tickets and contacts. Custom field definitions and their current values per ticket are migrated. Field type mapping depends on the destination — we convert Deskhero field types to nearest equivalents and flag unsupported field types for manual review.

Groups define team routing and agent permissions. We migrate Group definitions and their agent membership lists. If the destination uses a role-based access model instead of groups, we map group memberships to the nearest role or team structure.

Lists are segmentation objects with up to 5,000 or 10,000 entries depending on tier. We migrate list definitions and their entry records. Entries are tied to customer records by email or customer ID — we resolve these references and remap them in the destination.

Forms generate tickets from web submissions. We migrate form definitions (field structure, routing rules) and the submitted records. Form submissions that created tickets are linked via ticket references. Destination form recreation depends on the target platform's form builder capabilities.

Automation rules trigger on language, tone, or subject conditions to assign, tag, or triage tickets. We map these to the destination's automation or workflow engine. Not all platforms support the same condition triggers — we flag language-based and tone-based rules as requiring destination-specific equivalents.

Deskhero scrapes website pages to build knowledge base context. We migrate the scraped page URLs and their extracted content. The destination must either support its own scraping or have the content re-scraped there — we export the raw extracted text and category assignments.

Products and customer data sync from Shopify. Deskhero never caches price or stock — it queries live via Shopify API. We migrate Shopify store references, product ID mappings, and customer associations. Price and stock must be reconnected via API in the destination environment.