Migrate from Sugar Serve to Zoho Desk

Sugar Serve Cases map to Zoho Desk Tickets. The Case number becomes Ticket Number; status, priority, and type map to Zoho Desk standard picklist fields. We preserve the case-to-account linkage by resolving the Account record first, then setting the AccountId on the Ticket during import. The case description and internal notes map to Ticket Description and Private Comments respectively. If the source Cases include portal-visible records gated by an Enterprise license, we flag the ticket status flags that require a Zoho Desk customer portal configuration post-migration.

Sugar Serve Accounts map directly to Zoho Desk Accounts. The Account name, phone, website, industry, and address fields translate 1:1. The service_level field on Sugar Serve Accounts (capturing contractual SLA tier) maps to a Zoho Desk custom Account field that we create before migration. We handle the parent-account hierarchy where it exists by mapping the parent_id to Zoho Desk's Parent Account lookup.

Sugar Serve Contacts map to Zoho Desk Contacts with the contact-to-account relationship preserved via the Account lookup. We map first name, last name, email, phone, mobile, title, and address fields. Custom Contact fields created in Sugar Serve Studio migrate to Zoho Desk custom Contact fields scoped to the relevant department. We resolve the account relationship at import time using the external account ID.

Sugar Serve Leads map to Zoho Desk Leads. Lead status, source, and score fields from Sugar Serve migrate as custom fields in Zoho Desk. We note that Zoho Desk's Lead-to-Contact conversion workflow is available post-migration for the customer's admin to configure based on their sales process. Custom Lead fields created in Sugar Serve Studio require pre-creation in Zoho Desk before import.

Sugar Serve Studio custom modules have independent database tables with unique field schemas. We perform field-level discovery during scoping, extract all active custom module definitions, and generate a custom field mapping table for each module. Any lookup fields pointing to Cases, Accounts, or Contacts require cross-object ID resolution during migration. We pre-create Zoho Desk custom fields for each source custom module before any data import begins, ensuring field type compatibility (picklist, string, integer, currency, checkbox).

Sugar Serve file attachments are extracted from the Sugar file repository referenced by CRM records. We extract attachment references, download the files, and re-import them to Zoho Desk linked to the corresponding Ticket or Contact. File type and original filename are preserved. Zoho Desk enforces department-level storage limits that we confirm during scoping to ensure the attachment volume fits within the target plan.

Sugar Serve Notes attached to Cases, Accounts, and Contacts map to Zoho Desk Comments on the corresponding Ticket or Contact record. Note body and creation timestamp migrate, with the note's related module preserved as a reference during import. Private Notes in Sugar Serve map to Zoho Desk Private Comments.

SugarBPM workflow definitions are configuration metadata, not data records, and do not migrate as executable code. We export the SugarBPM package and deliver a written workflow inventory specifying the trigger conditions (record save, field update), branching logic, email alerts, and field update actions for each active workflow. The customer's Zoho Desk admin uses this inventory to rebuild the equivalent process in Blueprint (process flows) and Macros (ticket actions). Workflows are ranked by business criticality during scoping.

Sugar Serve Bug records track product defects linked to Cases. We migrate Bug records as Tickets in Zoho Desk with a Bug source category flag set via a custom picklist field. The Bug-to-Case linkage does not have a direct Zoho Desk equivalent, so we set a custom field bug_case_id__c carrying the original Sugar Serve Case ID for cross-reference.

Sugar Serve Projects with milestone tasks and dates migrate to Zoho Desk Tasks linked to the corresponding Ticket or Contact. Project resource assignments map to Zoho Desk Agent lookups, but resource capacity and project-level scheduling do not transfer as structured project management records. We flag the Project records requiring rebuild in Zoho Projects as a post-migration planning item.

The service_level field on Sugar Serve Accounts captures contractual SLA tier (Tier 1, Tier 2, etc.) used for case routing and SLA enforcement. We create a matching custom field in Zoho Desk Accounts before migration and populate it from the source service_level values. Zoho Desk's native SLA module operates at the department level and does not read from Account custom fields; the custom field provides the reference data for the customer's admin to configure department-level SLA rules post-migration.

Portal-visible Cases in Sugar Serve are gated by the Enterprise license and carry portal-specific status flags. We migrate these Cases as standard Tickets and flag any portal-facing status values requiring Zoho Desk customer portal configuration. Zoho Desk's customer portal is included from the Standard tier ($20/user/mo), so the portal feature itself may be unlocked post-migration if the source Sugar Serve Enterprise license was the gating factor.