Migrate from Anywhere365 to Salesforce Service Cloud

Agent identities in Anywhere365 are tied to UCC profiles containing presence states, skill assignments, and lowest-presence hunt values. We export these as Salesforce User records, provisioning each agent with the appropriate Service Cloud permission sets (such as Service Cloud User, Omni-Channel, and any skill-specific access). Presence configurations map to Salesforce Presence configurations under Workforce Engagement Setup. Any agent without an existing Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import begins.

Anywhere365 Queues are logical routing containers not accessible via Microsoft Graph API. We pull all queue data directly from the Anywhere365 Core REST API, including routing rules, SLA thresholds, escape actions, priority weighting, and skill assignments. Each queue maps to an Omni-Channel Presence Configuration with Capacity and Skills-Based Routing settings. Skill tags from the Anywhere365 UCC profile become Salesforce Skills that agents are assigned to under Workforce Engagement Management.

Historical interaction records from Anywhere365 capture customer dialogue, agent assignment, queue wait time, wrap-up codes, and disposition. We map each interaction to a Salesforce Case record, preserving the original timestamp as CreatedDate, agent assignment as OwnerId, queue wait time as a custom Case field, and wrap-up codes as Case custom fields. The interaction channel (voice, web chat, email) is stored in a custom Case field because Salesforce's standard Channel field covers limited values. Interactions are imported after all Users and Cases are created to satisfy OwnerId and lookup dependencies.

IVR dialogue trees built in Dialogue Manager are structured scripts with branching logic for voice, web chat, WhatsApp, and email channels. These scripts load texts dynamically via text-to-speech and do not export as portable configuration. We do not migrate them as code. We deliver a written inventory of every Dialogue Manager script with its channel, trigger conditions, menu steps, and routing destinations, paired with a Salesforce Flow Builder equivalent recommendation. The customer's admin rebuilds these in Salesforce Omni-Flow or a partner IVR tool post-migration.

Multichannel dialogue threads span asynchronous channels. The Anywhere365 CRM Service connector links some conversation threads to CRM records. We preserve thread integrity by mapping each thread to a Salesforce Case with individual message records stored as Tasks or EmailMessage records. Channel type (WhatsApp, SMS, WebChat) is preserved in a custom Case field. Thread timestamps and sequence ordering are maintained via ActivityDate on each Task record.

Anywhere365 queue-level routing rules define how interactions are assigned to agents based on availability, skill match, and priority. We extract these rules from the Core REST API export and map them to Salesforce Omni-Channel Routing Attributes and Case Assignment Rules. Skill-level routing rules require pre-creation of matching Skills in Salesforce Workforce Engagement Management before the routing rules can be activated.

SLA thresholds defined per queue in Anywhere365 map to Salesforce Entitlement Processes and Milestones. First Response Time, Next Response Time, and Resolution Time thresholds migrate as Milestone records tied to an Entitlement. The queue priority weighting becomes the Case Priority mapping under the Entitlement.

Agent wrap-up codes and disposition values from Anywhere365 interaction records are mapped to Salesforce Case custom picklist fields. We extract the full list of wrap-up codes from the Core REST API export, create a corresponding custom picklist on Case, and populate the field value from the interaction disposition field during Case import.

WebAgent is the agent-facing interface handling queue display, call controls, tab layouts, and shortcut settings. These configurations are agent-specific desktop settings that do not migrate to Salesforce because Service Cloud agents work within the Salesforce Console with their own layout configuration. We export a manifest of WebAgent settings per agent for reference and document the equivalent Salesforce Console layout and utility bar configuration steps in the handoff document.

Organizations extend Anywhere365 objects with custom properties for customer segmentation, SLA tiers, and routing attributes. We export these as name-value pairs and create corresponding custom fields on the relevant Salesforce object (Case, User, or a custom object) before migration. Any custom properties that require schema pre-creation are flagged during scoping so the customer admin provisions the fields in the destination org before the migration phase begins.

WFM components track agent schedules, adherence, and forecasting data. Where available via the Anywhere365 Core REST API, we export WFM configurations as a reference document. Direct migration of WFM data is limited because Salesforce's Workforce Engagement Management is a separate licensing tier. We flag dependencies on the Anywhere365 WFM module that may require a separate Workforce Engagement Management scoping exercise for Service Cloud.

Custom announcements, hold music, and IVR prompt files referenced by Anywhere365 queues are hosted within the Anywhere365 SaaS environment or the customer tenant. We export a manifest of all media asset references (file name, queue assignment, usage context) but the actual audio files require manual download, re-upload to Salesforce's Files library or a connected IVR provider (such as AWS Polly or a telephony add-on), and re-linkage to queue configurations post-migration.