Migrate from Verint Channel Automation to HubSpot Service Hub

Verint Interactions carry the core support record across all channels. We map interaction ID, status, timestamps, SLA flags (breach, met, warning), and priority to HubSpot Ticket properties. The original interaction channel (voice, email, social, chat, messaging) maps to the ticket conversation_source field or a custom source property. Threading is preserved by setting the ticket content to the initial customer message and appending subsequent messages as conversation entries. Verint's conversation_id becomes the HubSpot ticket hs_ticket_id for cross-reference.

Verint Channel records define the communication medium for each interaction. We map the channel enumeration to HubSpot's built-in conversation_source values: email becomes INBOX, live chat becomes CHAT, WhatsApp and SMS become MESSAGE, Facebook becomes FACEBOOK, Twitter/X becomes TWITTER, and voice becomes a custom TELEPHONY source property since HubSpot does not natively track voice within the ticket. Channel configuration at the destination requires enabling each source in Service Hub settings before the migration run.

Verint Agent records (name, email, role, team assignment, capacity settings) map to HubSpot Users. We resolve agents by email match against the destination HubSpot portal. Team assignments map to HubSpot Teams, and capacity settings are documented for reconstruction as HubSpot workflow-based workload management. Any Verint agent without a matching HubSpot User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Verint IVA and Agent Copilot Bot configurations define automation logic, decision trees, and handoff rules that are not structurally exportable from the platform. We document the active bot configurations during discovery by reviewing Verint's bot builder setup screens and interview the customer's bot administrators. The output is a written bot logic inventory with recommended Breeze AI agent equivalents in HubSpot, including trigger conditions, knowledge base grounding, and handoff thresholds. Bot rebuild is not included in migration scope.

Verint business-configurable routing rules map incoming contacts to teams, agents, or bots based on conditions. Routing logic is not exposed as structured data via Verint's API. We conduct a structured discovery session with the customer's Verint administrators to document each active routing rule (conditions, priority, target assignment, overflow handling). The output is a written routing rule inventory with recommended HubSpot Workflow equivalents, including trigger criteria, condition branches, and team assignment actions. Routing rebuild is not included in migration scope.

Verint SLA rules define response and resolution time targets per channel or queue. We export SLA definitions as structured records where accessible via API and map them to HubSpot Ticket SLA targets. Since HubSpot Service Hub does not have a native SLA enforcement engine in Starter, SLA targets migrate as custom number properties (sla_first_response_hours, sla_resolution_hours) that the customer's admin uses with workflow timers to enforce manually or via a third-party SLA tool on Professional and Enterprise.

Verint Knowledge Management articles (title, body content, tags, category associations) export via Verint API or SFTP. We transform article content to HubSpot Knowledge Base article format and import with matching articleSlug, articleBody (HTML), and publishStatus. Category mappings preserve the hierarchy, and tags map to HubSpot Knowledge Base topic associations. Articles linked to specific bot configurations are flagged in the migration report for the customer to re-link in Breeze AI agent grounding settings.

Verint Customer/Contact profiles carry contact details and cross-channel interaction history. We map name, email, phone, company association, and interaction count to HubSpot Contact properties. The Verint contact_id becomes hs_external_contact_id for cross-reference. Interaction counts and channel preferences migrate as custom properties. If Verint Customer Profiles include custom fields, we create matching HubSpot Contact custom properties before import.

Verint's Engagement Data Management uses SFTP push to export interaction data and media. We configure an SFTP receiver to capture Verint's export payload, parse the metadata JSON and WAV media files, and feed the structured data into HubSpot's import pipeline. Interaction content and timestamps become ticket messages; media files attach to the ticket or associated Contact record. This approach bypasses Verint's Excel export limitation (merged cells, auto-resize) and preserves data integrity.

Verint Interactions frequently carry custom fields capturing industry-specific data (case type, product line, escalation tier, department). We audit the Verint interaction schema during discovery, create matching HubSpot Ticket custom properties (with correct field types: single-line text, number, date, single-select, multi-select), and map values during import. Custom field mapping is validated in a sandbox pass before production migration.

Verint Customer Profiles that include a company association map to HubSpot CRM Companies. We resolve the company reference from the Verint Customer record and map to the HubSpot Company using domain name as the dedupe key. The Company is imported before Contact records so that the Company-to-Contact association is satisfied at insert time. If the customer's Verint environment uses a separate account object, we scope it as a distinct import with a mapping to HubSpot Company.

Verint captures CSAT, NPS, and survey response data tied to interactions. We export survey scores and response metadata from Verint's analytics export and map to HubSpot as custom properties on the associated Ticket (csat_score, nps_score) or as a custom Survey Response object. Survey linkage to the original interaction is preserved by referencing the migrated Verint interaction ID. HubSpot's native survey tool (Customer Satisfaction) is a post-migration replacement for ongoing survey collection.

Verint Compliance Archive stores call recordings and interaction media with metadata tags. We export WAV files and metadata from Verint's archive via the documented SMB folder, EMC Centera, or Hitachi Content Platform retrieval method (tapes and DVDs are not supported per Verint documentation). We attach recordings to the migrated HubSpot Ticket record using the HubSpot Files API. Encrypted calls are not supported for export and are flagged in the discovery report. Recordings from trader voice and front office calls migrate as separate file associations.

Scheduling and adherence data belong to Verint Workforce Management rather than Channel Automation. This data requires separate extraction via Verint WFM APIs and is out of scope for Channel Automation migration engagements. If the customer runs both WFM and Channel Automation, we scope each product independently and flag cross-product dependencies such as shared agent IDs that appear in both WFM and interaction records.