Migrate from Zoho FSM to Odoo CRM

Zoho FSM Contacts map to Odoo res.partner records where is_company=False. Email, phone, address, and job title map directly. The Zoho FSM contact ID is stored as a custom field (x_studio_fsm_contact_id) for traceability and delta-run de-duplication. During migration, we resolve the primary_company relationship to the parent_id field on the target res.partner, ensuring the contact-to-company hierarchy is preserved in Odoo. Owner resolution occurs via email matching to existing Odoo res.users records.

Zoho FSM Companies map to Odoo res.partner where is_company=True. Company name, website, industry, and annual revenue map to their Odoo counterparts. Parent-company hierarchies in Zoho FSM (if any) map to the Parent PartnerId field in Odoo. The original Zoho FSM company ID is preserved in x_studio_fsm_company_id for reconciliation across migration runs. Industry values from Zoho FSM are matched to res.partner.industry records by name, with any unmapped values flagged for manual resolution.

Odoo CRM has no native asset-tracking module. We create a custom FSM Asset model in Odoo with fields for asset name, serial number, product, location, associated customer (res.partner), site, and the Zoho FSM asset ID for reconciliation. The custom model links to res.partner via a Many2one partner_id field and to product.product via product_id. Asset status values from Zoho FSM are mapped to a custom pick-list (x_studio_asset_status) defined in Odoo Studio before migration loads the data.

Zoho FSM Requests — service tickets or work requests submitted by customers — map to Odoo crm.lead records. Request status (Open, Closed, On Hold) maps to Odoo lead stage. Request priority maps to a custom priority field on the lead.

Zoho FSM Work Orders carry the most complexity: service line items, parts used, service tasks, assigned technician (Crew), and skill requirements. These are split across a custom FSM Work Order model in Odoo and project.task records for task-level breakdown. The original Work Order number is preserved as x_studio_work_order_number.

Individual service tasks inside a Zoho FSM Work Order map to Odoo project.task child records linked to the parent Work Order task. Task name, description, status, and completed flag map directly. Original FSM task ID stored as x_studio_service_task_id. Each child task is linked to the parent x_fsm_work_order record via a Many2one relationship, and the assigned technician is resolved to a res.users record by email matching. Service task status values are mapped to Odoo project.task stage records defined in your Odoo project configuration.

Zoho FSM Estimates — pricing proposals for field service work — map to Odoo sale.order in quotation state. Estimate status (Draft, Sent, Accepted, Lost) maps to sale.order state. The customer-linked contact is resolved to an Odoo res.partner by email match.

Zoho FSM Service Appointments have scheduling data (start/end time, time slot, multi-day flag), assigned technicians, and customer location that has no Odoo native equivalent. We create a custom FSM Appointment model with fields for scheduled_datetime, duration_hours, assigned_technician_id, customer_location, and appointment_status.

Zoho FSM Services and Parts — the catalog of billable line items — map to Odoo product.product records. Service items get type='service', parts get type='product'. Product name, list price, and cost map directly. Zoho FSM product IDs preserved in x_studio_fsm_product_id.

Zoho FSM Skills (technician qualifications) have no Odoo equivalent. We create a custom Many2many field on res.partner (for technician contacts) and on project.task (for Work Order requirements). Skills are stored as a dedicated FSM Skills reference table with the Zoho FSM Skill ID preserved.

Zoho FSM Crews group field agents for dispatch. Odoo has no native Crew equivalent. We map Crews to Odoo res.users records grouped by a custom FSM Crew field, or to a custom Crew model linked to res.users — your admin chooses the structure based on how dispatch is managed in Odoo.

Zoho FSM Timesheets track hours worked per service appointment and technician. These map to Odoo account.analytic.line for time-tracking against project tasks. Billable flag and cost-per-hour from Zoho FSM migrate as custom fields on the analytic line since Odoo's native analytic lines store unit amount but not billing rate.

Files attached to Work Orders, Service Appointments, or Assets in Zoho FSM are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding custom FSM model. File size limits (default 25MB per file in Odoo) are respected during re-upload.