Migrate from Slaask to Intercom

Slaask Visitor records map to Intercom Contacts. We extract name, email, and all Custom Attribute fields from the Slaask export and map them field-by-field to Intercom's standard contact fields or create new custom contact attributes. The visitor's first_seen and last_seen timestamps migrate as Intercom custom fields since Intercom tracks last_contacted_at natively but not first_seen.

Slaask Conversations map to Intercom Conversations. We preserve the visitor reference (linked to the migrated Contact), page URL, conversation status (open, resolved), and the routing channel in Intercom's conversation metadata. The conversation assignee maps to an Intercom Admin or Team if the Slaask routing rule identified a specific channel owner.

Slaask Messages within each Conversation map to Intercom Parts in chronological order. We preserve message author (visitor or agent), message body, and timestamp as conversation parts. Parts from Slaask operators land as admin parts; visitor messages land as user parts, matching Intercom's conversation threading model.

Slaask Custom Attributes on Visitor profiles migrate to Intercom custom contact attributes. We create matching attribute definitions in the Intercom workspace before migration and map values field-by-field. Attribute data types (text, number, date, boolean) map to equivalent Intercom attribute types. Any attribute with a Slaask-specific purpose (routing hints, source attribution) is documented for manual re-creation as a tag or segment filter in Intercom.

Slaask conversations that were posted to Slack channels may be recoverable via Slack's native export (available on Slack Business+ or Enterprise Grid plans). We cross-reference the Slaask export's channel routing data with the Slack export to reconstruct visitor contacts and conversation threads. Visitor identification relies on email presence in Slack messages or Slaask's own visitor records; anonymous messages without a contact link are imported as conversations without a Contact association.

Slaask conversation-level metadata (page URL, referrer, routing team, country, device type) maps to Intercom conversation custom attributes. We create these as conversation-level custom attributes in Intercom before migration so that the full context of each conversation is preserved and filterable by the support team after cutover.

Slaask's first_seen and last_seen visitor timestamps have no direct Intercom equivalent (Intercom tracks last_contacted_at but not first_seen). We create two custom date fields on the Contact: slaask_first_seen__c and slaask_last_seen__c, populated from the Slaask export. These fields support historical analysis of when visitors first engaged with the website.

Slaask routing rules directing conversations to specific Slack channels or team members have no direct Intercom equivalent. We document each Slaask routing rule during discovery (source page, condition, target channel or team) and produce a configuration specification mapping each rule to an Intercom Inbox or Team plus an assignment rule. The Intercom admin rebuilds these as Inbox routing rules post-migration.

Slaask widget appearance settings (greeting message, trigger rules, color, positioning) are Slaask-specific and cannot be exported. We document the widget configuration during discovery as a detailed checklist and produce a written specification that the customer uses to configure the Intercom messenger in their workspace. Intercom's messenger settings (launcher position, greeting, custom colors, proactive messages) are configured manually in the Intercom dashboard after migration.

Slaask integrations beyond Slack (CRM connections, analytics tools, webhook targets) are not recoverable in migration. We identify each connected tool during discovery and produce a written integration inventory. For each tool, we specify whether a native Intercom integration exists, whether the tool has a Slack-based alternative, or whether a custom API integration needs to be built. The customer's team reconfigures integrations post-migration based on this inventory.