Migrate from CommBox to Salesforce Service Cloud

CommBox Customer profiles map to Salesforce Contact. Name, email address, phone number, and any tenant-defined custom properties (CRM ID, membership number, birth date) migrate as typed Contact fields or custom fields. Customer identity is preserved using the email address as the dedupe key during import. Where CommBox Customers have no email (voice-only contacts), we generate a hash-based external ID and use it as the lookup anchor on the Case record.

Each CommBox Conversation becomes a Salesforce Case. The conversation's opening message, status (open, pending, resolved), priority, and SLA timer state map to Case Subject, Status, Priority, and EntitlementId (via Milestone tracking). Individual messages across WhatsApp, email, voice transcript, chat, and social channels migrate as Salesforce EmailMessage records linked to the parent Case, each tagged with a custom CommBox_Channel__c field identifying the source. This normalization collapses channel-siloed message threads into a single chronological view in Salesforce.

CommBox Agent profiles map to Salesforce User records. Name, email, team assignment, and role migrate. Agent-to-conversation attribution is preserved by setting Case OwnerId to the matching Salesforce User ID resolved by email. Any CommBox Agent without a corresponding Salesforce User is held in a reconciliation queue for the customer's admin to provision before Case import begins.

CommBox Teams map to Salesforce Groups (public groups or queues depending on the routing model). Teams are imported before Agents so that the Salesforce User's Group membership is resolved at the time of User insert. Team-based SLA assignments map to Salesforce Entitlement Processes scoped to the relevant Group or queue.

CommBox Channels (WhatsApp, email, voice, chat, social) do not have a direct Salesforce standard object equivalent. Each conversation's channel attribution is captured as a custom picklist field, CommBox_Channel__c, on the Case. Channel-specific SLA configurations from CommBox migrate to Salesforce Entitlement Milestone definitions scoped per channel type using a CommBox_Channel__c filter criterion.

Every tenant-defined custom field on CommBox Customer profiles is extracted as a structured key-value pair during discovery. We map each to a Salesforce Contact custom field of equivalent type (text, number, date, picklist). Fields without a destination equivalent are flagged for the customer to define in Salesforce Setup before migration. Custom field naming follows Salesforce conventions with __c suffixes and a FieldType prefix where ambiguity exists (e.g., cbox_membershipnumber__c).

CommBox conversation tags migrate to a Salesforce custom picklist field on Case (Case_Tags__c) as a multi-select picklist. If the customer uses tags for content categorization across a knowledge base, we map them to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping based on how tags are used in reporting.

File attachments embedded in CommBox conversations are extracted via the media API and re-associated with their parent Case as Salesforce ContentDocument records linked via ContentDocumentLink. Inline images and media within email message bodies migrate as Salesforce ContentNote or as attachments on EmailMessage. File names and original timestamps are preserved to maintain media provenance.

CommBox knowledge base articles export as KnowledgeArticleVersion records in Salesforce Knowledge. Article title, body content, categories, and publish status migrate. Media embeds (screenshots, videos) are extracted and re-uploaded as ContentDocument records linked to the article body. Formatting differences between CommBox's article editor and Salesforce's Lightning knowledge editor may require manual post-migration formatting review for articles with complex layout structures.

AssignX routing rules have no documented export endpoint. We capture screenshots and configuration parameters for every active routing rule during the discovery phase and deliver a Routing Rules Inventory document that maps each CommBox rule to a recommended Salesforce Omni-Channel Work Item routing configuration or Case Assignment Rule entry. Routing rule recreation is a manual post-migration configuration task and is scoped separately from data migration.

CommBox SLA configurations defining response and resolution timers per channel or team migrate as Salesforce Entitlement Processes and Milestones. Each SLA name becomes an Entitlement record on the Contact, with First Response Time and Next Response Time milestones defined per channel type using a custom CommBox_Channel__c criterion. Entitlement configuration requires the Salesforce admin to recreate the exact timer thresholds in Salesforce Setup after migration.