Migrate from Odoo Field Service to Freshsales

Odoo res.partner records (customers and companies combined) split into Freshsales Account (company-level data) and Contact (individual person). When partner_id has child contacts in Odoo, those become separate Freshsales Contact records linked to the same Account via Account Contact Relationships, preserving the hierarchical structure and ensuring all related contacts are accessible from the parent Account record.

fsm.order task records map to Freshsales Deal (Opportunity) for the commercial dimension and to Task records for the activity log. Deal.Amount pulls from fsm_order.total_amount_revenue_line_ids; Task records preserve the fsm_order.description, stage history, and technician assignments as activity notes, maintaining complete audit trail of all field service activities and their financial impact.

fsm.location site records map to Freshsales Account with address fields populated from location.street, location.city, location.zip. GPS coordinates (location.partner_latitude, location.partner_longitude) migrate to custom number fields on the Account. The location.contact_id partner link resolves to a Contact record first, ensuring accurate assignment and preventing orphaned location data in the target system.

Odoo fsm_worker records link to res_users for login credentials. The worker.partner_id res.partner becomes a Freshsales Contact record. Worker skills (worker.skill_ids) and team assignments (worker.team_id) migrate as custom pick-list and multi-select fields on the Contact so the technician profile is preserved.

Odoo fsm_stage.name values map to Freshsales Deal StageName via value-by-value mapping. Stage sequence (stage.sequence) determines the order in Freshsales pipeline. If fsm_stage.fold is True, the stage is marked as Closed/Won or Closed/Lost in Freshsales based on business rules defined during scoping.

Odoo project.project records linked to fsm_order map to Freshsales custom fields on the Deal — specifically Project_Name__c (text) and Project_ID__c (text) capture the source project reference. Project.task_count migrates as an integer custom field for reporting continuity, allowing teams to track project-related metrics and maintain visibility into field service operations tied to specific projects.

Odoo project_task records linked to fsm_order migrate as Freshsales Task records. Task.name maps to Task.Subject, task.description to Task.Description, task.stage_id.name to Task.Status. Parent task hierarchy is not preserved natively in Freshsales — FlitStack captures it as a custom text field (Parent_Task_Reference__c) for manual reconstruction.

Timesheet entries (project_timesheet with line_id linking to fsm_order) migrate as Freshsales Tasks with Type='Time Entry'. The timesheet.hours value populates a custom Hours_Logged__c number field; timesheet.date becomes the Task.ActivityDate. Original user_id resolves to Freshsales User by email match, ensuring accurate assignment of time entries to the correct technician in the target system.

Odoo ir_attachment records on fsm_order, project_task, and res_partner migrate as Freshsales Files attached to the corresponding Deal, Task, or Contact. File size limits of 25MB per file apply; files exceeding this threshold are flagged for chunked re-upload or alternative delivery.

Odoo invoices (account_move) linked to fsm_order are not replicated as Freshsales billing records (Freshsales manages deals, not accounting). Instead, account_move.name and account_move.amount_total migrate as custom text and currency fields on the related Deal — Invoice_Number__c and Invoice_Total__c — preserving the financial reference.

Odoo res_users records map to Freshsales Users by email address match. Active status (res_users.active=True) determines Freshsales User status. Unmatched users are flagged before migration — teams either invite them to Freshsales or assign their records to a fallback owner, ensuring no data is lost due to missing user accounts in the target system.

Odoo fsm_order.priority selection field (very high/high/normal/low/very low) maps to Freshsales custom pick-list Deal_Priority__c with the same values. Stage-entered timestamps from fsm_order.stage_date are preserved as custom datetime fields for reporting continuity, allowing teams to analyze response times and prioritize follow-up activities based on original service level commitments.

SLA deadline (fsm_order.sla_deadline datetime) migrates to Freshsales custom datetime field SLA_Deadline__c on the Deal. Odoo SLA map configuration is not transferable — this field preserves the reference date for Freshsales-side workflow triggers, enabling teams to set up automated reminders and escalations based on original service level agreements established in Odoo.