Migrate from Anywhere365 to Zoho Desk

Anywhere365 UCC profiles include presence states, skill assignments, and lowest-presence hunt values tied to each agent's Teams identity. We export agent records from the Core REST API using Entra ID bearer token authentication and map them to Zoho Desk Agent records by email. Skill group assignments from Anywhere365 are preserved as Zoho Desk custom fields (agent_skill_group__c) since Zoho Desk's native skill-based routing requires the Advanced SLA add-on. Agent presence configurations are documented for the customer to configure in Zoho Desk's agent availability settings.

Anywhere365 Queues are logical routing constructs above Teams Call Queues with escape actions, SLA thresholds, and wrap-up codes that have no direct Zoho Desk equivalent. We export the full queue configuration manifest (routing rules, priority levels, escape actions, wrap-up codes, SLA timers) and reconstruct the routing logic as a Zoho Desk Blueprint process map delivered as a written document for the customer's admin to configure in Blueprint. Queue priority is preserved as a custom ticket priority field. The queue-to-department assignment is handled via Zoho Desk's department model, with the primary queue mapping to a Zoho Desk department and overflow routing mapped to Blueprint stages with conditional escalation paths.

Anywhere365 voice interactions include agent assignment, queue wait time, wrap-up codes, disposition, and duration. We split each voice interaction into a Zoho Desk Ticket (representing the customer service case) and a Call record (representing the phone contact). The ticket subject is derived from the queue name and disposition. Wait time, talk time, and wrap-up codes migrate to custom ticket fields (wait_time_seconds__c, talk_time_seconds__c, wrap_up_code__c). Call recording URLs are preserved as ticket attachment URLs pending re-hosting since Zoho Desk stores attachments differently from Anywhere365's Dialogue Cloud timeline.

Email interactions in Anywhere365 are part of the interaction record with subject, body, agent response, and thread direction. We map each email thread to a Zoho Desk Ticket with threaded comments preserving the inbound-outbound direction. The original email subject becomes the ticket subject. Email attachments migrate to Zoho Desk ticket attachments within the 30MB file limit per import. Inline images in email bodies are flagged for re-upload since Zoho Desk's import handles attachments as separate records.

Multichannel asynchronous conversations (web chat, WhatsApp, SMS) are stored as conversation threads in Anywhere365 with references to the CRM Service connector for linked records. We map each conversation thread to a Zoho Desk Ticket with threaded comments preserving the message direction and timestamp ordering. Channel source is preserved in a custom field (source_channel__c). Thread integrity is maintained by ordering comments by the original timestamp from the Anywhere365 interaction record.

Anywhere365 Dialogue Manager scripts define IVR branching logic across voice, web chat, WhatsApp, and email channels with dynamic text loading via text-to-speech. These scripts have no direct Zoho Desk equivalent because Zoho Desk uses Blueprint for ticket process flows rather than pre-contact IVR routing. We deliver a written Blueprint design document mapping each Dialogue Manager script entry point to a Zoho Desk Blueprint stage, with conditional routing paths documented for admin configuration. The IVR prompt texts are preserved in the document so they can be recreated as Zoho Desk macro responses or help center articles.

Anywhere365 custom properties (customer segmentation, SLA tiers, routing attributes) are stored as name-value pairs attached to interaction records. We export these as custom field imports in Zoho Desk, mapping property names to API field names (lowercase with underscores). A critical distinction: Zoho Desk custom fields are scoped per department per module, meaning a custom field created in the Support department is not available in the Accounts department without separate field creation. We create custom fields per target department and map property values to the correct department-scoped field.

WebAgent desktop configurations, tab layouts, and shortcut settings control the agent-facing interface in Anywhere365. These settings are platform-specific to the WebAgent client and do not transfer to Zoho Desk's agent interface. We deliver a written summary of each agent's queue assignments and skill group memberships from WebAgent so that the Zoho Desk admin can configure equivalent agent permissions and tab layouts post-migration. WebAgent layout presets are not migratable.

Queue jukebox media assets, announcements, hold music, and IVR prompt files are hosted within the Anywhere365 SaaS environment or customer tenant. We export a manifest of all media asset references (filename, duration, usage context, and URL if accessible) and deliver it as a handoff checklist. Actual audio files require manual download from Anywhere365, re-upload to Zoho Desk's media library (or a linked content delivery URL), and re-linkage to queue configurations. This step is documented as a manual post-migration task with file-by-file re-hosting instructions.

Anywhere365 WFM components track agent schedules, adherence, and forecasting data available via the Core REST API. Zoho Desk does not include a native WFM module. We export WFM schedule configurations as a written schedule manifest and deliver agent availability patterns as Zoho Desk agent working hours configuration. Adherence and forecasting data are preserved as a reference CSV for the customer's workforce management team to import into a dedicated WFM tool or to use as baseline configuration for Zoho Desk's Advanced SLA scheduling features.

Anywhere365 interaction records reference customer contact data (name, phone, email, organization) attached to the interaction history. We extract unique contact records from the interaction dataset, deduplicate by email, and import into Zoho Desk Contacts with linked Accounts. Contact phone numbers from voice interactions map to the Contact phone field and to the Call record for call association. Any CRM linkage maintained through Anywhere365's CRM Service connector is preserved by resolving the linked record reference and creating a corresponding Account in Zoho Desk.

Anywhere365 SLA thresholds define first response time, queue wait time, and resolution time targets per queue or customer tier. Zoho Desk SLA Policies enforce first response and next response times at the department level. We map Anywhere365 SLA thresholds to Zoho Desk SLA Policy configurations, with queue-level granularity reduced to department-level since Zoho Desk applies SLA policies per department. Custom SLA fields (sla_queue_target__c, sla_priority__c) are created to preserve the per-queue threshold reference for audit purposes.