Migrate from Watermelon to Freshdesk

Watermelon Contact records (name, email, phone, and all custom fields) map directly to Freshdesk Contact. We extract every custom Contact field during scoping, map each to an equivalent Freshdesk custom contact field, and flag any Watermelon custom fields that have no direct Freshdesk type equivalent. Contact-to-Contact mapping preserves the Watermelon contact_id as a reference field for post-migration audit and reconciliation.

Each Watermelon Conversation becomes one Freshdesk Ticket with a Conversation record for each message. The first customer message in the Watermelon thread becomes the Ticket description in Freshdesk; all subsequent messages (customer and agent) become Freshdesk Conversation entries with direction, sender type, and timestamp preserved. We extract the original Watermelon channel from the message payload and set it as a custom ticket field or ticket source mapping.

Individual Watermelon messages (sender type, content, timestamp, channel metadata) map as Freshdesk Conversation entries within the parent Ticket. Message direction maps to Freshdesk Conversation direction (inbound/outbound), and sender type maps to agent or customer. Timestamps are preserved using Freshdesk's created_at field on the Conversation object. Note that Freshdesk does not support multi-channel message threading natively; we embed channel attribution in the message body as a prefix for cross-channel conversations that spanned multiple channels.

Watermelon Tags applied to Contacts and Conversations are extracted as arrays on each parent record. We map Watermelon Tags to Freshdesk Tags and apply them to the migrated Contact and Ticket records. If the customer used Tags for routing or categorization logic, we document the tag-to-queue assignment for manual reconstruction in Freshdesk.

Watermelon Contact-level custom fields are exposed via API with per-account schema variation. We discover all custom fields during scoping, map each to a Freshdesk custom contact field of equivalent type (text, number, date, dropdown, checkbox), and flag any fields requiring transformation or truncation before import. Custom field ordering and grouping are documented for Freshdesk admin to configure post-migration.

Watermelon Notes attached to Contacts (free-text commentary) migrate to Freshdesk Contact Notes. We preserve note content and created_at timestamp. Note visibility in Watermelon (agent-only vs shared) maps to Freshdesk's internal note behavior by default.

Watermelon flow builder configurations (routing, triggered actions, conditional branches) are not accessible via the Watermelon API and cannot be exported. We do not migrate Flow Automations as code. We deliver a written inventory of every active Watermelon Flow with its trigger conditions, actions, and recommended Freshdesk Workflow or Scenario Automation equivalent. The customer's Freshdesk admin rebuilds them manually post-migration.

Watermelon AI Actions and model finetuning settings control bot behavior and are stored server-side without API access. Freshdesk's equivalent AI features (Freddy Copilot, Custom Bots) use a different configuration model. We document the customer's current AI Actions scope and intent so the admin can evaluate Freshdesk's AI feature set and configure equivalent behavior post-migration.

Watermelon webhook endpoint URLs and event types can be exported, but re-registering them in Freshdesk requires manual configuration. Freshdesk webhooks are configured under Admin > Workflows > Custom Functions > Webhooks and point to the same external listener endpoints. We export the complete webhook inventory and provide step-by-step Freshdesk reconfiguration instructions for each endpoint and event type.

WhatsApp Business, Meta (Facebook/Instagram), and live chat integrations use OAuth credentials scoped to the Watermelon installation. These cannot be transferred. We inventory every active Watermelon channel and document the associated business accounts (Meta Business, WhatsApp Business) that need reconnection. Freshdesk channel setup (Admin > Channels) requires admin access to those business accounts and follows Freshdesk's own OAuth flow for each channel.