DMT
ClonePartner Helpdesk Migration Planner
Step 1

Export From

Capabilities (12)
  • Tickets & Conversations
    • Core support records including status, priority, comments, and file attachments.
  • Users (Agents & Customers)
    • Profiles for both Support Agents and End-Users (Customers).
  • Organizations
    • Company profiles that group multiple users together.
  • Groups / Teams
    • Agent teams or departments (e.g., "Sales", "Support").
  • Knowledge Base
    • Public or private help center documentation and categories.
  • Macros / Canned Responses
    • Pre-written responses used by agents to reply quickly.
  • Triggers
    • "If-This-Then-That" rules that run immediately on ticket updates.
  • Automations
    • Time-based rules (e.g., "Close ticket after 4 days of inactivity").
  • Tags
    • Labels attached to tickets for categorization and reporting.
  • Custom Fields
    • Non-standard data fields added to tickets or user profiles.
  • Ticket Forms
    • Different ticket layouts presented to customers based on request type.
  • SLA Policies
    • Service Level Agreement rules defining response/resolution deadlines.
Step 2

Import To

Capabilities (7)
  • Tickets & Conversations
    • Core support records including status, priority, comments, and file attachments.
  • Users (Agents & Customers)
    • Profiles for both Support Agents and End-Users (Customers).
  • Organizations
    • Company profiles that group multiple users together.
  • Groups / Teams
    • Agent teams or departments (e.g., "Sales", "Support").
  • Knowledge Base
    • Public or private help center documentation and categories.
  • Tags
    • Labels attached to tickets for categorization and reporting.
  • Custom Fields
    • Non-standard data fields added to tickets or user profiles.

Migration Analysis

We analyzed the API capabilities of both Zendesk Support and Freshdesk.

Automated
API to API
Manual
API Gap
Scope Summary
Compatible Items7
Incompatible Items5
Step 3

Select Scope & Volume

Tickets & Conversations
Core support records including status, priority, comments, and file attachments.
API Compatible
Users (Agents & Customers)
Profiles for both Support Agents and End-Users (Customers).
API Compatible
Organizations
Company profiles that group multiple users together.
API Compatible
Groups / Teams
Agent teams or departments (e.g., "Sales", "Support").
API Compatible
Knowledge Base
Public or private help center documentation and categories.
API Compatible
Macros / Canned Responses
Pre-written responses used by agents to reply quickly.
Destination (Freshdesk) missing Import API
Triggers
"If-This-Then-That" rules that run immediately on ticket updates.
Destination (Freshdesk) missing Import API
Automations
Time-based rules (e.g., "Close ticket after 4 days of inactivity").
Destination (Freshdesk) missing Import API
Tags
Labels attached to tickets for categorization and reporting.
API Compatible
Custom Fields
Non-standard data fields added to tickets or user profiles.
API Compatible
Ticket Forms
Different ticket layouts presented to customers based on request type.
Destination (Freshdesk) missing Import API
SLA Policies
Service Level Agreement rules defining response/resolution deadlines.
Destination (Freshdesk) missing Import API