Migrate from GorillaDesk to Zoho CRM

GorillaDesk Customer maps directly to Zoho CRM Contact, transferring first name, last name, email, phone, mailing address, and any notes as standard Contact fields. The GorillaDesk custom properties service_type, route_assignment, and technician_preference become custom fields on the Contact (for example, Service_Type__c, Route_ID__c, Preferred_Technician__c) that must be created via the Zoho CRM Settings API before migration loads any data, preserving the original service category and routing information for segmentation and reporting.

GorillaDesk customers who have not yet had a scheduled job are treated as raw prospects and migrate as Zoho CRM Leads. Active customers with at least one completed job migrate as Contacts. The split is determined by job_history_count in GorillaDesk before migration runs.

GorillaDesk Company maps to Zoho CRM Account, moving company name, domain, and billing address into Account.Name, Account.Website, and Account.Billing_Street/City/State/Zip respectively. GorillaDesk's parent_company_id becomes the Account.Parent_Account lookup, enabling multi‑location hierarchies; this lookup requires the parent Account to be migrated first, and any circular references are flagged during validation to avoid broken links.

GorillaDesk Job has no direct Zoho CRM equivalent — it is a composite of a Deal (revenue, stage, close date) and a service description. FlitStack AI maps job_name to Deal_Name, job_amount to Amount, job_status to Stage (value-mapped: Scheduled→'Pre-Qualification', Completed→'Closed Won', Cancelled→'Closed Lost'), and job_date to Expected_Close_Date.

GorillaDesk line items—describing the service performed, materials used, and chemicals applied—map to Zoho CRM Deal Line Items attached to the corresponding migrated Deal. Each line item transfers item name, quantity, unit_price, tax_amount, and the original sequence order, preserving the service‑execution flow for reporting. The Deal Line Items are inserted via the Zoho CRM Bulk API, and any missing product records are created using the item name as the product identifier.

GorillaDesk service_type (e.g., 'Pest Control - Quarterly', 'Pool Cleaning', 'Carpet Cleaning') has no equivalent standard field in Zoho CRM. FlitStack AI creates a pick‑list custom field called Service_Type__c on the Contact module, populating it with every active service_type value discovered in GorillaDesk. This field enables detailed segmentation, targeted marketing, and service‑category reporting within Zoho CRM.

GorillaDesk route assignments identify which technician or route zone a customer belongs to. Zoho CRM has no native route concept. We create a Route_ID__c text field on Contact. Your Zoho admin can later populate this via Zoho Analytics or a route-optimization integration.

GorillaDesk User records (technicians, office staff) resolve by email to Zoho CRM Users. Unmatched GorillaDesk users are flagged and can be invited to Zoho CRM before migration or assigned to a fallback Zoho User. GorillaDesk role labels (technician, dispatcher) map to Zoho CRM Profiles and Roles.

GorillaDesk Note objects (created via POST /Note) migrate as Zoho CRM Notes attached to the parent Contact or Deal. The note body, created_at timestamp, and linked customer_id are transferred verbatim, preserving technician observations and client communications. Field‑technician notes that describe job details become Zoho Deal Notes, allowing context to stay with the revenue record.

GorillaDesk invoicing and payment-status records do not map to standard Zoho CRM objects. We export invoice data as a CSV and recommend connecting Zoho Books for full invoice management post-migration. Payment status flags can be stored as a custom field on the Deal for reference.

GorillaDesk Service Templates define pre-defined job checklists, required materials, and procedural steps. Zoho CRM has no native service-template equivalent. We export the template definitions as a JSON reference document for your Zoho admin to rebuild as a Zoho Blueprint or a custom module.

GorillaDesk stores GPS coordinates and driving directions for service addresses. Zoho CRM does not have a native GPS/latitude-longitude field. We store GorillaDesk location data as lat_long__c (text) on the Account record for reference. True map integration requires a Zoho Maps or Google Maps connector post-migration.