Migrate your Odoo Field Service data

Tasks are the primary FSM object in Odoo. They contain stage, worker, location, scheduled dates, and chatter. We export via read() on fsm.order and import via create()/write() XML-RPC calls. Recurring tasks carry a recurring_id reference that we preserve as a custom field on the target system.

Workers are stored as res.partner records with a person flag. The worker's skills, certifications, and territories are stored in related fsm.worker and fsm.tag models. We map the partner record and also pull related fsm.worker fields to reconstruct the full worker profile in the destination.

Field service locations are res.partner records with address data plus geometry (geo_localize fields). We export the partner address fields and geo coordinates separately, then reconstruct the location record in the target system using the destination's address object model.

Odoo FSM tasks are linked to project.project records for grouping and reporting. We include the parent project record in every migration scope so stage pipelines and project-level timesheets remain consistent after import.

Stages are stored in project.task.type and referenced on fsm.order via stage_id. We preserve the stage order, name, and fold status. Custom stage colors or legends stored in ir.model.data are flagged as mapping items requiring manual re-creation in the destination.

Time entries logged against FSM tasks are stored in account.analytic.line linked by task_id. We export the date, duration, employee, and description. Billingable flag and cost/price fields require explicit mapping to the destination's time tracking object.

Worksheets are custom form templates attached to fsm.order via x_models / ir.model.data. The template structure varies by installation. We export the worksheet template and the filled values as JSON blobs, landing them as structured fields or notes in the destination depending on target schema.

Spare parts and materials used on tasks reference product.product records. We export name, default_code, uom, and list_price. BoM-linked products require a separate product.boM export to preserve bill of materials relationships in the destination.

Task attachments (signatures, photos, PDFs) are stored in ir.attachment with a res_model of fsm.order. We export the attachment name, datas (base64), and create_date. Large binary attachments are chunked and uploaded via the destination's attachment API or stored as downloadable URLs.

Custom fields created via Settings > Technical > Fields use ir.model.fields and store their values in x_name columns in the base table. We detect these columns during the schema audit and include them as explicit mapped fields with their declared field type.

Task chatter is stored in mail.message linked to fsm.order via res_id. Chatter includes internal notes, emails, and customer-facing messages. We export the body, author, and create_date. Rich-text content may require HTML sanitization depending on the destination's message format.

Customer and worker contacts live in the shared res.partner model. FSM-specific fields (customer_rank, supplier_rank, is_fsm_location) are exported alongside standard address and contact fields. Where a contact has both a CRM role and an FSM role, we preserve both role flags.