Migrate from Odoo Field Service to Zoho CRM

Odoo res.partner records (customers, vendors, and individuals) map directly to Zoho CRM Contacts. Address fields transfer as structured multi-line address fields. Partners marked as company=True in Odoo can alternatively map to Accounts based on your Zoho configuration preference. If Odoo partners have multiple address records (e.g., invoice and delivery), each address can be represented as a separate subform on the Zoho Contact, preserving all address variations.

Odoo res.company records representing business entities map to Zoho CRM Accounts. The company logo stored as an attachment migrates to Zoho CRM Notes or to the Account Image field for visual identification. In multi-company Odoo setups, each company must map to a separate Zoho CRM account, with ownership assigned to the corresponding Zoho user or team to maintain proper data isolation and reporting.

Odoo field service tasks with their state lifecycle (Unconfirmed, Confirmed, In Progress, Pending, Done, Cancelled) map to Zoho CRM Tasks. Task states require custom pick-list fields since Zoho's native Status does not replicate Odoo's six-state model. Original state history preserved in a custom datetime audit trail per task.

Odoo service orders (field.service.order) containing multiple tasks, line items, and pricing do not have a direct Zoho CRM equivalent. We create a custom Service_Order module with lookup to Contact/Account, subforms for task items, and custom fields for order totals and tax information.

Odoo field.service.location records store service site addresses, contact persons at the site, and navigation coordinates. These data merge into the Account address fields for site-level records, while the GPS latitude and longitude are stored in custom Latitude__c and Longitude__c fields on the Account. Site-specific contact details are preserved as a custom subform on the Account record, allowing multiple contacts per location.

Odoo equipment records with serial numbers, maintenance history, and meter readings require a custom Equipment module in Zoho CRM. Equipment links to Account (customer site) via lookup field. Maintenance history and meter readings migrate as subform records with datetime and numeric fields.

Odoo product.product records (parts, service items, and consumables used in field service tasks) map to Zoho CRM Products. The product name, SKU, description, and list price transfer directly. Because Zoho Products lack a type taxonomy matching Odoo's service/stockable/consumable distinction, the product type migrates as a custom pick-list field. If the Odoo product includes an image, we attach it as a Zoho CRM file to the product record, preserving visual reference.

Odoo field.service.team groups technicians by territory or skill set. These map to Zoho CRM Users via email match, with the team relationship preserved as a custom lookup field (Service_Team__c) on the User record. If a technician belongs to multiple teams, each team assignment is recorded as a separate lookup entry. Unmatched technicians are flagged during migration and assigned to a fallback owner until their Zoho user accounts are provisioned.

Odoo field service worksheets (digital forms filled by technicians on-site) migrate as Zoho CRM Notes attached to the parent Task record. Worksheet PDF or HTML content converts to Note body text. Binary attachments re-upload as Zoho CRM file attachments up to 25MB each.

Odoo time slots for scheduling field visits map to Zoho CRM Events. The start and end datetime fields align, while the slot type (Morning, Afternoon, Evening) migrates as a pick-list field on the Event record. If the Odoo slot includes a location or a linked contact, we map those to the Event's location field and the Who_Id lookup. Recurring slot patterns are translated into Zoho CRM Event series when supported.

Odoo order line items with product, quantity, unit price, and tax need a custom subform on the Service Order module. Each line links to the Zoho Product record, preserving the original Odoo product SKU. Lines are sequenced by display_order to maintain the original ordering. Discount fields map to Zoho custom percent fields with rounding rules applied, and tax amounts are stored in a custom currency field to preserve multi-currency information.

Odoo ir.attachment records linked to tasks, partners, or equipment are downloaded and re-uploaded to Zoho CRM as file attachments. Each attachment inherits the original file name and the creation timestamp. Zoho's 25 MB per-file limit is enforced; files exceeding this size are flagged for compression or storage. Inline images embedded in rich-text fields are extracted and stored as separate attachments linked to the parent record, ensuring all visual content is preserved.

Odoo task timer logs recording start time, end time, and technician duration per work session migrate as a custom Time_Logs subform on the Task record in Zoho CRM. Duration in seconds converts to hours:minutes format. Billing-eligible time flags preserve as boolean field.