Helpdesk migration
Field-level mapping, validation, and rollback between Sunrise ITSM and Zoho Desk. We move data and schema; workflows are rebuilt natively in Zoho Desk.
Sunrise ITSM
Source
Zoho Desk
Destination
Compatibility
11 of 12
objects map 1:1 between Sunrise ITSM and Zoho Desk.
Complexity
CModerate
Timeline
4-6 weeks
Overview
Moving from Sunrise ITSM to Zoho Desk addresses two consistent pain points: opaque pricing with gated advanced capabilities and a sparse integration ecosystem. Zoho Desk sits within the Zoho suite, giving service desks native connections to Zoho CRM, Analytics, and Creator for custom applications. The structural challenge on the Sunrise side is that no public bulk export API exists, requiring FlitStack AI to coordinate directly with Sunrise Software's professional services team to obtain structured data extracts. Custom module schemas are invisible to standard exports and must be requested explicitly before scoping. We handle that coordination, resolve attachment storage paths that reference internal file servers, and deliver tickets, agents, accounts, products, and knowledge base content into Zoho Desk using Zoho's REST API with department-aware field mapping. Workflows, automations, and approval chains do not migrate; we deliver a written inventory of every active Sunrise ITSM workflow for your admin to rebuild in Zoho Desk's Blueprint module.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Sunrise ITSM object lands in Zoho Desk, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Sunrise ITSM
Incident
Zoho Desk
Ticket
1:1Sunrise ITSM Incidents map directly to Zoho Desk Tickets. Priority, category, assignee, and SLA timer fields map to Zoho Desk's priority (Low/Medium/High/Urgent), status, assignee field, and SLA field respectively. Any organisation-level custom Incident properties are audited pre-migration and recreated as custom fields scoped to the relevant Zoho Desk department before import. Incident number becomes a read-only external reference field on the ticket.
Sunrise ITSM
Service Request
Zoho Desk
Ticket
1:1Service Requests carry requestor information, fulfiller assignment, and approval chain history. We preserve request lineage by mapping the requestor to Zoho Desk's Contact, the fulfiller to the Agent, and the approval history as a thread note with timestamps. Any linked knowledge article references are carried forward as internal notes on the ticket for the agent's context.
Sunrise ITSM
Change
Zoho Desk
Ticket
1:1Change records include risk level, approval status, and related Incident associations. We map these to Zoho Desk Tickets with a custom field change_type__c (Normal, Standard, Emergency), risk_level__c, and a related ticket reference linking back to related Incident tickets. The Change calendar linkage is preserved as a planned_start__c and planned_end__c custom date field.
Sunrise ITSM
Asset (CI)
Zoho Desk
Product
1:1Sunrise ITSM Configuration Items with relationships to Incidents and Changes map to Zoho Desk Products. Where custom CI types exist (Server, Network Device, Software License, etc.), we map them field-by-field to Zoho Desk Product fields plus custom fields for CI-specific properties like serial number, purchase date, and warranty expiry. CI relationships to Incidents are preserved as internal notes on the linked Product record.
Sunrise ITSM
Users and Agents
Zoho Desk
Agent
1:1Sunrise ITSM User and Agent records map to Zoho Desk Agents. Contact details, role assignments, and team memberships are mapped to Zoho Desk Agent fields with department assignments matching the Sunrise team structure. Active Directory synchronisation identities are preserved in a custom field for SSO continuity if Zoho Desk's SAML-based SSO is configured.
Sunrise ITSM
Teams
Zoho Desk
Department
1:1Sunrise ITSM Teams define agent group boundaries for routing and escalation. We map each Team to a Zoho Desk Department, preserving team membership order and escalation hierarchy as agent role assignments within the Department. Zoho Desk's department-based routing ensures tickets land with the correct group based on the Sunrise team assignment.
Sunrise ITSM
Knowledge Articles
Zoho Desk
Knowledge Base (Articles and Sections)
1:1Sunrise ITSM KB Articles with HTML body content are extracted from the custom-richtext format, restructured, and imported into Zoho Desk Knowledge Base as Articles within the relevant Sections. Article status (Draft, Published, Archived) maps to Zoho Desk's article status. Note that Knowledge Base attachments are excluded from Zoho Desk's migration intake; we attach them separately as file uploads linked to the article record.
Sunrise ITSM
Service Catalog Items
Zoho Desk
Products (service catalog representation)
lossySunrise ITSM Service Catalog items linked to workflows and approval matrices are migrated as Zoho Desk Products with a product_type__c = 'Service Catalog Item' custom field. Any broken workflow references from Sunrise are flagged in the handoff document for manual re-linkage to Zoho Desk Blueprint workflows. The catalog item description and pricing migrate as structured fields.
Sunrise ITSM
Training Courses
Zoho Desk
Custom Module or Products
1:1The ITBM Training module stores course outlines and costs. We map course definitions to a Zoho Desk custom training_courses module if the Professional or Enterprise tier is deployed, or to a custom field set on the Agent record for simpler scopes. Delegate attendance history migrates as records with effective dates carried forward as completion_date and expiry_date fields.
Sunrise ITSM
Skills and Certifications
Zoho Desk
Custom Module or Agent custom fields
1:1Skills linked to agents with effective-date semantics in Sunrise ITSM are flattened into a structured record: skill_name__c, proficiency_level__c, certified_date__c, and expiry_date__c. Expired certifications are flagged with a status indicator for customer review. If a custom Skills module is not feasible in the Zoho Desk tier, skills migrate as a multi-select picklist on the Agent record.
Sunrise ITSM
Custom Modules
Zoho Desk
Custom Fields and Modules
1:1Sunrise ITSM's 30+ configurable modules may include bespoke objects beyond standard ITSM records. We request the full live schema from Sunrise Software support before scoping, extract each custom module's field list, recreate the equivalent structure in Zoho Desk (as custom fields on the relevant standard object or as a separate custom module in Professional/Enterprise), and map records individually. Custom module data is the most common source of silent omission if schema pre-audit is skipped.
Sunrise ITSM
Attachments
Zoho Desk
Attachments (on Tickets, Contacts, Products)
1:1Sunrise ITSM attachments store file path references rather than inline binaries. We resolve each reference, retrieve the file from the source storage location, and re-attach to the equivalent Zoho Desk record. If the source file server is decommissioned before migration completes, attachments become unrecoverable; we flag this risk during discovery and recommend a freeze on server changes until migration cutover. Zoho Desk's 10GB upload limit per migration batch may require chunking for large attachment volumes.
| Sunrise ITSM | Zoho Desk | Compatibility | |
|---|---|---|---|
| Incident | Ticket1:1 | Fully supported | |
| Service Request | Ticket1:1 | Fully supported | |
| Change | Ticket1:1 | Fully supported | |
| Asset (CI) | Product1:1 | Fully supported | |
| Users and Agents | Agent1:1 | Fully supported | |
| Teams | Department1:1 | Fully supported | |
| Knowledge Articles | Knowledge Base (Articles and Sections)1:1 | Mapping required | |
| Service Catalog Items | Products (service catalog representation)lossy | Mapping required | |
| Training Courses | Custom Module or Products1:1 | Mapping required | |
| Skills and Certifications | Custom Module or Agent custom fields1:1 | Mapping required | |
| Custom Modules | Custom Fields and Modules1:1 | Mapping required | |
| Attachments | Attachments (on Tickets, Contacts, Products)1:1 | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Sunrise ITSM gotchas
Custom module schema is invisible to standard exports
No documented public API for bulk data extraction
Attachment storage paths reference internal file servers
ITBM training and skills module uses effective-date semantics
Zoho Desk gotchas
Agent email identity determines comment ownership after migration
Blueprints and SLA policies do not export via API
File upload capped at 10GB per migration batch
Tier-gated export and migration capabilities
Inbound migration is two-phase with a hard Phase 2 cutoff
Pair-specific challenges
Migration approach
Discovery and Sunrise Software vendor coordination
We audit the Sunrise ITSM instance across all active modules (Incident, Request, Change, Asset, Knowledge, ITBM, and any bespoke custom modules), record counts per object, attachment volume and storage locations, active workflow count and complexity, and agent/user headcount. Simultaneously, we initiate the Sunrise Software professional services coordination to request a bulk data extract. We cannot complete scoping without the schema export from Sunrise Software because custom module field lists are not accessible through any self-service export. Discovery output is a written migration scope document and a vendor coordination status update.
Schema audit and Zoho Desk pre-configuration
Once the Sunrise Software schema export is received, we audit every custom field across every active module. We pre-create the equivalent Zoho Desk structure: custom fields on Tickets, Contacts, Products, and Agents; custom modules for Training and Skills if Professional or Enterprise tier is deployed; Departments matching Sunrise team structure; and ticket field mappings for priority, status, and category. Custom field API names are matched to Sunrise ITSM field names for traceability. Zoho Desk pre-configuration happens in a sandbox or staging department before any production import begins.
Attachment retrieval and packaging
We resolve every Sunrise ITSM attachment reference against the source file storage. For attachments stored on internal network drives, we confirm access permissions and disk health with the customer's IT team. For attachments stored in Sunrise ITSM's managed storage, we use the provided extract to locate and retrieve binary data. We package each file with its parent record ID and target record type so that re-attachment in Zoho Desk is deterministic. If any source file servers are decommissioned or inaccessible, we flag them immediately and escalate to the customer for remediation before proceeding.
Zoho Desk sandbox import and reconciliation
We run a full import into a Zoho Desk sandbox environment (or a staging department in production) using representative data volume. The customer's service desk manager and admin reconcile record counts, spot-check twenty to thirty records against the Sunrise ITSM source for field accuracy, and validate that ticket threading, SLA timers, and agent assignments transferred correctly. Custom field mapping corrections, any Sunrise workflow logic that maps to Zoho Blueprint steps, and department assignment adjustments happen in this phase. No production import begins until the sandbox reconciliation is signed off.
Production migration in dependency order
We run production migration in record-dependency order: Agents (departments created first), Contacts and Accounts, Products (CIs and service catalog items), Tickets (Incidents, Service Requests, Changes with parent record IDs resolved), Knowledge Base articles, Training and Skills records, Custom Module data, and Attachments last. Each phase emits a row-count reconciliation report. Tickets are imported in Sunrise ITSM created_at order to preserve chronological threading where Zoho Desk supports it. Any ticket status that cannot map directly (for example, a Sunrise-specific status value not present in Zoho Desk's status list) is mapped to the nearest equivalent with a status_note__c field carrying the original value.
Cutover, delta migration, and workflow handoff
We freeze Sunrise ITSM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho Desk as the system of record. We deliver the Workflow Inventory document listing every active Sunrise ITSM workflow with its trigger conditions, steps, and recommended Zoho Desk Blueprint equivalent. We do not rebuild workflows as code inside the migration scope; that is a separate engagement for the customer's Zoho Desk admin or a Zoho implementation partner. We support a one-week hypercare window for reconciliation issues raised during the first week of live Zoho Desk operation.
Platform deep dives
Sunrise ITSM
Source
Strengths
Weaknesses
Zoho Desk
Destination
Strengths
Weaknesses
Complexity grading
Moderate Helpdesk migration. 4 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Sunrise ITSM and Zoho Desk.
Object compatibility
4 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Sunrise ITSM: Not publicly documented.
Data volume sensitivity
Sunrise ITSM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Sunrise ITSM to Zoho Desk migration scoping. Not seeing yours? Book a call.
Walk through your Sunrise ITSM to Zoho Desk migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Sunrise ITSM
Other ways to arrive at Zoho Desk
Same-Helpdesk migrations
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.