Migrate from GorillaDesk to Odoo CRM

GorillaDesk customers export as JSON with id, name, email, phone, address, and custom properties. FlitStack creates res.partner records with partner_latitude, partner_longitude from GorillaDesk GPS fields if present, and country_id resolved from address strings. The customer type (residential/commercial) maps to a custom x_customer_type selection field.

Commercial GorillaDesk customers frequently include multiple contacts representing different roles within the organization, such as an office manager responsible for scheduling, a billing contact handling invoices, and a site supervisor overseeing on-location work. FlitStack creates one primary res.partner record to represent the company, then generates additional related contact records using type='contact' and assigns each contact's specific function and email address while linking them to the parent company via parent_id.

GorillaDesk jobs carry status (scheduled, in-progress, completed, cancelled), scheduled date, assigned technician, service type, and notes. FlitStack creates a crm.lead for each completed or active job, using job status to set stage_id via Odoo's crm.stage mapping. Scheduled future jobs become lead_ids with a 'Scheduled' custom stage that the Odoo admin can rename to match their pipeline.

GorillaDesk job statuses (scheduled, in_progress, completed, cancelled) map to Odoo crm_stage records. FlitStack creates stage entries matching GorillaDesk's status vocabulary before lead import begins, or maps to existing Odoo stages if the pipeline is already configured. Probability values are assigned per stage per the admin's Odoo configuration.

GorillaDesk stores technician user IDs on each job. FlitStack resolves these by matching GorillaDesk user email addresses to Odoo res.users.login. Unmatched technicians are flagged pre-migration; the admin either invites them to Odoo or assigns their jobs to a fallback user to preserve the technician dimension as a custom x_technician_id field.

GorillaDesk service types (pest control, lawn care, cleaning, etc.) have no native Odoo CRM equivalent. FlitStack creates a selection field x_service_type on crm.lead, pre-populated with the distinct service-type values found in the source data. The admin can rename or add values via Odoo Studio after migration.

GorillaDesk invoice data (amount, status, line items, payment method) maps to Odoo account.move records when the Odoo Accounting app is installed. FlitStack creates customer invoices (type='out_invoice') linked to the res.partner via partner_id. Invoice line items become account.move.line records with product reference. Unpaid GorillaDesk invoices migrate as 'posted' or 'draft' based on payment_status.

GorillaDesk notes attached to customers or jobs migrate as mail.message records linked to the corresponding res.partner or crm.lead via model and res_id. FlitStack preserves the full note body content, author information derived from user_id, and original create_date timestamp so that the note chronology reflects the actual GorillaDesk activity sequence rather than migration runtime.

GorillaDesk users with name, email, and role (admin, office, technician) map to Odoo res.users. FlitStack creates users with active=True for office/admin and can set active=False for technicians who should not have Odoo login. The admin must set passwords post-migration or use Odoo's invitation flow.

GorillaDesk stores multiple phone numbers per customer with type labels (work, mobile, home). FlitStack maps the first work phone to res.partner.phone, the first mobile to mobile, and stores additional phone numbers as a serialized x_additional_phones custom field since Odoo res.partner natively supports only one phone and one mobile.

GorillaDesk custom properties appear as top-level JSON keys on customer and job records. FlitStack creates matching Odoo custom fields via ir.model.fields before migration: selection fields for pick-lists, char/text for strings, float/integer for numbers, date/datetime for timestamps. Field names are normalized (lowercased, underscores replace spaces) and prefixed with x_studio_ on Enterprise instances.