Migrate from Dispatch to Zoho CRM

Dispatch field-service Jobs have no native Zoho CRM equivalent — mapping requires custom Task fields

Zoho CRM does not have a field-service Job or Work Order module out of the box. Dispatch Jobs must map to Tasks with a set of custom fields (Service_Type__c, Work_Order_Number__c, Dispatch_Status__c, Dispatch_Scheduled_Date__c, Source_Job_ID__c) to preserve the service context. Without these custom fields, Job metadata like priority level, work order reference, and service category would be lost. FlitStack AI creates these custom fields on the Task module during schema setup and maps all relevant Dispatch Job properties into them. If Zoho CRM Professional or higher is not the target edition, Blueprint automation also needs to be factored into the rebuild plan.

Dispatch Location latitude/longitude has no native Zoho CRM storage — geo-data must be custom fields

Zoho CRM Account and Contact records do not have native latitude and longitude fields. Dispatch Locations with geo-coordinates for routing and proximity queries will lose that spatial data if not stored in custom decimal fields. FlitStack AI creates Dispatch_Latitude__c and Dispatch_Longitude__c on the Account module and populates them from Dispatch Location records. Teams that rely on geo-based routing in Dispatch will need to rebuild that logic using Zoho CRM's custom functions and Deluge scripting or a third-party mapping integration — this is not handled by the data migration itself.

Zoho CRM API credit limits vary by edition — bulk migration pace must respect tier limits

Zoho CRM API credit consumption varies by edition: Standard allows 500 requests per minute, Professional allows 2,500 per minute, and Enterprise allows 10,000 per minute. FlitStack AI paces bulk imports to stay within the active edition's limits, but migrations against a Standard-tier Zoho CRM instance will run significantly slower than against Enterprise. API credits also reset on a 24-hour rolling window, so large datasets may require multiple batch windows. We surface the target Zoho CRM edition before migration runs so the import schedule accounts for throttling.

Dispatch Invoices have no direct Zoho CRM equivalent — financial data requires separate migration

Dispatch Invoices (amount, date, status, line items) do not map to any standard Zoho CRM object. The closest Zoho CRM constructs are Quotes and Sales Orders, but those are tied to the sales pipeline, not field-service billing. FlitStack AI preserves Dispatch Invoice data as a custom module (Dispatch_Invoice__c) linked to Account records — this gives teams a reference record for historical billing. For teams actively using Zoho Books, a separate Zoho Books migration (not covered by the standard Dispatch-to-Zoho CRM migration) is the proper path for live financial data continuity.

Dispatch scheduling algorithms and optimization rules do not migrate

Dispatch uses routing and optimization algorithms tied to technician availability, geographic clustering, and time-window constraints. Zoho CRM has no native field-dispatch scheduling engine — scheduling logic must be rebuilt from scratch using Zoho CRM Workflows, Blueprint stages, and potentially custom Deluge functions. FlitStack AI exports Dispatch scheduling rules and technician assignment patterns as a reference document for the Zoho CRM admin, but the migration covers data only. Workflows, sequences, and automation rules in Dispatch are explicitly out of scope.