Migrate from GorillaDesk to Pipedrive

GorillaDesk customers map directly to Pipedrive People. Primary phone becomes the Person phone field, email maps to the email field, and the customer's primary address splits across Pipedrive's address subfields (street, city, state, zip). Additional locations that GorillaDesk stores as separate address records migrate as a custom address_long field on the Person.

GorillaDesk company records map to Pipedrive Organizations. Company name becomes the Organization name, domain/website maps to the website field, and industry maps via value-mapping since GorillaDesk and Pipedrive use different pick-list taxonomies. GorillaDesk company hierarchies (parent/child) map to Pipedrive Organization parent relationships.

GorillaDesk allows each customer to link to one primary company (and potentially additional companies). Pipedrive requires a single primary Organization link on the Person via the org_id field. Any secondary company associations in GorillaDesk are preserved in a custom field on the Person record since Pipedrive does not natively support N:1 person-to-multiple-organizations.

GorillaDesk jobs have no direct Pipedrive equivalent — jobs represent service-ticket records with status, assigned technician, route, price, line items, and location. FlitStack creates one Pipedrive Deal per GorillaDesk job, using the service template name as the Deal title and the job price as the Deal value. Job status (Scheduled, In Progress, Completed, Cancelled) maps to a custom pick-list field on the Deal since Pipedrive Deals use stage, not a status field.

Pipedrive has no native job-status equivalent for Deals. GorillaDesk's job status values (Scheduled, In Progress, Completed, Cancelled, On Hold) migrate to a custom pick-list field Job_Status__c on the Deal object. Stage mapping is configured separately in Pipedrive based on your preferred pipeline stages.

GorillaDesk service templates define repeatable job types (e.g., 'Quarterly Pest Control', 'Pool Inspection'). Pipedrive has no native service-template object. FlitStack uses the service template name as the Deal title and stores the full template identifier in a custom field Service_Template__c on the Deal so reporting by service type is possible in Pipedrive.

GorillaDesk job pricing comes from line items attached to the job. Pipedrive Deal.value is a single numeric field. FlitStack sums the GorillaDesk job line-item amounts and writes the total to Deal.value. If multiple meaningful price buckets exist, itemized amounts are preserved in custom fields on the Deal.

GorillaDesk users represent technicians and office staff. Pipedrive users represent CRM users. FlitStack resolves GorillaDesk users by email match to existing Pipedrive users. For technicians who will not be Pipedrive CRM users, the technician name and user_id are stored in a custom field Technician__c on the Deal.

GorillaDesk notes attach to customers via the /notes endpoint. FlitStack creates Pipedrive Activities of type 'Note' linked to the corresponding Person. Note content, create date, and last-modified date are preserved. Inline images or file attachments in GorillaDesk notes are downloaded and re-uploaded as Pipedrive Files attached to the Person record.

GorillaDesk custom properties on customers and jobs (routing zone, service area, custom pricing tier, customer priority flag) require corresponding Pipedrive custom fields. FlitStack creates these in Pipedrive before migration using the field type closest to the source type (text, pick-list, number, date). Field key names are preserved so reporting continuity is maintained.

GorillaDesk distinguishes phone types (Mobile, Work, Home, Fax). Pipedrive Person has a single phone field and a secondary phone field. Additional phone types beyond Mobile and Phone migrate as a custom field Phone_Other__c on the Person record. Phone type labels are preserved in the custom field value.

GorillaDesk stores GPS coordinates and route assignments on jobs. Pipedrive has no native GPS, route, or dispatch field. These values migrate as custom fields on the Deal (latitude, longitude, route_name) for reference, but Pipedrive cannot display route maps or dispatch from this data — a field-service add-on or third-party integration is required for those capabilities.