Migrate from Freshservice to Freshdesk

Freshservice Tickets (called Incidents in ITIL terminology) map directly to Freshdesk Tickets via the Freshworks API. We preserve subject, description, status, priority, type, group, and agent assignment. Custom fields on Tickets migrate as typed Freshdesk custom fields. Conversation threads (public and private notes) migrate as Freshdesk Ticket conversations. The source ticket ID is preserved in a Freshdesk custom field for audit trail.

Freshservice Requesters map to Freshdesk Contacts. Both objects share the same schema core: name, email, phone, and organization. We match by email address as the dedupe key. If the Requester has an associated Organization in Freshservice, we map that to a Freshdesk Company record first so the Contact-to-Company lookup is satisfied at insert time.

Freshservice Agents map directly to Freshdesk Agents. Both platforms use the same Freshworks agent data model: name, email, role, group membership, and skill assignments. We resolve by email match. Agents without a matching Freshdesk account are held in a reconciliation queue for the customer's admin to provision before ticket reassignment proceeds.

Freshservice Assets (hardware, software, network items in the CMDB) have no direct Freshdesk equivalent. Freshdesk does not have an asset management or CMDB module. We discuss the customer's goal: if they need to preserve Asset records as reference data, we migrate them as Freshdesk Products with a custom field asset_type__c set to distinguish hardware, software, and network items. If asset management is a hard requirement post-migration, Freshservice or a dedicated ITAM platform remains the right destination.

Freshservice Changes (planned IT modifications with approval workflows and risk assessment) have no native Freshdesk equivalent. Freshdesk does not include a Change Management module. We can migrate Change records as Freshdesk Cases with custom fields capturing change_type, risk_level, approval_status, and affected_configuration_items, but the approval workflow itself cannot migrate. We document the change workflow for the customer's admin to rebuild in Freshdesk's Automation Rules.

Freshservice Problems (root-cause records tracking the underlying cause behind one or more Incidents) have no native Freshdesk equivalent. Freshdesk does not include a Problem Management module. We migrate Problem records as Freshdesk Cases with a custom field problem_id__c and link_status__c set to indicate the problem is a root-cause record. The linkage to related Incident records is preserved as a custom text field linking_ticket_ids__c rather than a native association.

Freshservice Releases group Changes and Assets into a deployable unit with a scheduled date and approval workflow. Freshdesk does not include a Release Management module. We migrate Release records as Freshdesk Cases with a custom field release_date__c and release_status__c. The approval workflow and associated Change linkages require manual rebuild in Freshdesk.

Freshservice Service Catalog items (multi-step request forms with approval chains) have no direct Freshdesk equivalent. Freshdesk's Solutions module is a knowledge-base system, not a service catalog. We migrate catalog item titles and descriptions as Freshdesk Solution articles categorized by original catalog item name, and document the full form logic and approval chain for the customer to rebuild using Freshdesk's custom apps or external form tooling.

Freshservice Custom Objects (Forest and Enterprise plans only) cannot define associations to native Freshservice objects. Freshdesk Custom Objects (Fortune and Enterprise plans only, in beta) similarly do not support associations to native objects. Both platforms share this limitation, which means a migration does not resolve the association gap — it carries it forward. We migrate Custom Object records as Freshdesk Custom Object records where the destination plan supports them, and flag the association limitation in the migration report.

Freshservice Solutions (knowledge-base articles that agents link to tickets) map directly to Freshdesk Solutions. We preserve article title, body, category, and section structure. The article-to-ticket linkage migrates as a Freshdesk Solution article attached to the corresponding ticket via Freshdesk's built-in knowledge-base-to-ticket linking.