Migrate from Watermelon to Zendesk

Watermelon Contact records map to Zendesk End Users (the requester role). We map name, email, phone, and all custom fields to equivalent Zendesk user fields or custom user fields. The Zendesk user serves as the requester on all migrated Tickets. Agent users (support team members) are a separate provisioning step mapped from Watermelon Owner records.

Watermelon Owner records (the agents managing conversations) map to Zendesk Agent users. We extract owners by email from Contacts, Conversations, and Messages and provision them as Zendesk Users with the Agent role. Active versus inactive status is preserved. Owners without a matching Zendesk user are held in a reconciliation queue for the admin to provision before record import.

Each Watermelon Conversation maps to a Zendesk Ticket. The Watermelon channel (WhatsApp, Instagram, Facebook, or web chat) becomes a Ticket field or tag we create during migration. Conversation status (open, resolved, archived) maps to Zendesk Ticket status (Open, Pending, Solved, Closed). The original Watermelon Conversation ID is stored in a custom field wm_conversation_id__c for cross-reference.

Watermelon Messages within a Conversation map to Zendesk Ticket Comments. Each comment carries sender type (agent, bot, customer), content, timestamp, and channel metadata. We preserve the chronological message sequence within each Ticket to maintain conversational context. Bot-generated messages are included as public or internal comments depending on the source visibility setting.

If Watermelon Contacts include company-level data (either as a custom field or a linked field), we map these to Zendesk Organizations. Organization provides shared context across multiple End Users and allows ticket grouping by company. We use the company name or domain as the Zendesk Organization name.

Watermelon Tags applied to Contacts and Conversations migrate to Zendesk Tags on the corresponding User and Ticket records. Tags used for categorization and routing in Watermelon map directly. We preserve the full tag vocabulary and note which tags were applied to which record type for the Zendesk admin to apply to triggers or views post-migration.

Watermelon Notes attached to Contacts migrate as internal Zendesk Ticket Comments on the most recent related Ticket for that Contact. If no Ticket exists for the Contact, we flag the orphaned note for the admin to review and attach manually. Internal note visibility is preserved as private agent comments.

Contact-level custom fields are discovered during scoping, typed (text, number, date, dropdown, checkbox), and mapped to equivalent Zendesk custom user fields and custom ticket fields. Zendesk custom field IDs from the destination account are required before migration so that the import payload uses the correct field references. Field-level validation rules in Zendesk are temporarily disabled during import to prevent rejection of legacy data.

Watermelon channel configurations (WhatsApp Business API, Facebook page, Instagram business account, live chat widget) are OAuth-based credentials scoped to the Watermelon installation. These cannot be transferred. We inventory every active channel, record the associated business account identifiers, and provide step-by-step reconnection instructions for configuring equivalent channels in Zendesk Admin Center. The customer must have admin access to the relevant Meta Business and WhatsApp Business accounts.

Watermelon Flow automations define routing, triggered actions, and AI Response logic inside the platform. The API does not expose flow configurations, so we cannot migrate them automatically. We document every active Watermelon Flow with its trigger conditions, actions, and channel scope, and deliver this as a written inventory for the Zendesk admin to rebuild as Triggers, Automations, and Macros in Zendesk Admin Center. The rebuild is outside standard migration scope.

Watermelon webhook endpoint URLs and event types (new contact, message received) are exported as a configuration document. Re-registration in Zendesk requires the customer to configure new webhook targets in Zendesk Admin Center pointing to the same external systems. We flag any webhook payloads that reference Watermelon-specific field names requiring replacement with Zendesk equivalents.

Watermelon aggregate analytics including resolution rates, conversation volume, and agent performance are exported from the dashboard where accessible. We map key Watermelon metrics to equivalent Zendesk Explore datasets (Tickets solved, first response time, CSAT) and provide a reporting gap analysis document identifying metrics that cannot be directly reproduced in Zendesk without custom Explore reports.