Migrate from MobileWorker to Zoho CRM

Zoho's API credit budget governs migration throughput and can throttle large imports

Zoho CRM allocates API credits on a rolling 24-hour window: base 50,000 plus 250 per Standard user, 500 per Professional user, or 2,000 per Enterprise/Ultimate user. A Bulk Write Initialize consumes 500 credits per job, and upsert operations deduct 1 credit per 10 records. For a migration carrying 50,000 work orders with attachments, this means a Standard-tier org (10 users = 52,500 credits) may need to pace the migration across multiple 24-hour windows or request temporary credit top-ups. FlitStack AI monitors X-API-CREDITS-REMAINING headers and pauses ingestion when the threshold drops below 20% to avoid HTTP 429 errors that would corrupt in-flight batches.

MobileWorker GIS coordinates have no native Zoho CRM field type — custom decimal fields are required

MobileWorker stores X/Y coordinates on every work order and assignment. Zoho CRM has no built-in latitude/longitude field type; the platform expects address strings for its native Maps integration. Migrating coordinates requires creating Latitude__c and Longitude__c custom decimal fields on the Deal module manually before data lands. If these fields are missing, FlitStack AI logs a pre-flight error and halts the migration until the custom fields are created. The address string from MobileWorker is preserved in a separate Street_Address__c custom field to support Zoho Maps address lookup post-migration.

Zoho's 25MB per-file attachment limit may truncate legacy photo archives

MobileWorker field crews frequently attach photos and PDF inspection reports to work orders. Zoho CRM enforces a 25MB per-file ceiling on attachments. Photos taken at high resolution on modern smartphones regularly exceed this. FlitStack AI detects files above 20MB during the pre-flight audit, splits multi-image attachments into individual records, and flags PDFs exceeding the limit for manual download-link storage in a URL custom field. Teams with extensive historical photo archives should budget time for this review before the migration window.

Assignment chaining in MobileWorker requires decomposition into parent-child Task hierarchies

MobileWorker allows sequential assignment chains — one assignment triggers the next based on completion. Zoho Tasks support Sub-Tasks but not automated sequential chaining natively. FlitStack AI flattens assignment chains into sibling Tasks linked to the same Deal (What_ID) and preserves the sequence order in a Sequence_Order__c integer field. Zoho Blueprint conditions can then reference Sequence_Order__c to gate the next Task's status-change trigger, but this requires manual Blueprint configuration by your Zoho admin post-migration.

Territory and dispatch rules cannot be migrated — they become Blueprint conditions

MobileWorker's most field-specific logic lives in its dispatch rules: territory-based routing, skill-matching, and load-balancing. Zoho CRM has no equivalent native dispatch engine — territory management requires Zoho FSM (Field Service Management) or custom Deluge functions. FlitStack AI exports the source dispatch rule definitions as a structured JSON reference document and creates a Territory__c pick-list on Deals and Contacts. Your Zoho admin uses the reference document to configure Blueprint conditions or Zoho FSM routing rules after go-live.