Migrate from Odoo Field Service to Pipedrive

Odoo res.partner records with type='contact' map directly to Pipedrive Person records. The name, email, phone, and address fields align by field name. Partner records that are companies map to Organization records instead; contacts attached to a company link via the Person-Organization relationship.

Odoo res.partner records with type='company' map to Pipedrive Organizations. Company name, domain (website), industry, address, phone, and email fields translate directly by field name alignment. Child companies (commercial partner relationships) map to Pipedrive's related organization link feature, preserving the corporate hierarchy in the CRM.

Odoo's crm.lead records (sales leads not tied to field service) and standalone project.task records that represent pre-service prospects map to Pipedrive Leads. Odoo lead stage values map to Pipedrive Lead status values via a value-mapping table defined in the migration plan.

Odoo fsm.task is the primary migration challenge — Pipedrive has no native field-service object. We map each fsm.task to a Pipedrive Deal, using custom fields (Task_State__c, Assigned_Worker__c, Service_Location__c, Scheduled_Date__c) to carry task metadata that normally lives in Odoo's task record. The Deal's person link points to the Odoo res.partner customer on the task.

Odoo fsm.task.stage values (New, Assigned, In Progress, Testing, Done, Cancelled) map to a dedicated Pipedrive pipeline with matching stage names. Stage-order and probability weights are re-applied in Pipedrive's pipeline settings post-migration. A separate 'Service Jobs' pipeline keeps field-service deals distinct from sales Deals.

Odoo projects group related field-service tasks. In Pipedrive, there is no project equivalent — multiple fsm.tasks belonging to the same project.map to Deals sharing a Project_Name__c custom field value. If your team needs project-level rollup reporting, we create a custom grouping dashboard in Pipedrive's reporting layer using this field.

Odoo timesheet lines (account.analytic.line) store hours per task per user. Because Pipedrive has no per-user timesheet object, we aggregate hours per fsm.task and store the total as a custom numeric field (Timesheet_Hours__c) on the corresponding Deal. Individual user-hour detail is preserved in a migration reference table for manual entry if needed.

Odoo products linked to field-service tasks map to Pipedrive Products linked to Deals. However, Pipedrive Products lack lot/serial number tracking and Bill of Materials — we store the Odoo product name and qty_delivered in a custom text field on the Deal line item. Full inventory traceability requires an external inventory system.

Odoo Chatter messages on fsm.task records migrate as Pipedrive Activity notes on the corresponding Deal. Internal-only messages (private on Odoo) cannot be made private in Pipedrive — we flag these during the sample migration and let your team decide whether to include them or exclude them from the migration scope.

Odoo res.users records for field technicians and owners are matched by email address against Pipedrive Users. Active users with matching emails map directly; unmatched users are flagged before migration so your Pipedrive admin can invite them to join or assign their deals to a designated fallback owner.

Odoo lot/serial numbers tracked on field-service tasks have no Pipedrive equivalent. We preserve the lot number as Lot_Number__c text on the Deal line item for reference, but Pipedrive cannot enforce lot-level inventory controls or maintain which serial numbers were serviced during each visit — this data is informational only and requires an external inventory management system for traceability.

Odoo file attachments on fsm.task records (photos, signed forms, reports) migrate as file attachments on the corresponding Pipedrive Deal. Files are downloaded from Odoo's attachment storage and re-uploaded to Pipedrive. Size limits apply — files over 100MB per attachment are noted for manual handling.