Migrate from Infoset to HubSpot Service Hub

Infoset Tickets map to HubSpot Tickets as the primary support record. We preserve ticket status, priority, assignee (mapped to HubSpot Owner/User), full conversation thread, and created/updated timestamps. Infoset's pipeline stage names map to HubSpot Ticket pipeline stages which we configure before migration. If Infoset Tickets are linked to Deals, we also map the association to HubSpot Deals and preserve the ticket-to-deal link via HubSpot's association API.

Infoset Contacts migrate 1:1 to HubSpot Contacts with all standard fields (name, email, phone, company link) preserved. Custom contact properties in Infoset map to HubSpot Contact Properties, creating equivalent custom fields in HubSpot during schema setup. We use email address as the dedupe key. If Infoset Contacts are associated with Companies, we import Companies first so that the Company lookup is satisfied at Contact import time.

Infoset Company records map directly to HubSpot Companies. The company name, domain, industry, employee count, and address fields migrate to equivalent HubSpot Company properties. HubSpot Company is created before Contact import to satisfy the parent lookup. If Infoset Companies have associated Deals, we map the deal associations to HubSpot Deals attached to the same Company record.

Infoset Deals (sales pipeline records with stage, value, close date, and owner) map to HubSpot Deals. The deal stage from Infoset maps to HubSpot Deal stage within a configured Deal pipeline. We map Infoset deal amount to HubSpot deal amount, close date to close date, and owner to a HubSpot User. If Infoset Deals are associated with Contacts and Companies, those associations migrate as HubSpot Deal associations via the HubSpot associations API.

Infoset multi-channel conversation threads (email, live chat, social messages) map to HubSpot Conversations threads. We preserve channel type (email, chat, Facebook, Instagram, WhatsApp) as HubSpot Conversation source attribution, message timestamps, participant agents, and inline attachments. Each conversation thread is associated with the migrated Contact record. We flag conversations that fall outside the 3-month retention window and cannot be extracted from Infoset.

Infoset agent profiles map to HubSpot Users. We resolve agents by email match against the HubSpot destination portal. Agent roles (admin, agent) map to HubSpot User roles where applicable. If Infoset agent seats exceed the HubSpot Service Hub plan allowance, we flag the overage during scoping and recommend a plan upgrade before migration proceeds.

Infoset Help Center articles and category hierarchy migrate to HubSpot Knowledge Base articles. We preserve article title, body content (with rich text formatting), publication status, category assignment, and article slug. Articles are created in HubSpot's knowledge base before or alongside ticket migration to enable linking help articles to tickets.

Infoset cloud call center records including IVR path traversed, call queue name, call duration, disposition, and recording URL link migrate to HubSpot Calls. We preserve call start time, end time, duration in seconds, and recording attachment (downloaded as a binary blob and re-attached in HubSpot). Inbound versus outbound direction migrates as a custom property. Call associations link to the Contact record.

Infoset connected mail accounts map to HubSpot Shared Email Inbox routing rules. We map mail account routing (inbound email assignment, auto-response rules) to HubSpot Inbound mailbox rules and sequence assignments. If the source account count exceeds the HubSpot plan allowance, we recommend consolidation during scoping. Multiple mail accounts on Infoset may require HubSpot Professional+ for sufficient routing rule capacity.

Infoset chat widget configurations (branding, greeting messages, online/offline settings) map to HubSpot Chat widget settings. We identify all active widget instances in Infoset and configure equivalent HubSpot chat widgets before migration. If Infoset deployment includes multiple widgets across different websites or brands, we consolidate them into HubSpot's multi-widget architecture and flag any that require additional HubSpot Chat seats.

Infoset automation rules (ticket routing triggers, auto-responses, campaign triggers) do not migrate as executable code. HubSpot workflows use a different trigger-action model with different field names and flow logic. We deliver a written inventory of every active Infoset automation with its trigger conditions, actions, and recommended HubSpot workflow equivalent, so the customer's admin rebuilds them post-migration in HubSpot's workflow builder.

Infoset pre-built reports and custom dashboards are platform-specific definitions that do not export. We migrate the underlying raw data (ticket volumes, CSAT scores, agent metrics, call duration stats) as structured records or CSV extracts. The customer's admin rebuilds reports and dashboards in HubSpot's analytics engine using the migrated data. We provide a report requirements document listing each Infoset report's metric definitions for the admin to recreate.