Migrate from Oracle Field Service Cloud to Zoho CRM

Oracle Field Service Cloud activities (installation, repair, maintenance, inspection) map to Zoho Tasks when they represent a to-do item with status tracking. Meeting-type activities with a scheduled start and end time map to Zoho Events. The Oracle activity type field becomes a Zoho Task.Subject prefix or Event type indicator. Original start and end timestamps migrate with full precision.

Oracle activity statuses (Pending, In Progress, Completed, Cancelled, Not Done) map value-by-value to Zoho task status pick-list values (Not Started, In Progress, Completed, Cancelled). Each Oracle status code is explicitly mapped to its Zoho equivalent. Status transition timestamps from Oracle are preserved as custom datetime fields on the Zoho Task record.

Oracle work orders that carry revenue data (service fees, parts charges, contract billable amounts) map to Zoho Deals. The Oracle work order number becomes the Deal name or a custom field (OFSC_Work_Order_ID__c). Work order status and priority map to custom pick-list fields on the Deal. Revenue amounts from Oracle line items aggregate into the Deal amount field.

Oracle work orders that do not carry revenue data (internal service tasks, preventive maintenance without billing) map to Zoho Tasks. These tasks link to the Zoho Account representing the service location and carry the Oracle work order ID as a reference field. Work order description and notes migrate as task description text.

Oracle Field Service Cloud locations represent service sites — customer addresses with associated assets and inventory pools. Each location maps to a Zoho Account with the location name as Account Name, the full postal address migrated to Zoho's Street, City, State, and Zip fields. Geographic coordinates (latitude/longitude) from Oracle are preserved as custom number fields for mapping integration.

Oracle assets attached to a location (equipment, installed base items) migrate as Zoho Product records or a custom Assets module depending on whether the migration includes full equipment lifecycle data. Asset serial numbers, model numbers, and install dates migrate to custom fields. Asset status (Active, Under Repair, Retired) requires a custom pick-list field in Zoho.

Oracle Field Service Cloud resources (technicians, vehicles, crews) are mapped to Zoho CRM Users by email address lookup. Unmatched resources are flagged before migration — your team either creates Zoho user accounts first or assigns records to a fallback owner. Skills, certifications, and capacity data from Oracle Resource profiles migrate as custom fields on the Zoho User record.

Oracle activity-to-resource assignments (which technician is assigned to which activity at what time) map directly to Zoho Task.Assigned_To and Event.Owner fields. The mapping uses the resource email resolution established in the User mapping step, ensuring the correct Zoho user receives the migrated activity in their queue.

Oracle inventory pools tracking parts at locations migrate as Zoho Product records linked to the corresponding Zoho Account. Bin locations, reorder points, and quantities on hand become custom fields on the Product. Full Zoho Inventory module activation is recommended if serial number tracking is required — this requires a separate configuration step not included in the base migration.

Oracle routes (ordered sequences of activities assigned to a resource for a given day) are reconstructed in Zoho as Event records representing the scheduled day or as a custom Routes module if your team relies on route-level reporting. The route name, date, and ordered activity list become custom fields on the Zoho record. Route optimization rules do not migrate — they must be rebuilt using Zoho's scheduling logic.

Oracle business rules and SLA timers enforcing step sequences and response deadlines have no Zoho CRM equivalent at the activity level. These must be rebuilt in Zoho Workflow Rules (for field updates and email alerts) and Blueprint stages (for process enforcement). We export Oracle rule definitions as JSON for your Zoho admin to use as a rebuild reference.

Oracle routing configurations (geographic zones, skill-based assignment rules, capacity constraints) are scheduling engine settings that do not translate to Zoho CRM's data model. Service territory and routing logic must be rebuilt using Zoho's Territory management and custom workflow criteria. We preserve the routing configuration as an exported reference file.

Oracle activity attachments, work order documents, and asset images are downloaded and re-uploaded to Zoho CRM Attachments linked to the corresponding Deal, Task, or Account record. File size limits apply (Zoho supports files up to 50MB per attachment). Inline images in Oracle notes are extracted and re-hosted as Zoho Attachment records.