Migrate from Mobile Service App to Zoho CRM

Mobile Service App Jobs map directly to Zoho CRM Deals. The Job body (name, description, scheduled start/end, actual start/end) maps to the Deal name and standard close date fields. Mobile Service App job status (Pending, In Progress, Completed, On Hold, Cancelled) requires a custom pick-list field (Job_Status__c) on Zoho Deals since Zoho's native Opportunity Stage has a different taxonomy focused on sales cycle stages rather than job lifecycle states.

Mobile Service App priority levels (Low, Normal, High, Urgent) have no native equivalent in Zoho CRM. We migrate priority as a custom pick-list field (Job_Priority__c) on the Deal module. Priority values are mapped one-for-one with the original Mobile Service App display label preserved. If your team uses custom priority labels, we add them to the pick-list definition before migration so the field is ready on Day 1.

Service type values such as Installation, Repair, Maintenance, Inspection, and Emergency map to a custom pick-list field (Service_Type__c) on the Zoho Deal module. These values are specific to field-service operations and Zoho CRM's standard product or industry taxonomy does not cover them. We extract the distinct service type values from Mobile Service App, define the pick-list in Zoho before migration, and populate the field for every Job record that becomes a Deal.

Mobile Service App Customers map directly to Zoho CRM Accounts. The Account Name, phone, email, billing address, and industry classification carry over as standard Zoho Account fields. Mobile Service App customer records that contain both a company entity and a primary contact will generate an Account record plus a related Contact record, with the Contact linked via the Account Lookup field (Account Name) on the Contact module.

The primary contact stored on a Mobile Service App Customer record maps to a Zoho CRM Contact linked to the corresponding Account. Name, email, phone, job title, and department transfer as standard Contact fields. If the Mobile Service App record holds multiple contact points, additional contacts are created as separate Contact records and all are associated to the same Account. Mobile Service App contact notes and communication history are preserved as Contact-level Notes.

Mobile Service App workers can be mapped to Zoho CRM Users if they need full CRM access, or to Contacts if they should appear on Deal records as assignees without a Zoho seat. Resolution is by email match against Zoho users. Workers with no matching Zoho user are flagged before migration and assigned to a fallback owner or created as Contacts. Multi-worker job assignments require a primary worker in the Deal Owner or Assigned_To lookup, with additional workers stored as a custom multi-text or look-up field (Secondary_Workers__c).

Mobile Service App job site address maps to the Address compound fields on the Zoho Account (Street, City, State, Zip, Country). Job site coordinates (latitude and longitude) are stored as custom Number fields (Site_Latitude__c, Site_Longitude__c) since Zoho CRM has no native geolocation type. Zoho CRM mobile app can render these coordinates on a map via custom widgets or Zoho Flow integrations with mapping services. Site name and location notes transfer as text custom fields on the Account.

Job photos, signatures, and uploaded documents in Mobile Service App are downloaded from the source and re-uploaded as Zoho CRM Attachments on the corresponding Deal record. Zoho CRM supports file uploads up to the storage limit of your plan (25 MB per file on most tiers). Photos embedded in Mobile Service App notes are extracted, saved as separate files, and attached to the Deal. Inline images from rich-text note fields are downloaded and re-hosted as file attachments.

Mobile Service App job notes migrate to Zoho CRM Notes attached to the corresponding Deal. The note body, original author, and creation timestamp are preserved. Notes are linked to the Deal by the native Notes lookup. If Mobile Service App notes contain structured data (checklist items, before/after fields), the raw text transfers and any structured parsing is documented in the migration plan for manual re-entry or Zoho Creator form rebuild.

Any custom fields defined on Mobile Service App Jobs that do not have a Zoho CRM native equivalent are created as custom fields on the Deal module before migration. We extract the full Mobile Service App custom field schema (field label, data type, pick-list values), map data types to their nearest Zoho equivalent (text, number, date, pick-list, multi-select), and deliver a pre-migration Zoho custom field setup checklist so your admin can create the fields before the data loads.

If Mobile Service App records job status transitions with timestamps and the identity of the worker who changed status, we preserve this as a custom text area field (Status_Change_Log__c) on the Deal. Zoho CRM's native field-history tracking can be enabled on custom fields post-migration for ongoing change auditing. Historical transitions are stored as a concatenated log string for reporting continuity rather than individual child records.