Migrate from Slaask to HubSpot Service Hub

Slaask Conversations map to HubSpot Service Hub Tickets. We preserve visitor name, page URL, timestamp, and conversation status (open, resolved) from Slaask as Ticket properties. If Slaask stored any tags or custom metadata on conversations, we map these to Ticket custom properties. The HubSpot pipeline and ticket stage are configured during setup to match the customer's preferred resolution workflow.

Slaask Message history within each Conversation migrates as HubSpot Ticket Comments in chronological order. We preserve the message author (visitor or agent), message body, and timestamp. If messages contain inline images, these migrate as attachments on the Ticket Comment. The original send order is maintained by setting the comment timestamp to the original Slaask message timestamp.

Slaask Visitor records map directly to HubSpot Contacts. Name, email, and any metadata collected at the time of chat (company name, phone, plan tier) become HubSpot contact properties. The primary email address is used as the dedupe key during import to prevent duplicate Contact creation. Visitor records without an email address are created with the name and available metadata as an identifier.

Slaask Custom Attributes attached to Visitor profiles map field-by-field to HubSpot Contact Properties. We preserve the original attribute name and data type (string, boolean, number, date). String attributes that used comma-separated values map to HubSpot multi-select picklists; boolean attributes map to HubSpot checkboxes; number and date attributes map to the equivalent HubSpot property types. Custom properties are created in HubSpot before Contact import begins.

Slaask did not have a native Company object. If visitor Custom Attributes included company name, company domain, or organization identifier fields, we derive HubSpot Company records from those values and create a Contact-to-Company association at migration time. If no company-level data was captured in Slaask Custom Attributes, this object is omitted from the migration scope.

Slaask conversations that were posted to Slack channels are recoverable via standard Slack export on a Business+ plan or higher. We extract message history from the Slack export, match each Slack thread to the corresponding Slaask Conversation by date, participant email, and channel name, and land the recovered messages as Ticket Comments in HubSpot. This step recovers history that existed only in Slack and never had a Slaask-native record.

Slaask routing rules directing conversations to specific Slack channels or team members have no direct HubSpot equivalent. We document each routing rule (channel name, team, condition logic) as a configuration specification during discovery. HubSpot Inboxes and team assignments are used to recreate equivalent routing in HubSpot Service Hub, but this is a manual rebuild outside the data migration scope.

Slaask's widget appearance settings, greeting messages, proactive chat triggers, and trigger rules are stored in Slaask's platform and cannot be exported. We document all visible widget settings during the discovery call and produce a configuration specification that the customer's HubSpot admin uses to configure the HubSpot Chat widget. The migration does not include widget implementation; this is a separate setup step or a HubSpot implementation partner engagement.

Slaask integrations with third-party tools beyond Slack are not recoverable in migration. We identify any third-party integrations connected to the Slaask workspace during discovery and flag each one as a reconfiguration item. The customer or their HubSpot partner implements equivalent integrations in HubSpot App Marketplace after migration.

Slaask team members referenced in conversation assignments map to HubSpot Users by email match. We extract all agent identifiers from Slaask conversation metadata and cross-reference against the destination HubSpot portal's User table. Any agent without a matching HubSpot User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Slaask Conversation created_at timestamps map to HubSpot Ticket hs_ticket_createdate (internal timestamp). We preserve the original date and time of the first visitor message so that historical reporting reflects when the conversation actually began. Updated_at timestamps map to the last-modified date on the Ticket.

If Slaask generated a direct URL or conversation identifier for each chat, we store this as a custom Ticket property (slaask_conversation_url__c) for audit traceability. This allows support managers to reference the original Slaask record if a compliance question arises post-migration, even though the original platform is decommissioned.