Migrate from QuickDesk to Salesforce Sales Cloud

QuickDesk Contacts migrate to Salesforce Contact. We preserve all standard fields—FirstName, LastName, Email, Phone, Title—and any custom contact properties via the API. The company's internal_id maps to a custom External_Id__c field for dedupe and reconciliation. A Salesforce Contact must have an AccountId to avoid being orphaned in the standard UI, so we resolve the company text field to an AccountId (see Account mapping) before Contact insert.

QuickDesk Leads migrate directly to Salesforce Lead. We preserve lead source, creation date, and status fields. Personalized lead form fields migrate as custom Lead fields. If the destination Salesforce org uses a Lead-to-Contact convert workflow, the customer's admin decides whether to convert before or after migration. Lead Status picklist values are matched against the Salesforce org's active status values and extended if needed.

QuickDesk stores company data as a text field on Contact rather than a separate object. We extract every distinct company name value, deduplicate by normalized string (trim, lowercase), and create one Salesforce Account per unique company. Contacts sharing the same company name receive the same AccountId. The customer reviews any duplicates flagged by our dedupe logic and decides whether to merge Accounts in Salesforce post-migration.

QuickDesk Customer Pipeline records map to Salesforce Opportunity. We extract deal name, amount, close date, stage, owner, and any custom deal fields. Stage mapping is configured against Salesforce StageName values that we define before migration. QuickDesk's stage progression rules (automated or manual) are preserved as documentation; they require rebuild in Salesforce as part of the automation handoff.

QuickDesk pipeline stages (prospecting, qualification, proposal, negotiation, close, etc.) map to Salesforce StageName values. We configure the stage set in Salesforce before migration, preserving the original QuickDesk stage names and assigning probability percentages to match historical close rates. Custom stage names from QuickDesk are flagged for renaming if they diverge from Salesforce conventions.

QuickDesk custom fields on Leads and Contacts, including personalized lead form fields, migrate as Salesforce custom fields with equivalent data types. Text fields map to Text, numeric fields to Number, dates to Date, and picklist values to Picklist. We create the destination fields in Salesforce before migration using the metadata API, match the API names to QuickDesk field names where possible, and populate the values during the record import phase.

QuickDesk call logs and task records migrate to Salesforce Task. Call duration, outcome, and notes migrate to custom Task fields. Task Status, Priority, and ActivityDate are preserved. Assignee resolution maps the QuickDesk owner reference to Salesforce OwnerId via the User email lookup. Automated activity triggers and goal-linked tasks do not migrate because QuickDesk automations are not exposed via API.

QuickDesk Calendar entries and goal-tracked activities map to Salesforce Event where they represent scheduled meetings or appointments. StartDateTime, EndDateTime, and Location migrate. Goal-setting linked to calendar activities is documented for the customer to rebuild in Salesforce with Goals or a custom object. Recurring calendar patterns require manual rebuild in Salesforce.

QuickDesk owners referenced on Contacts, Leads, Deals, and Activities are mapped by email to Salesforce User records in the destination org. We extract all distinct owner references, match against the User table by email, and populate OwnerId on each record type during import. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before the migration resumes.

QuickDesk call engagements with duration, disposition, and outcome migrate to Salesforce Task with TaskSubtype=Call and CallDisposition preserved in a custom field. Call recording URLs migrate as a text field on the Task record. The WhoId links to the converted Lead or Contact; the WhatId links to the related Account or Opportunity. ActivityDate preserves the original timestamp for timeline ordering.

QuickDesk note records migrate to Salesforce Note linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. Rich text formatting is preserved where the source API returns it; plain text is stored in the Note Body field. Attachments embedded in notes migrate as separate ContentDocument records linked to the same parent.

QuickDesk automation sequences and engagement triggers are proprietary and not exposed through the documented API. We cannot extract automation logic as code. During scoping, we document every automation name, trigger type, conditions, and actions visible in the QuickDesk account and deliver a rebuild checklist mapped to Salesforce Flow equivalents. The customer's admin or a Salesforce partner rebuilds each automation post-migration as a separate engagement.