Migrate from Slaask to Salesforce Service Cloud

Slaask Visitor records map to Salesforce Contact. The visitor name maps to the Contact's standard Name fields, email to Email, and phone to Phone. Any Custom Attributes collected on the visitor profile become typed custom fields on the Contact object (Text, Number, Date, or Picklist depending on the source data type). If the Slaask workspace captured company name, we create a parent Account record first and link Contact via AccountId. We resolve duplicate contacts by email during import.

Slaask Conversations map to Salesforce Case records. We create a dedicated Case Record Type named Slaask_Conversation to distinguish migrated Slaask cases from other Case origins (email-to-case, phone). Case Subject defaults to the Slaask Conversation thread title or the visitor name and page URL. Case Status maps to a custom Status field reflecting the Slaask conversation state. The ContactId on Case is resolved by matching the Slaask visitor email to the migrated Contact record.

Slaask Message records migrate as Salesforce Task objects linked to the parent Case via WhatId and to the Contact via WhoId. For messages that contain rich content or attachments, we store the content body in Task.Description and attach files as ContentDocument records via ContentDocumentLink. Message timestamps are preserved in ActivityDate. We flag any Message record where the sender email matches no migrated Contact as a manual review item.

Slaask per-workspace Custom Attributes on Visitor profiles become Salesforce custom fields on the Contact object. We define each attribute as a custom field with the appropriate Salesforce type (Text, Number, Picklist, or Checkbox) during the schema design phase, before any Contact records are loaded. We produce a mapping table documenting the Slaask attribute name, Salesforce API field name, and data type for every custom field created.

Slaask routing rules directing conversations to specific Slack channels or team members have no direct Salesforce equivalent. We document the routing rules during the discovery call as a configuration specification that the customer's Salesforce admin uses to configure Omni-Channel Routing, Service Channels, and Presence Configuration in Service Cloud. This is a change-management deliverable, not migrated data.

Slaask conversations that were posted to Slack channels are recoverable via a Slack Business+ or Enterprise Grid data export. We ingest the Slack export archive, match messages by timestamp and channel name to Slaask Conversation IDs from the dashboard export, and land matched messages as Salesforce Task records linked to the corresponding Case. Messages that cross-reference cleanly are attributed; messages that cannot be matched to a Slaask conversation are landed against the best-fit Contact by email if available.

Slaask widget appearance settings (greeting message, trigger rules, color scheme) are stored in Slaask's own platform and have no export mechanism. We produce a written widget configuration specification describing the current settings in plain language so the customer's team can configure the equivalent behavior in Salesforce's Embedded Service (formerly Salesforce Chat) or a third-party chat widget that the organization selects as the replacement live-chat tool.

Slaask integrations with third-party tools beyond Slack are not recoverable in migration because Slaask never exposed a configuration export API. We audit the Slaask dashboard for any documented integrations and produce an integration inventory listing each connected tool and its purpose. The customer's admin rebuilds each integration using Salesforce native integrations, AppExchange apps, or custom REST API connections post-migration.

Slaask Conversation metadata fields (visitor page URL, referrer, browser, conversation start time, conversation end time, status) map to custom fields on the Salesforce Case object. We create slaask_page_url__c, slaask_referrer__c, slaask_browser__c, slaask_conversation_start__c, and slaask_conversation_end__c as text or datetime fields on Case to preserve the full session context for support agents reviewing historical cases.

Any file attachments uploaded within Slaask Conversations are recoverable only if the customer has a Slaask dashboard export that includes attachment URLs. We download attachments from those URLs and upload them to Salesforce as ContentDocument records, linked to the corresponding Case via ContentDocumentLink. Attachments for which the export does not include a direct URL are flagged as unrecoverable and noted in the final reconciliation report.