Migrate from Service Desk Panel to Zoho Desk

Service Desk Panel Tickets map directly to Zoho Desk Tickets. Subject, description, status, priority, and assignee migrate to the equivalent Zoho Desk fields. The source createdAt timestamp migrates to Zoho Desk's createdTime; we preserve this rather than setting it to migration date so that historical ticket ordering is accurate in Zoho Desk's timeline view. We resolve assignee by email match against the Zoho Desk agent records imported in the Agents phase.

Service Desk Panel Customer records map to Zoho Desk Account (organization) and Contact (individual). If the source Customer has a company name, we create an Account first and link the Contact to it via AccountId. If the source stores only individual contact details without an organization, we create a standalone Contact with no Account link. We match Contacts by email and flag duplicates for customer review.

Service Desk Panel Agents map to Zoho Desk Agents. We match by email as the dedupe key. Agents are imported before Tickets so that assignee and watcher references resolve at insert time. Any source Agent without a matching Zoho Desk user account goes to a reconciliation queue for the customer's admin to provision before Ticket import resumes.

Service Desk Panel team assignments map to Zoho Desk Departments. Zoho Desk's department-centric hierarchy uses Department records to determine which agents see which tickets and which layout applies. We map team names to Department names and assign the migrated agents to the corresponding department. If the source has nested teams, we flatten to a single department level or create a hierarchy per the customer's layout strategy.

Service Desk Panel conversation messages map to Zoho Desk Ticket Threads (chronological message entries) and Comments (internal notes). We preserve author attribution by resolving the source author email to the migrated Zoho Desk agent. Thread direction (incoming vs outgoing) migrates as is if the source exposes this flag, otherwise all replies default to customer-facing direction. HTML formatting is preserved where supported.

Service Desk Panel file attachments migrate as Zoho Desk Ticket Attachments. If the source platform exposes direct download URLs, we fetch and re-upload to Zoho Desk's attachment storage. If only file name and reference metadata are available without a downloadable URL, we flag this during scoping and provide a checklist for manual export. Zoho Desk enforces a 10GB total upload limit per migration; files exceeding this require customer handling.

Service Desk Panel tags migrate as Zoho Desk tags on the Ticket record. Tags are string arrays and map consistently. Note that Zoho's Zwitch tool does not migrate tags, but our API-led approach preserves them. Tag naming differences are carried forward as-is and the customer deduplicates or consolidates post-migration if needed.

Service Desk Panel custom ticket fields map to Zoho Desk custom fields by matching label and data type (text, dropdown, date, checkbox). We rely on the customer to confirm the correct destination field during the mapping review step before import. Zoho Desk Enterprise users with multiple departments may have department-scoped custom fields that require layout assignment; we coordinate with the customer's admin to ensure correct visibility settings.

SLA policy configuration is not portable across platforms. Each platform defines response and resolution time targets, business hours, and escalation rules differently. We document the source SLA policies during discovery (first response time, resolution time, business hours, priority mapping) so the customer can manually recreate them in Zoho Desk under Setup > SLA Policies before go-live. This must be completed before cutover to avoid SLA breaches from day one.

Service Desk Panel knowledge base articles migrate to Zoho Desk Help Center articles with title, body, category, and section preserved. Formatting differences between platforms may require post-migration review of article layout and link behavior. Knowledge base attachments do not migrate via Zoho Desk's Zwitch tool; our API-led approach attempts to re-link attachments where accessible URLs are available, but attachments without downloadable links must be handled manually by the customer.

Automated rules, ticket routing logic, trigger actions, and macro conditions are platform-specific and not stored in a portable format. We list all active Service Desk Panel automations during discovery and include a rebuild guide in the migration package mapping each rule to the equivalent Zoho Desk Blueprint stages and actions. The customer must plan time to reconfigure these after go-live. Blueprint is available from the Professional tier ($23/agent/mo) and above.

Analytics and reporting configurations are not portable across platforms. Historical ticket metrics may be available as raw data for reimport into Zoho Analytics or a BI tool. We deliver a written inventory of all Service Desk Panel reports with their filters, groupings, and chart types so the customer's admin can rebuild equivalent Zoho Analytics dashboards post-migration. There is no 2-year reporting time cap on any Zoho Desk paid plan.