Migrate from GorillaDesk to Salesforce Sales Cloud

GorillaDesk Customer maps to a Salesforce Account (company/organization name and address) and a Salesforce Contact (individual name, email, phone). GorillaDesk's primary address becomes the Account billing/shipping address; secondary addresses require Salesforce's multi-address model or custom fields. FlitStack creates both records in a single migration step and links them by AccountId on the Contact.

GorillaDesk phone numbers migrate to Contact.Phone by default. If GorillaDesk stores a mobile label or second phone type, the secondary number migrates to Contact.MobilePhone. Label metadata from GorillaDesk's phone type list does not have a Salesforce equivalent and is discarded unless preserved as a custom field.

Email maps directly to Contact.Email. Used for Salesforce duplicate-matching on insert. If multiple GorillaDesk customers share an email (unlikely but possible in B2B service), Salesforce's duplicate rules apply and FlitStack flags these before the migration commits. During validation, FlitStack reviews all email values to identify duplicates and reports them for resolution before the migration run executes.

GorillaDesk Jobs are work orders — service tickets with a status, assigned technician, service type, scheduled date, and materials list. Salesforce has no native work-order object; Cases serve as the closest equivalent. FlitStack maps job fields to standard Case fields (Subject, Description, Priority) and preserves GorillaDesk-specific data in custom fields: Service_Type__c, Technician__c, Custom_Status__c, Materials__c, and Job_Created_Date__c.

GorillaDesk job statuses (e.g., Scheduled, In Progress, Completed, Cancelled) do not map 1:1 to Salesforce Case statuses (Open, In Progress, Closed). FlitStack builds a value-mapping table before migration so each GorillaDesk status routes to the correct Salesforce Case Status value. If your GorillaDesk uses custom status labels, they are captured as Custom_Status__c in addition to the mapped Case Status.

GorillaDesk Users (technicians and office staff) map directly to Salesforce Users. FlitStack resolves each GorillaDesk user by email match to an existing Salesforce User. If a Salesforce User does not exist for a GorillaDesk user, the account is flagged before migration — your team can invite the user to Salesforce first or assign their jobs to a fallback owner.

GorillaDesk Estimates have estimate number, status, line items, subtotal, and tax. Salesforce has no native estimate object (Quote is for Opportunity-linked proposals). FlitStack creates a custom Estimate__c object in Salesforce with Estimate_Number__c, Status__c, Subtotal__c, and Tax__c fields. Estimate line items map to Estimate_Line_Item__c (custom junction or child object) with description, quantity, unit price, and total.

GorillaDesk Invoices include invoice number, status, line items, subtotal, tax, and payment status. Salesforce has no native Invoice object. FlitStack creates a custom Invoice__c object with Invoice_Number__c, Status__c, Subtotal__c, Tax__c, Amount_Paid__c, and Balance_Due__c fields. Invoice line items migrate to Invoice_Line_Item__c with description, quantity, unit price, and total.

GorillaDesk notes on customers or jobs migrate to Salesforce Notes (the modern Notes object, not legacy Note). Each note preserves its body text, original created date, and the parent record link to the migrated Contact or Case. Note titles are derived from the first line of the note body if no explicit title field exists.

GorillaDesk file attachments on jobs or customers are downloaded and re-uploaded to Salesforce Files (ContentDocument / ContentVersion model). Files attach to the migrated Case or Contact via ContentDocumentLink. Salesforce Files carry a 25MB per-file size limit; files exceeding this are flagged before migration so your team can split or compress them.

GorillaDesk custom fields (custom_status, custom_priority, routing info, and any fields added via the Custom fields section) have no native Salesforce equivalent. FlitStack creates matching custom fields in Salesforce — suffixed with __c on the appropriate object — before migration. Custom pick-list values are mapped value-by-value. Custom field creation requires a Salesforce admin to deploy the fields or FlitStack can deploy them via API with appropriate credentials.

GorillaDesk service templates are pre-defined job definitions (service type, default duration, default materials). Salesforce has no direct equivalent. FlitStack migrates the service template name and description to a custom Service_Template__c object as reference records. Default duration and materials can be stored as fields on this object or mapped to Salesforce Products for pricing and inventory tracking.