Migrate from CommBox to Zoho Desk

CommBox Conversations map to Zoho Desk Tickets. Each conversation thread becomes a single ticket with all messages from WhatsApp, email, voice, and social channels preserved as Thread Comments in chronological order. Channel origin is tagged via a Zoho Desk custom field (original_channel__c) using values from CommBox's channel source metadata so agents can filter by omnichannel origin in Zoho Desk views.

CommBox Customer records map to Zoho Desk Contacts. We extract name, email, phone, and any custom properties stored on the customer profile card and map them to the corresponding Zoho Desk Contact fields. Custom properties become either Zoho Desk standard fields (if type matches) or custom fields scoped to the relevant Zoho Desk department.

CommBox organization-level records attached to Customers map to Zoho Desk Accounts. Account name, website, industry, phone, and address fields migrate directly. If CommBox customers are not linked to a company record, they import as standalone Contacts without an Account association.

CommBox Agent profiles map to Zoho Desk Agent records matched by email address. We export agent name, email, team assignment, and role. Zoho Desk requires agents to accept invitations before accessing tickets; we handle the invitation acceptance workflow as part of provisioning. Deactivated CommBox agents cannot transfer; they are excluded from the migration export.

CommBox Teams map to Zoho Desk Departments. Zoho Desk enforces a department-centric hierarchy where every ticket belongs to a department; teams in CommBox become departments or sub-departments depending on nesting depth. We capture team membership during discovery and assign agents to the corresponding Zoho Desk department during migration. Migration Wizard cannot transfer teams automatically; we configure departments manually before ticket import so the department reference is satisfied at insert time.

CommBox conversation tags cannot migrate via Zoho Desk's native migration tool, which explicitly drops tags, groups, teams, and collaborators. We map CommBox tags to Zoho Desk multi-select picklist custom fields on the Ticket object. The customer chooses the destination field during scoping. Tags used for content categorization also become Ticket custom fields rather than a separate tagging system.

File attachments embedded in CommBox conversations are extracted via the media API and re-associated with the parent Zoho Desk Ticket record. We handle both inline image attachments and standard file uploads. Inline images embedded in HTML ticket bodies do not migrate automatically; we document each affected ticket and recommend re-uploading post-migration or retaining CommBox access for reference.

CommBox Commsite knowledge base articles map to Zoho Desk Knowledge Base articles. We export article title, body content, categories, and publish status. Article structure and media embeds may require post-migration formatting adjustments depending on the richness of the original HTML content. KB categories map to Zoho Desk category and section hierarchy.

CommBox SLA configurations define response and resolution timers per channel or team. We export SLA definitions as structured metadata including timer duration, business hours reference, and escalation thresholds. Zoho Desk SLA policies are recreated by the destination admin using the exported configuration; SLA policy transfer is a manual-rebuild step rather than an automated data import because SLA association with tickets requires department-level configuration in Zoho Desk.

AssignX routing rules govern conversation-to-agent assignment in CommBox but have no exportable format. We document every active routing rule during discovery as a Configuration Inventory including trigger conditions, agent/team targets, priority settings, and business hours dependencies. The inventory is delivered as a Zoho Desk rebuild guide with corresponding Zoho Desk Assignment Rule and Macro equivalents for each CommBox rule. Routing rules are not migrated as executable code; the rebuild is a post-migration admin task.

CommBox's proprietary automation scripts (AutoX, IntentX, AssignX, TransformX) do not export to standard data formats and have no Zoho Desk equivalent. We document every script trigger, condition, action, and delay during scoping as an Automation Logic Inventory. This document is the rebuild blueprint; the customer's Zoho Desk admin or a Zoho partner recreates equivalent Blueprint flows and Macros post-migration. This is not a data-migration gap; it is a process-migration task scoped separately.

CommBox channel metadata (WhatsApp, email, voice, chat, social) is preserved as a custom field original_channel__c on Zoho Desk Tickets rather than as a separate object. This ensures the omnichannel context of each ticket is visible to agents in Zoho Desk without requiring a custom integration to surface channel source. Channel assignment for new tickets is handled through Zoho Desk's channel integration setup post-migration.