Migrate from SmartDesk to Salesforce Sales Cloud

SmartDesk Leads map directly to Salesforce Lead. Lead Source and Lead Status from SmartDesk migrate to Salesforce LeadStatus picklist or custom fields on Lead. We enumerate the SmartDesk Lead schema via live API authentication or a SmartDesk platform export before migration to capture any custom properties that must map to Salesforce custom fields on Lead. Duplicate detection uses email as the dedupe key.

SmartDesk Contacts map directly to Salesforce Contact. Standard fields (Name, Email, Phone, Title, MailingAddress) migrate 1:1. Custom contact properties defined in SmartDesk must be pre-created in the Salesforce destination org as custom fields before migration; we provide the manifest. Contacts are imported after Account creation to satisfy the AccountId Lookup relationship required by Salesforce's data model.

SmartDesk Accounts and Companies are interchangeable objects and map 1:1 to Salesforce Account. Industry classification, employee count, annual revenue, and any custom properties attached to the account migrate to the corresponding Salesforce Account fields or pre-created custom fields. Website URL from SmartDesk becomes the Account Website field.

SmartDesk Deals map to Salesforce Opportunity. Deal name becomes Opportunity Name, deal value maps to Amount, expected close date maps to CloseDate, and owner maps to OwnerId. The SmartDesk Pipeline assignment determines the Salesforce Record Type and Sales Process, which together control the available stage values. We reconcile the stage set before migration because SmartDesk allows fully custom stage names with no standard set.

SmartDesk Pipeline Stages are enumerated from the source account and mapped to Salesforce StageName values on Opportunity. We configure Salesforce Sales Processes (one per SmartDesk Pipeline) to whitelist the migrated stage values, and map stage probability percentages from SmartDesk to Salesforce StageProbability. Stage sequence order is preserved from SmartDesk.

SmartDesk Pipelines map to Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process and Page Layout so that stage values, field visibility, and record-type-specific logic remain scoped per line of business. If the destination Salesforce org has multiple Record Types already configured, we reconcile the SmartDesk pipeline count against the available Record Type slots.

SmartDesk Tasks attach to Contacts or Deals with assignee, due date, status, priority, and description. We map Status to Salesforce Task Status, Priority to Priority, ActivityDate to ActivityDate, and the owner to OwnerId via the User mapping. Tasks linked to Deals in SmartDesk attach to the migrated Opportunity in Salesforce via WhatId.

SmartDesk call activities map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL (if available) migrate to custom Task fields. Activity timestamp becomes ActivityDate to preserve timeline ordering. Parent record linkage uses WhoId for Contact/Lead and WhatId for Account/Opportunity.

SmartDesk email activities migrate to Salesforce EmailMessage records (the email content and headers) linked to an Activity Task record (the timeline entry). HasAttachment, Incoming, MessageDate, Subject, and TextBody map directly. Email addresses resolve to Contact or Lead WhoId via the contact and lead mapping. If SmartDesk does not expose email body via API, the activity is logged as a Task with the subject preserved.

SmartDesk meeting activities map to Salesforce Event with StartDateTime, EndDateTime, Subject, Location, and Description preserved. Attendees resolve to EventRelation records linked to the migrated Contact, Lead, or User. If the SmartDesk meeting record carries internal notes, those migrate to the Event Description field.

SmartDesk note activities migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note title, body, and timestamp preserve. If SmartDesk notes include file attachments, those migrate as separate ContentDocument records linked to the same parent.

SmartDesk Campaigns store campaign name, type, status, start and end dates, and budget. These map to Salesforce Campaign fields (Name, Type, Status, StartDate, EndDate, BudgetedCost). Email send, open, and click tracking data does not migrate because it lives in the email delivery system rather than the CRM object. Campaign Member history migrates if the source export includes member records.

SmartDesk Email Templates migrate as Salesforce EmailTemplate records with the template body and subject preserved. Merge field placeholders are preserved as-is; dynamic content or conditional logic embedded in templates may require manual post-migration review because SmartDesk's template language may differ from Salesforce's merge field syntax. HTML templates migrate with the HTML body preserved.

SmartDesk Help Desk Tickets link to Contacts and carry priority, status, assignee, and conversation threads. Tickets map to Salesforce Case with Subject, Description, Priority, Status, and Origin. The linked Contact resolves to the migrated Salesforce Contact via email match. Conversation threads migrate as CaseComments or as EmailMessage records linked to the Case depending on the thread structure in the SmartDesk export. Case Record Type is configured based on the SmartDesk ticket category or queue.

SmartDesk Knowledge Base Articles migrate as Salesforce Knowledge articles with title, body (HTML), category, and publication status preserved. Links to attachments are preserved as URLs and re-linked post-migration. The article data category structure in SmartDesk maps to Salesforce Knowledge data categories if present. Publication status (draft, published, archived) maps to Salesforce Knowledge article statuses.

File attachments associated with Contacts, Deals, Tickets, or Notes in SmartDesk are downloaded and re-uploaded to Salesforce as ContentVersion records linked to ContentDocument. We handle file type validation, preserve original filenames, and link to the parent record via ContentDocumentLink. The ContentDocumentLink WhatId points to the migrated Account, Contact, Opportunity, or Case.

SmartDesk supports Unlimited Custom Fields on core objects. All custom field definitions in the source export are enumerated during schema discovery and listed in the custom field manifest. These must be pre-created in the Salesforce destination org before the migration run because Salesforce does not allow dynamic custom field creation via API during data load. Field types are mapped: SmartDesk text to Salesforce Text, number to Number, date to Date, checkbox to Checkbox, dropdown to Picklist.

SmartDesk Users and Owners are resolved by email address against the Salesforce destination org's User table. Any SmartDesk Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status and the User's Profile and Role migrate as metadata flags. Salesforce User records must exist before any record that carries OwnerId can be imported.