Migrate from ChannelReply to Zoho Desk

ChannelReply maps every incoming marketplace message into a helpdesk ticket. The ticket inherits the message body, agent replies, and ChannelReply's threading logic. We export the full ticket record including status, priority, assignee, created date, and last modified date, and map them directly to Zoho Desk Ticket. Ticket Threads (agent and customer messages) migrate as Zoho Desk Thread entries. We preserve message timestamps for activity timeline ordering.

Individual messages from Amazon MWS/SP-API, eBay, Walmart, Etsy, Back Market, Newegg, and WooCommerce are the atomic unit ChannelReply delivers. Each message maps to a Zoho Desk Thread entry with the original message body, sender type (customer or agent), and timestamp. Shopify messages arriving via email are captured as standard email-to-ticket Thread entries with the original email headers and body preserved. Thread ordering is preserved by thread sequence position.

ChannelReply pushes order-level data into helpdesk custom fields: Item Title, Order ID, Order Status, Order Total, Customer Name, Shipping Address, Buyer Location, SKU, Shipping Fee, Payment Method, and Channel Name. We export these as structured field values and create equivalent custom fields in Zoho Desk using the Custom Field module under Setup. Field types are mapped: text fields for Item Title and SKU, numeric for Order Total and Shipping Fee, date for order date, picklist for Order Status and Payment Method, and multi-line text for Shipping Address.

ChannelReply applies marketplace-specific tags to tickets indicating channel source (Amazon, eBay, Walmart, Etsy, Shopify, Back Market, Newegg, WooCommerce). We export these tags and create equivalent Zoho Desk tags during migration. Tags used for channel attribution map directly. If the customer uses custom ChannelReply tags for internal routing or priority, we remap them to Zoho Desk tags with a naming convention the customer's admin approves during scoping.

ChannelReply enriches tickets with buyer details sourced from marketplace APIs: buyer name, email, shipping address, buyer location, and payment method. We parse these values from the exported ticket custom fields and create Zoho Desk Contacts for buyers who do not already exist, linking them to the migrated Ticket. If the customer maintains company-level data (B2B ecommerce accounts), we create Zoho Desk Accounts and link Contacts to them. Duplicate Contact detection uses email as the primary dedupe key.

Each connected marketplace account (Amazon seller account, eBay account, Walmart account, Etsy shop, Shopify store, Back Market account, Newegg account, WooCommerce store) is a ChannelReply configuration unit. We export account-level settings and notification preferences as a structured reference document. The marketplace API credentials themselves cannot be exported from ChannelReply. We deliver a reconnection permission checklist specifying exactly which permissions (SP-API operations, OAuth scopes, API keys) each marketplace requires for Zoho Desk's native channel or partner connector, and the customer's admin completes re-authentication post-migration.

ChannelReply distinguishes customer messages from system notifications (Amazon shipment updates, eBay order confirmations, Walmart tracking pings). System notification settings (enabled or disabled per marketplace) are exported as a configuration reference. Notification counts are preserved in Zoho Desk's ticket event log as informational entries if the customer wants to audit the original notification activity. We flag which system notifications counted toward ChannelReply's message limit so the customer can evaluate whether to re-enable them in Zoho Desk's notification rules.

ChannelReply stores per-marketplace and per-account agent signatures used when sending replies through ChannelReply's action panel. These are exported as plain-text configuration data. Zoho Desk uses Macros for automated reply templates, not per-marketplace signatures. We deliver the exported signature data as a Zoho Desk Macro content document so the customer's admin can incorporate the text into appropriate Macros or email templates. This is a manual configuration step outside the automated migration scope.

ChannelReply enables in-ticket actions: Amazon Mark as No Response, eBay Resolution Center cases, Etsy shipping uploads, cancellations, and refunds. These action logs are recorded in the ChannelReply ticket history. We export the action log as a text attachment or comment entry on the Zoho Desk Ticket, preserving the action type, timestamp, and agent who performed it. We do not execute refund or cancellation actions during migration; those require manual re-execution in the destination platform post-cutover.

ChannelReply itself has no separate user directory; it relies on the connected helpdesk for agent identity. Agent assignments and activity logs are sourced from the connected helpdesk export. We export agent email addresses, names, and roles from the source helpdesk and provision matching Zoho Desk agents by email match. We flag any agent who does not have a corresponding Zoho Desk user account for the customer's admin to provision before production migration.

ChannelReply's Unwanted Text Remover preprocessing feature strips extraneous text (email headers, quoted replies) before displaying messages. This is not a stored data object but a message display setting. We document the active preprocessing rules and provide a Zoho Desk Email Parser configuration guide that replicates the behavior using Zoho's email parsing and filtering tools. This is delivered as documentation for the customer's admin to configure post-migration.

ChannelReply notification settings per marketplace and per account define which events trigger a ChannelReply message (and thus count toward the message limit). We export the active notification settings as a structured CSV and map them to Zoho Desk SLA definitions and Assignment Rules where applicable. For example, an Amazon shipment update notification enabled in ChannelReply maps to a Zoho Desk SLA rule that resets response time on shipment-status-change events.