Migrate from GorillaDesk to Freshsales

GorillaDesk scheduling and job data has no native Freshsales equivalent and must be preserved as a custom-field payload

GorillaDesk's scheduling engine — job dates, assigned technician IDs, GPS coordinates, service type, and dispatch status — is stored in GorillaDesk's job objects, which have no structural match in Freshsales. Freshsales has Contacts, Accounts, Deals, and Sales Activities but no native scheduling or field-service dispatch object. FlitStack serializes GorillaDesk job and dispatch records into a structured JSON string and stores it in a Freshsales Contact custom field (Field_Service_Data__c). This preserves the data completely for operations teams to reference or reconstruct in a dedicated scheduling tool, but it does not become an active schedule in Freshsales — it remains read-only reference data. Teams expecting live scheduling visibility in Freshsales after migration will need to rebuild dispatch logic in Freshsales Workflows or a connected scheduling platform.

GorillaDesk custom fields require pre-creation in Freshsales before migration; the 100-field-per-object limit constrains complex setups

Freshsales enforces a maximum of 100 fields per object on Contacts, Accounts, Leads, and Deals. GorillaDesk allows flexible custom field creation without a documented per-object cap in its public API schema. For GorillaDesk accounts with 50+ custom fields on the Customer object, FlitStack must prioritize the highest-value fields for migration and document the remainder in a custom-field export manifest for post-migration manual entry. Additionally, Freshsales custom fields must be created before migration runs — FlitStack handles this via the Freshsales API, but the custom field names, types, and pick-list values must be confirmed in the migration plan. If a GorillaDesk custom field type (e.g., multi-select checkbox) has no direct Freshsales equivalent, FlitStack maps it to the nearest Freshsales field type and notes the transformation in the field-level diff.

GorillaDesk VoIP call logs and SMS history do not migrate to Freshsales without Freshcaller

GorillaDesk includes integrated VoIP calling, SMS messaging, call recording, and transcription as a native feature across its plan tiers. Freshsales does not store call records or SMS threads without the Freshcaller add-on, which is a separate Freshworks product. FlitStack exports GorillaDesk call log metadata (call ID, timestamp, duration, recording URL) as a custom field on the Freshsales Contact record, preserving the reference for manual re-linking if Freshcaller is activated. However, the actual call recordings and SMS message bodies are not transferred into Freshsales because the platform lacks a native telephony storage object. Teams relying on GorillaDesk call recordings for customer service disputes or compliance audits must retain GorillaDesk access or export those recordings independently before the migration window closes.

GorillaDesk's API rate limits (HTTP 429) can slow migration throughput on large datasets

The GorillaDesk REST API enforces rate limits to protect platform stability. When FlitStack receives an HTTP 429 response, it pauses for the number of seconds specified in the rate_reset response header before retrying — a standard exponential-backoff approach. For migrations with 10,000+ customer records, this backoff behavior can extend the migration clock significantly if GorillaDesk's rate limits are low during business hours. FlitStack mitigates this by running export passes during off-peak hours when possible and by batching API calls to minimize total request count. Teams with time-sensitive migration deadlines should coordinate with GorillaDesk support to confirm whether temporary rate-limit increases are available during the migration window.

GorillaDesk invoice and payment data cannot become active billing records in Freshsales

Freshsales has no native invoicing or payment processing module in the base CRM. GorillaDesk invoice line items, payment amounts, transaction IDs from Stripe and Square, and payment status flags have no target object in Freshsales. FlitStack migrates invoice totals, last payment amounts, and payment dates as read-only custom fields on the Freshsales Contact record (Last_Invoice_Amount__c, Last_Invoice_Date__c, Payment_Status__c). These serve as historical billing context for the sales team but cannot trigger Freshsales billing workflows, generate Freshsales quotes, or sync with Freshsales's CPQ module without additional integration. Teams that rely on GorillaDesk invoices for accounts receivable tracking must continue using GorillaDesk for billing or migrate to Freshsales Suite which includes a basic quote and invoice capability.