Migrate from Sobot Omnichannel Suite to HubSpot Service Hub

Sobot Customer records map directly to HubSpot Contact. Sobot's CRM-integrated customer list-view fields transfer as Contact properties. If Sobot Customer records include a linked company or organization, we create the corresponding HubSpot Company record first and associate it via the Contact-Company association. Sobot's customer tags migrate as Contact properties (single-select or multi-select picklist based on Sobot's tagging structure). Email and phone fields map 1:1 to HubSpot's standard email and phone properties.

Sobot Tickets map to HubSpot Tickets with status and priority enumerations transferred where equivalent HubSpot values exist. Ticket subject becomes the HubSpot Ticket name. Sobot's channel source (email, chat, WhatsApp, voice, social) migrates as a tag or custom property on the HubSpot Ticket. Sobot's ticket owner maps to the HubSpot Ticket owner by email resolution against HubSpot Users. Custom fields on Sobot Tickets migrate as HubSpot custom properties with equivalent field types.

Sobot Agent accounts map to HubSpot User records by email. Sobot agent role and status fields map to HubSpot User properties including team assignment. Agents without matching HubSpot Users enter a reconciliation queue for the customer's admin to provision before the production migration. Inactive Sobot agents can be mapped to inactive HubSpot Users if ticket history preservation requires it.

Sobot team structures and skills-based routing configurations require field-level mapping to HubSpot's Team and Inbox model. Sobot routing rules that assign tickets based on team, skill, or language map to HubSpot Inbox routing rules configured during the migration setup phase. We deliver a written map of the Sobot team hierarchy and recommended HubSpot Team and Inbox structure for the customer's admin to configure.

Sobot conversation threads transfer as linked message records on the corresponding HubSpot Ticket. Each message becomes a Ticket comment with author, timestamp, body, and attachments preserved. Sobot internal notes migrate as internal Ticket comments with privacy flags. Sobot's agent handoff context and SLA timestamps transfer as Ticket properties or custom fields for audit continuity.

Sobot channel configurations for WhatsApp, email, live chat, voice, and social channels migrate as channel-type metadata (tags or custom properties) on the associated Ticket and Contact records. We do not establish live channel connections during migration because WhatsApp Business API requires independent Facebook Business Manager provisioning. Email routing into HubSpot Inbox requires post-migration DNS and routing setup by the customer's admin team.

Sobot workflow automation rules and task chatbot flows are extracted as structured definitions and translated to a written inventory document. We do not migrate automations as functional code because Sobot's automation logic and HubSpot Workflows are different automation models. The inventory document includes each Sobot automation's trigger conditions, actions, delays, and routing rules with a recommended HubSpot Workflow equivalent for the customer's admin to rebuild.

Sobot chatbot task workflows including knowledge search nodes, variable collection steps, and action invocations export as structured logic definitions rather than visual flow files. We extract the logic tree and conversation branches as a written document. HubSpot'sConversational Bot builder requires a separate configuration phase where Sobot bot logic is translated into HubSpot chatflow nodes, triggers, and conditional branches.

Sobot KB Articles and KB Categories transfer to HubSpot Knowledge Base. Sobot article body content migrates as HubSpot article content. Sobot article categories become HubSpot article categories or folders. Sobot's knowledge optimization metadata (search keywords, related articles) migrates as HubSpot article metadata or tags. Sobot article status (published, draft) maps to HubSpot article availability settings.

Sobot's tagging system transfers as standard tag assignments on Tickets and Contacts. Sobot tag taxonomy maps directly to HubSpot tag objects. Tags used for channel classification (WhatsApp, email, chat) migrate as tags on the associated Ticket. Tags used for customer segmentation migrate as tags on the Contact record.

Custom fields on Sobot Customer records and Tickets require field-level mapping during migration scoping. Sobot field types map to HubSpot property types: text to single-line text or multiple-line text, number to number, date to date picker, dropdown to single-select or multi-select picklist, and checkbox to boolean. Multi-value Sobot fields map to HubSpot multi-select picklists.

Sobot's 300+ built-in reports and custom report definitions cannot migrate as functional reports because Sobot's reporting schema has no direct HubSpot equivalent. We deliver a written inventory of every Sobot report with its metrics, filters, dimensions, and schedule, mapped to a recommended HubSpot Service Hub report type and dashboard configuration for the customer's admin to rebuild.