Migrate from Anywhere365 to HubSpot Service Hub

Anywhere365 Queues are logical routing constructs above Microsoft Teams Phone System that are not accessible via Microsoft Graph API. We extract queue configurations, routing rules, escape actions, and SLA thresholds directly from the Anywhere365 Core REST API or Attendant Console exports. Each queue maps to a HubSpot Ticket pipeline with team-based assignment routing. SLA thresholds become conditional SLA rules on the pipeline. Agents assigned to each queue map to HubSpot Teams, and individual ticket assignment follows the queue's routing rule logic via HubSpot's team routing settings.

Agent UCC profiles in Anywhere365 include presence states, skill assignments, lowest-presence hunt values, and WebAgent desktop configurations. We export these as HubSpot User records, mapping the agent's email address as the primary key. Skill assignments and presence configurations are preserved as custom User properties. Any agent without a matching HubSpot User record enters a reconciliation queue for the customer's admin to provision before the agent-level migration phase begins.

Historical Anywhere365 interactions (voice calls, web chat sessions, emails, WhatsApp threads, SMS) preserve as HubSpot Ticket records with conversation threads attached. Each interaction's queue wait time, agent assignment, wrap-up code, and disposition migrate as Ticket properties and conversation message records. Channel type maps to the HubSpot Ticket's source channel property. The original timestamp preserves on each conversation message for timeline integrity.

Asynchronous multichannel conversations in Anywhere365 that are linked to CRM records via the Anywhere365 CRM Service connector migrate to HubSpot Conversations inbox. Each thread becomes a Ticket with messages preserved in chronological order. Channel attribution (WhatsApp, SMS, web chat) is set via the ticket source property. Thread-to-contact linking uses email address or phone number as the dedupe key against HubSpot Contacts.

Organizations that extend Anywhere365 objects with custom properties for customer segmentation, SLA tiers, and routing attributes export these as name-value pairs. We create equivalent custom properties on the HubSpot Ticket object before migration. Custom field types (text, number, date, picklist) map to the corresponding HubSpot property types. Fields used for SLA tiering map to HubSpot SLA rule conditions.

IVR dialogue trees built in Dialogue Manager with branching logic across voice, web chat, WhatsApp, and email channels are stored as structured scripts with dynamic text-to-speech loading. We do not migrate these as executable configuration. We produce a written inventory of every Dialogue Manager script, including its trigger conditions, branch logic, channel coverage, and recommended HubSpot Workflow or Conversation Automation equivalent. The customer's admin rebuilds routing logic in HubSpot's Workflow builder post-migration.

Queue jukebox media assets, hold music, and announcement files hosted in the Anywhere365 SaaS environment or customer tenant require manual rehosting. We export a manifest of all media asset references (file names, queue assignments, play triggers) and flag which files need to be downloaded from Anywhere365, re-uploaded to HubSpot's knowledge base or a linked media host, and re-linked to queue routing configurations. This step is documented for the customer's admin to execute post-migration.

WebAgent desktop configurations, tab layouts, queue display settings, call controls, and shortcut settings exportable from Anywhere365 do not have a direct HubSpot equivalent. We document the full WebAgent configuration profile for each agent and deliver it as a configuration reference sheet. The customer's admin recreates relevant display and layout preferences in HubSpot's user settings and any installed agent productivity apps from the HubSpot App Marketplace.

WFM components tracking agent schedules, adherence, and forecasting data export from the Anywhere365 Core REST API where available. We preserve WFM configurations as a reference document for the customer's workforce management team. HubSpot Service Hub does not include native WFM scheduling; teams requiring this functionality need a third-party WFM tool (Shifts, Zoom Workforce Management, or similar) integrated via HubSpot's API post-migration.

Wrap-up codes and disposition values assigned by agents at the end of Anywhere365 interactions migrate to HubSpot Ticket custom properties of type enumeration. Each wrap-up code becomes a picklist value on the migrated Ticket. We preserve the mapping between Anywhere365 wrap-up codes and their descriptions so that reporting continuity is maintained across the transition.

Anywhere365 interaction records linked to CRM records through the Anywhere365 CRM Service connector carry forward the linked contact reference. We resolve these contact references using email address or phone number as the lookup key against HubSpot Contacts. Unresolved contact references are flagged in a reconciliation report for the customer's admin to investigate before the conversation history migration phase.

SLA thresholds configured per Anywhere365 Queue (first response time, resolution time, escalation triggers) migrate to HubSpot SLA Rules attached to the corresponding Ticket pipeline. We map threshold values and escalation actions to HubSpot's SLA rule conditions, including business hours definition and milestone deadlines. SLA reporting metrics carry forward as pipeline-level targets.