Migrate from Watermelon to Zoho Desk

Watermelon Contact records (name, email, phone, and all custom fields) map directly to Zoho Desk Contacts. The Zoho Desk Contact schema includes First Name, Last Name, Email, Phone, Mobile, Street, City, State, Country, Zip, Facebook, Twitter, and Description fields. We discover all Watermelon custom fields during scoping, map each to a Zoho Desk custom field (created per department), and flag any field type mismatches (date vs string, multi-select vs single-select) before import. The ContactExtId maps from Watermelon's contact ID for dedupe and cross-reference.

Each Watermelon Conversation becomes a Zoho Desk Ticket. The Watermelon conversation channel (WhatsApp, Instagram, Facebook, web chat) maps to the Ticket's Channel field in Zoho Desk. Conversation subject and first customer message typically form the Ticket Subject and Description. The conversation open/close status from Watermelon maps to Zoho Desk Ticket Status (Open, Pending, On Hold, Closed). We set the original conversation creation timestamp as Ticket Created Time where Zoho's API accepts it; Zoho Desk native imports accept Created Time in YYYY-MM-DDTHH:MM:SS.000Z format.

Watermelon message sequences map to Zoho Desk Ticket Comments (public agent and customer replies) and Ticket Threads (internal notes). The sender type (agent, bot, customer) from Watermelon determines whether we write to Comment or Thread in Zoho Desk. We preserve the full message timestamp and content for each entry. Note that Zoho Desk's Zwitch migration tool does not migrate Comment Author as Contact or Agent in all cases; we use the Zoho Desk REST API to write author references correctly rather than relying on Zwitch CSV import for message content.

Watermelon Tags applied to Contacts and Conversations map to Zoho Desk Tags. Tags are a flat label system in both platforms. We extract the full tag set from Watermelon during scoping, map each tag to a Zoho Desk Tag with identical or equivalent name, and apply tags to the corresponding Contact and Ticket records at import time. Tag migration is configuration rather than a data transform step.

Watermelon Channels (WhatsApp Business, Facebook, Instagram, live chat, email) are OAuth-based integrations that cannot be transferred to Zoho Desk as credentials. We inventory every active Watermelon channel, record the associated business account identifiers, and provide step-by-step reconnection instructions for each channel in Zoho Desk's Channels module. The customer must have admin access to the relevant Meta Business and WhatsApp Business accounts to complete re-authentication. We do not migrate channel credentials as data.

Watermelon Flow automations define routing and triggered actions that have no export path via the API. We document every active Watermelon Flow (trigger conditions, actions, delay logic) in a structured inventory delivered to the customer. Zoho Desk Blueprint and Workflow Rules serve as the functional equivalents for ticket routing, auto-assignment, and SLA escalation. The customer's Zoho Desk admin rebuilds each flow using the FlitStack AI inventory as a specification. This is manual work outside the data migration scope.

Watermelon AI Actions and model Finetuning settings are platform-specific configurations controlling bot response behavior. The API exposes no export path for these settings. Zoho Desk's Zia AI provides conversation intelligence and automation capabilities at the Professional tier. We document the Watermelon AI configuration scope (topics covered, finetuning source documents, action triggers) for the customer's Zoho Desk admin to reproduce in Zia AI configuration. AI tuning is outside the data migration scope.

Watermelon Webhooks (registered subscriptions on contact creation, message receipt, and other events) export as endpoint URLs and event type lists. We inventory every active Watermelon webhook URL, the event types subscribed, and any shared secret or header authentication. Re-registration of webhooks in Zoho Desk is a manual configuration step that the customer's admin performs using the exported inventory. Zoho Desk webhook registration is available via the Zoho Desk API at the extension or custom function level.

Watermelon aggregate analytics (resolution rates, conversation volume, agent performance) export from the Watermelon dashboard where accessible. We extract summary statistics and key metric definitions. Zoho Desk's Reports module provides equivalent analytics but requires manual configuration of dashboards and report types. We deliver a metric mapping table (Watermelon metric to Zoho Desk equivalent report field) so the customer's admin can rebuild dashboards in Zoho Analytics or Zoho Desk's native reporting.

Watermelon Notes attached to Contacts (free-text commentary) migrate to Zoho Desk Contact Description fields or as internal Ticket Threads if attached to a specific conversation. We identify all Notes during scoping, determine the target field in Zoho Desk based on the note's parent record type, and include the note content in the appropriate import phase.

Watermelon Contact-level custom fields vary by account and are exposed via API. Zoho Desk custom fields are scoped to specific departments and modules. We discover all Watermelon custom fields during scoping, create equivalent Zoho Desk custom fields in the relevant department, and map field types (string, integer, checkbox, picklist) during the import transform. Custom field creation in Zoho Desk requires Support Administrator permissions.

Watermelon does not expose a separate Agent object; agent identity is implicit in conversation assignments and message authorship. We extract distinct agent identities from Watermelon Conversations and map them to Zoho Desk Agents by email match. Zoho Desk Agents require provisioning in the destination portal before Ticket import can reference them. The customer provides the Zoho Desk agent list during scoping, and we reconcile any unmatched Watermelon agents to a queue for manual provisioning.