Migrate from ChannelReply to Zendesk

ChannelReply maps each incoming marketplace message into a helpdesk ticket. We preserve the full ticket chain including the subject line (derived from ChannelReply's message subject format), ticket ID, requester, assignee, status, and priority. ChannelReply's marketplace thread view maps to Zendesk's native threaded comment model where agent and customer replies are ordered by Zendesk's comment timestamp. We preserve ChannelReply's internal ticket ID as a custom field for cross-reference during reconciliation.

Individual messages from Amazon MWS/SP-API, eBay, Walmart, Etsy, Shopify, Back Market, Newegg and WooCommerce are the atomic unit ChannelReply delivers. We migrate each message body as a Zendesk Ticket Comment. Public comments (customer messages) and private comments (agent internal notes, ChannelReply system notifications) are distinguished by Zendesk's public boolean field. Shopify messages are handled as standard email-to-ticket comments without ChannelReply's marketplace metadata enrichment.

ChannelReply pushes order-level data into helpdesk custom fields: Buyer Name, Item Title, SKU, Order ID, Order Status, Order Total, Shipping Address, Buyer Location, Shipping Fee, Payment Method, and channel-specific fields (eBay Buyer Checkout Message, Etsy Tracking Number, Walmart Fulfillment Option, Back Market Payment Method, Newegg Item Number). We create matching Zendesk ticket custom fields before migration and map each ChannelReply field value to its Zendesk equivalent. Field types are aligned: text fields map to Zendesk text, numeric fields (Order Total, Shipping Fee) map to Zendesk numeric, and status fields map to Zendesk dropdown custom fields.

ChannelReply applies marketplace-specific tags to tickets to indicate the channel source (e.g., Amazon, eBay, Walmart, Etsy, Shopify, Back Market, Newegg, WooCommerce). We preserve these tags during migration and remap them to Zendesk's tag model. Zendesk's tag length limit is 100 characters per tag and there is no hard cap on tag count per ticket. Tags are preserved as a flat list; ChannelReply's hierarchical or nested tag structures are flattened to the leaf level.

ChannelReply stores each marketplace's API credentials (Amazon MWS/SP-API keys, eBay OAuth tokens, Walmart tokens) to pull messages and order data. These credentials cannot be exported from ChannelReply. We provide a credential reconnection checklist specifying the required permission scopes for each marketplace (e.g., Amazon SP-API orders read-only role, eBay sell account permissions). The Zendesk admin must manually reconnect each marketplace account to a Zendesk Marketplace app (such as ChannelReply itself for teams that want to continue using it) or an alternative Zendesk-native marketplace integration.

ChannelReply records action history (Amazon Mark as No Response, eBay Resolution Center case creation, Etsy shipping uploads, refunds, cancellations) in the ticket history. We preserve action timestamps, action types, and outcomes as Zendesk private comments with a standardized prefix (e.g., [CHANNELREPLY ACTION] Amazon: Mark as No Response triggered on [date]). The admin uses these records to continue in-flight Resolution Center cases manually after migration.

ChannelReply stores per-marketplace and per-account agent signatures used when agents reply from within the ChannelReply sidebar. These are exported as text configuration data. We deliver them as a Zendesk Macro inventory document with the recommended per-channel macro assignment, which the Zendesk admin creates manually in Admin > Macros. Zendesk Macros support dynamic placeholders (requester name, ticket ID) that ChannelReply signatures did not, allowing for an upgrade in signature behavior at rebuild time.

ChannelReply enriches each ticket with structured buyer and order data sourced from marketplace APIs. The buyer email and name map to Zendesk User (requester) fields. Order-level fields (SKU, Order ID, Order Total) map to Zendesk ticket custom fields attached to the requester. We resolve the Zendesk User record first so that the requester is created before any ticket assignment.

ChannelReply distinguishes between customer messages (required, counted toward limit) and system notifications (some free, some paid). We audit the customer's active ChannelReply notification settings before migration and deliver a written map of which notification types the customer had enabled. The Zendesk admin uses this list to configure equivalent notification handling via Zendesk Triggers or a Zendesk Marketplace app post-migration.

ChannelReply does not have its own user directory; it relies on the connected helpdesk for agent identity. Agent assignments and activity history are sourced from the helpdesk. We export agent assignments per ticket and map them to Zendesk User records by email match. Unassigned tickets in ChannelReply are flagged and mapped to a default Zendesk agent specified by the customer during scoping.