Migrate from Anywhere365 to Freshdesk

Anywhere365 agent identities are stored as UCC profiles containing presence configurations, skill assignments, hunt-group membership, and WebAgent desktop settings. We export each UCC profile by email address and map it to a Freshdesk Agent record, preserving the agent's display name, email, and group membership. Agent availability settings (presence states) require manual reconfiguration in Freshdesk's Agent Settings because the presence model differs between Teams-based UCC and Freshdesk's online/offside/busy agent status.

Historical Anywhere365 interaction records (customer dialogue, agent assignment, queue wait time, wrap-up codes, disposition) map to Freshdesk Tickets with embedded Conversations. The interaction's timestamp, channel type (voice/email/chat/SMS/WhatsApp), and disposition migrate as Ticket properties. The full customer and agent dialogue migrates as Conversation notes and replies on the ticket. Queue wait time and agent assignment are preserved as ticket custom fields. Freshdesk's conversation threading preserves the chronological order of the original interaction.

Anywhere365 Queues are logical routing constructs sitting above Microsoft Teams Phone System and are not exposed via Microsoft Graph API. We must pull queue configuration from the AnywhereNow Core REST API or Attendant Console exports. Each queue maps to a Freshdesk Group with the same agent membership. Queue routing rules (overflow, escape actions, SLA thresholds) are documented as configuration records for the customer's admin to rebuild as Freshdesk Routing Rules in Admin > Dispatcher Console. Queue-level wrap-up codes migrate as Freshdesk Ticket custom fields or predefined field values.

Anywhere365 customer records linked to interactions (including CRM Service connector references) map to Freshdesk Companies. The company name, domain, and any custom properties migrate directly. Note that Freshdesk's Company API uses org_company_id rather than id in list responses, which affects how we resolve lookups during custom object population. We fetch company records via GET /api/v2/companies to capture org_company_id for cross-object reference.

Anywhere365 custom properties (customer segmentation flags, SLA tier markers, routing attributes) extend the base objects and are exported as name-value pairs. We map each to a corresponding Freshdesk ticket field, company field, or contact field depending on the target object. Custom objects in Freshdesk require pre-creation via the Custom Object API before any lookups can be resolved. The Freshdesk Custom Object API requires the Company API scope, and lookup fields must use the target record's org_company_id rather than its id when populating lookup relationships.

Dialogue Manager scripts define branching IVR flows for voice, web chat, WhatsApp, and email channels. These are structured scripts with dynamic text loading and conditional routing that do not have a direct Freshdesk equivalent. Freshdesk's automation builder handles ticket-level triggers (status change, priority change, assignment) but not inbound IVR dialogue routing. We export a manifest of each Dialogue Manager script including channel, entry point, branch conditions, and action nodes. The customer's admin rebuilds these as Freshdesk Freddy AI bot flows or as Routing Rules using the documentation we deliver.

Queue jukebox announcements, hold music, and IVR prompt files are media assets hosted within the Anywhere365 SaaS environment. We export a manifest listing each media asset, its reference URI, the queue or dialogue it is attached to, and the playback trigger. The actual audio files require download and re-upload to a CDN or the Freshdesk Knowledge Base. Re-linkage to Freshdesk routing rules is documented separately for the customer's admin to complete post-migration.

Where available via the AnywhereNow Core REST API, WFM schedule, adherence, and forecasting configurations are exported as documentation. Freshdesk does not have a native WFM module in its core product. Any agent scheduling logic documented from Anywhere365 WFM is delivered as a configuration inventory that the customer can rebuild using Freshdesk's availability settings, agent roles, and shift-based routing if available on their plan tier.