Migrate from SympoQ to Zoho Desk

SympoQ Tickets map to Zoho Desk Tickets with status, priority, assignee, queue, custom fields, and attachment references transferred. Each SympoQ ticket thread (email messages stored as conversation entries) maps to Zoho Desk Ticket Threads and Ticket Comments. The mapping preserves the chronological ordering of entries by timestamp. Note that Zoho Desk migration tools cannot sort tickets by date by default; we handle ordering through timestamp metadata embedded in the comment body if chronological accuracy is required. CC users on SympoQ tickets do not migrate to Zoho Desk as CC users; we embed their email addresses in a custom field for manual follow-up.

SympoQ Agents map to Zoho Desk Agents. The mapping uses email as the dedupe key: if a Zoho Desk Agent with the matching email already exists, the system maps to the existing record. If not, we create the Agent during migration. The migration order enforces Agents first (Zoho Desk's Zwitch requires this sequencing to satisfy Ticket assignee lookups). Deactivated SympoQ agents cannot migrate; we flag these in the scoping report for the customer's admin to provision manually before migration begins. Role mapping: SympoQ Admin maps to Zoho Desk Support Administrator; SympoQ Agent maps to Zoho Desk Agent.

SympoQ Customers map to Zoho Desk Contacts. The mapping includes name, email, phone, and custom fields. On SympoQ Premium accounts, bulk customer import is available; on Team and Concept tiers, customers must be added individually. Zoho Desk's assisted migration file format requires agentExtId (external ID) and Last Name as required fields, with Email as a required field. We map SympoQ customer email to Zoho Desk Contact Email and generate the external ID from SympoQ's internal customer ID.

SympoQ's Queue architecture (shared queues scoped to departments) maps to Zoho Desk Accounts, with the queue name becoming the Account Name. If a SympoQ account has multiple departments represented as separate queues, each queue becomes a distinct Zoho Desk Account. This preserves the department-level scoping that SympoQ provides through its queue architecture. Zoho Desk's Accounts file format requires accountExtId (required) and Account Name (required), with optional fields for phone, email, website, industry, and address.

SympoQ Custom Submission Forms define field labels, optional/mandatory status, and ordering. These map to Zoho Desk Ticket Layouts under Setup > Customization > Layouts and Fields. We map form field definitions and mandatory status to Zoho Desk field-level requirements, but form layout and conditional logic (e.g., show field X when field Y is populated) do not migrate and require manual rebuild in Zoho Desk's layout designer. The customer's admin receives a field-by-field inventory of every SympoQ form with its Zoho Desk layout equivalent.

SympoQ Knowledgebase Articles export to CSV with titles, categories, and metadata, but the article body may export as plain text stripped of HTML formatting. We inspect the exported CSV during data profiling and flag articles where formatting loss is material. Articles are mapped into Zoho Desk KB Sections and Categories, preserving the category hierarchy. Articles flagged for formatting impact are noted in the scoping report for manual post-migration review or alternative screen-scrape export if HTML fidelity is required. Zoho Desk does not migrate KB article attachments; these are documented separately for manual re-embedding.

SympoQ Workflow Rules automate processing and assignment logic. We map rule triggers, conditions, and actions from the Settings API and deliver a written inventory of every active rule with its SympoQ configuration details. Zoho Desk does not import SympoQ Workflow Rules; the equivalent Zoho Desk constructs are Blueprints (process enforcement) and Macros (canned responses with variable substitution). We do not rebuild them as code. The inventory document includes recommended Zoho Desk Blueprint or Macro equivalents for each SympoQ rule so the customer's admin can rebuild.

SympoQ Email Templates are stored in the Settings API with template names, subject lines, body content, and variable placeholders. We export this data and map template names, subjects, and body text. Rich formatting and conditional logic may not transfer cleanly; we document any template with non-transferable formatting for manual rebuild in Zoho Desk's template editor. Variable placeholders are noted with their SympoQ syntax for the customer's admin to convert to Zoho Desk's {FIELD_NAME} syntax.

SympoQ's embedded web widget provides a customer-facing submission portal with domain mapping and blank-label options. We export the widget configuration (domain mapping, label text, active/inactive status) from SympoQ Settings. Zoho Desk's equivalent is a Web Form embedded in a Customer Portal or the Help Center. The widget configuration does not migrate; we deliver a written map of the current SympoQ widget settings so the customer's admin can configure the equivalent Zoho Desk Web Form and Customer Portal post-migration.

SympoQ analytic reports, ticket summaries, and billable time records are generated on demand and are not accessible via API. Historical report data cannot be migrated programmatically. We document the reports and dashboards active in SympoQ during scoping so the customer's admin can rebuild them in Zoho Desk's Reports module. Zoho Desk's reporting engine supports ticket volume, response time, CSAT, and agent performance dashboards.

SympoQ custom update fields on Tickets map to Zoho Desk custom fields on the Ticket module. We define custom field types (text, picklist, number, date, checkbox) during scoping and pre-create them in Zoho Desk under Setup > Customization > Layouts and Fields before any Ticket import begins. Custom field values migrate as string data; Zoho Desk validates picklist values against its whitelist, so we flag any SympoQ picklist values that are not in the Zoho Desk picklist definition.

SympoQ ticket attachments are referenced by URL in the API response. We resolve these URLs during migration and download the attachment content, then upload to Zoho Desk linked to the corresponding Ticket. Inline images embedded in ticket threads do not migrate to Zoho Desk; Zoho's own Zwitch documentation confirms that inline images are not supported in migration. We flag inline image usage in the scoping report and recommend re-attaching the most critical images manually post-migration.