Migrate from Mobile Worker to Zoho CRM

Mobile Worker records are the primary person entity; they map to Zoho Contacts with a Technician__c checkbox field added to distinguish field workers from sales contacts. Each Worker's system ID is stored as Source_System_ID__c for delta-run de-duplication. FlitStack validates email uniqueness before insertion to prevent duplicate Contact creation during incremental migration runs.

Mobile Worker captures GPS latitude and longitude per worker. These translate to Location_Lat__c (decimal, 10,6) and Location_Long__c (decimal, 10,6) custom fields on the Contact record. A Last_Location_Updated__c custom datetime field preserves the original capture timestamp. The precision accommodates sub-meter location accuracy requirements common in field service operations and route-efficiency reporting.

Active and historical work orders map to Zoho Tasks by default. If the Mobile Worker setup includes custom fields beyond standard Task columns, FlitStack recommends creating a custom Work_Orders module to hold those attributes as subform records linked back to the parent Contact.

Mobile Worker status values (Pending, In Progress, On Hold, Completed, Cancelled) map to Zoho Task status values (Not Started, In Progress, Completed) with a custom pick-list field preserving the original sub-status for reporting continuity. This mapping ensures historical status trends remain analyzable after migration, preventing data loss for operational reporting and performance dashboards.

A single Mobile Worker assignment carries both a scheduled window (start/end time) and a task description. FlitStack splits this into a Zoho Task for the work description and a Zoho Event for the scheduled window, both linked to the same Contact owner.

If Mobile Worker stores client site records, those map to Zoho Accounts with the site address stored in the Account's mailing address fields. Parent-account hierarchies from Mobile Worker map to Zoho ParentId. Multi-site clients with multiple locations in Mobile Worker become multiple Account records linked to a parent Zoho Account for hierarchical reporting and consolidated account views.

Technician skill certifications stored as custom fields on the Contact record (e.g., HVAC_Certified__c checkbox, License_Number__c text). For multi-certification lists, a custom pick-list field or Tags on the Contact stores the full skill roster. This approach enables skill-based Task assignment using Zoho CRM filters without requiring custom Deluge scripts.

Photos, PDFs, and signature captures attached to Mobile Worker work orders re-upload to the corresponding Zoho Task or custom module record as CRM Attachments. File size is capped at Zoho's 25MB per attachment limit. For files exceeding this threshold, FlitStack stores a reference URL to the original file location and notifies the admin to manually archive the oversized asset.

Clock-in/clock-out records from Mobile Worker become a Time_Worked_Minutes__c integer field and a Time_Entries_JSON__c text field (for detailed line items) on the Zoho Task. Original timestamps are preserved as audit data. This preserves billable hour calculations and supports compliance audits requiring granular time tracking records across technician payroll cycles.

Free-text service notes stored in Mobile Worker map to Zoho Task Comments linked to the parent Task record. Rich-text formatting is stripped to plain text to comply with Zoho's Notes module formatting rules. Images embedded in Mobile Worker notes are downloaded separately and reattached as CRM Attachments linked to the Task for complete service history preservation.