Migrate from FuseDesk to Salesforce Service Cloud

FuseDesk Cases map directly to Salesforce Case records. Case status (open, pending, resolved, closed), priority, and assigned agent migrate to Case.Status, Case.Priority, and Case.OwnerId respectively. All channel threads (email, SMS, chat, social) attached to the Case migrate as EmailMessage records (for email) and Task records with TaskSubtype=Call or TaskSubtype=Chat (for non-email channels). We resolve the parent Contact or Account by matching the FuseDesk contact email against Salesforce Contact email, and we flag any Case without a resolvable Contact as a manual Account creation step. FuseDesk's custom Case Fields discover via API during scoping and map to Salesforce Custom Fields on the Case object.

FuseDesk Notes attached to Cases — including inline checklists tracking multi-step resolutions — migrate as Salesforce Task records linked to the parent Case. Checklist items are preserved as a structured text block in the Task description field or as a custom checklist field, depending on the destination org's field inventory. We preserve the original note author and timestamp by setting Task.CreatedById to the mapped User and ActivityDate to the original timestamp.

FuseDesk syncs contact data from Infusionsoft/Keap and ActiveCampaign. Contact fields and custom properties vary by CRM configuration and may include address, phone, company, and custom properties that differ from standard Salesforce Contact fields. We discover the synced contact schema during the scoping run, map each FuseDesk contact field to a Salesforce Contact field (or custom field if no standard equivalent exists), and flag any field with no Salesforce analog for manual mapping review. The Contact mapping is a prerequisite for Case migration because Case records require a ContactId or AccountId.

FuseDesk Departments organize Agents and route Cases. We export department names and Case routing assignments. Salesforce queues serve a similar routing function. We create Salesforce Queues named after each FuseDesk Department and assign Cases to the corresponding Queue during migration. If the destination org uses Profiles and Permission Sets instead of Queues, we store the department as a custom picklist field on Case for reporting purposes.

FuseDesk Agents (support staff) map to Salesforce User records. We match by email address — if a FuseDesk Agent email matches a Salesforce User email, we assign the Case OwnerId to that User. If no match exists, we hold the Case in a reconciliation queue for the customer's admin to provision the User in Salesforce before record reassignment resumes. Agent role assignments and department memberships from FuseDesk are stored as custom fields on the Salesforce User record or mapped to Salesforce Profiles and Permission Sets.

FuseDesk ships email, text, and note Templates used by agents. We export Template content (subject, body, type) as structured JSON and categorize by type. Salesforce has Email Templates available in Classic and Lightning, but FuseDesk Templates often include dynamic variable syntax that does not map directly to Salesforce merge fields. We deliver a Template export file with original content and recommended Salesforce Template mapping; the admin rebuilds Templates in Salesforce Setup as a post-migration activity. Templates are not migrated as active, usable records — they are exported as content for manual recreation.

FuseDesk channel threads aggregate all inbound and outbound messages per Case. Email channel threads migrate to Salesforce EmailMessage records linked to the parent Case. However, FuseDesk strips email subject lines and CC/BCC headers on inbound messages, so original email envelope metadata cannot be reconstructed. We migrate the message body, sender address, timestamp, and thread order. Subject lines and CC lists appear as blank or missing in Salesforce and are documented in the migration audit report as a data gap attributable to FuseDesk's normalization behavior, not the migration process.

FuseDesk SMS, live chat, Facebook Messenger, Instagram DM, and phone channel messages have no direct Salesforce EmailMessage equivalent. We migrate each message as a Task record with TaskSubtype set to Call (for phone), Chat (for live chat), or Custom (for SMS and social channels). Message body and timestamp are preserved in Task.Description and ActivityDate. Channel metadata (SMS phone number, social handle) is stored in custom Task fields. This is a structural divergence — FuseDesk threads appear as a chronological list in its unified Case view, while Salesforce represents them as discrete Task records on the Case activity timeline.

FuseDesk allows custom fields on Cases beyond the standard set. Custom field schemas vary by account and may include drop-downs, text fields, number fields, or date fields. We discover custom field definitions via the FuseDesk API during scoping, create corresponding Custom Fields on the Salesforce Case object before migration, and map values during Case import. Custom picklist values in FuseDesk must be replicated as picklist values in Salesforce. If a FuseDesk custom field has no Salesforce equivalent, we store the value in a generic custom text field and flag it for the admin to re-evaluate after cutover.

Some FuseDesk accounts include a Knowledge Base of help articles and categories. We export Knowledge Base articles as structured content (title, body, category, tags) from FuseDesk. Salesforce Knowledge requires schema setup — Articles, Data Categories, and Article Types — before import. We create the corresponding Article Type and Data Category structure in Salesforce, then import articles as KnowledgeArticleVersion records. This step adds 1-2 weeks to the migration timeline because Salesforce Knowledge architecture must be designed and deployed to a Sandbox before production migration. If Knowledge Base is not in use in FuseDesk, this step is omitted and the migration scope covers Cases, Contacts, and Channels only.

FuseDesk attachments on Cases migrate as Salesforce ContentDocument records linked to the parent Case via ContentDocumentLink. We preserve file name, MIME type, content, and upload timestamp. Files are uploaded to Salesforce via the ContentVersion object and linked via ContentDocumentLink with LinkedEntityId pointing to the Case.