Migrate from Field Service Trakker to Odoo CRM

Field Service Trakker customer records map to Odoo res.partner with partner_type='contact' for individual customers and partner_type='company' for organizations. Primary contact email and phone migrate to email and phone fields on res.partner. Multi-location customers create child-partner records linked via parent_id. Additional address fields such as street, city, state, zip, and country map to res.partner, and parent_id links each location-specific child to the organization partner.

Field Service Trakker contact records attached to a customer merge into res.partner as child-partner records under the company partner. Email, phone, mobile, and title fields map directly. FST contact roles (Billing Contact, Site Contact) preserved as a custom selection field on the child partner.

Work orders become Odoo crm.lead records with type='opportunity'. The work order number maps to x_studio_work_order_number, service type to x_studio_service_type, and priority to crm.lead priority selection. Original create date preserved in x_studio_original_create_date for historical reporting. The work order description maps to crm.lead description, and FST status values map to Odoo stage records with Completed setting pipeline_won=True. Work-order fields become x_studio_* fields on crm.lead via ir.model.fields, and values are written during migration.

When Odoo Sales app is active, work order line items migrate as sale.order.line records with origin pointing to the crm.lead. Product/service description, quantity, and unit price map to sale.order.line name, product_uom_qty, and price_unit. If Sales app is inactive, line items store as a serialized text field on the crm.lead.

Field Service Trakker technician profiles map to hr.employee records linked to res.users. The user record provides login credentials for Odoo mobile app access. FST skill certifications migrate as many2many tags on hr.employee using Odoo's Skills app or a custom x_studio_skills field.

Scheduled appointments from Field Service Trakker become Odoo crm.activity records with activity_type_id, user_id (assigned technician), and date_deadline matching the original start datetime. If the Odoo Calendar app is active, calendar.event records generate with res_model='crm.lead' linking back to the work-order lead.

When Odoo Accounting is active, Field Service Trakker invoices map to account.move with move_type='out_invoice'. Line items from the invoice migrate to invoice_line_ids matching product, quantity, and price_unit. Payment state (paid, outstanding) translates to Odoo's payment_state field on account.move. The activity type defaults to 'Call' unless a specific type is indicated in the source data.

Parts consumed on work orders migrate to a custom x_studio_parts_used field on crm.lead as serialized JSON (part name, quantity, cost). When Odoo Inventory app is active, stock.move records generate with stock_picking_id linking to the work-order opportunity via origin reference. The JSON stores each part as an object with 'name', 'qty', and 'cost', allowing usage reports per lead. If Inventory is absent, the field stays available for later integration.

Field Service Trakker site records map to partner addresses on the customer res.partner. Street, city, state, zip, and country map to Odoo's address fields (street, street2, city, state_id, zip, country_id). Multiple sites per customer create additional contact records with address_type='other'.

Field Service Trakker custom fields on work orders (e.g., txt_equipment_model, num_hourly_rate) create Odoo custom fields via ir.model.fields with field_type matching the source type (char, float, datetime). Selection fields map to Odoo selection fields with identical option values. Required field constraints are set based on FST field settings.

Service history notes and technician comments from Field Service Trakker migrate as mail.message records on the crm.lead with message_type='comment'. Author field set to the mapped technician's res.users record. Create_date preserves the original note timestamp for audit continuity. The mail.message records are attached to the crm.lead's mail.thread, and file attachments are linked via ir.attachment with res_model='crm.lead' and res_id pointing to the lead, preserving the full audit trail.

Work order photos and file attachments download from FST and re-upload to Odoo's ir.attachment with res_model='crm.lead' and res_id pointing to the migrated lead. Inline images in service notes become mail.message attachments with the same res_model reference. The migration script downloads a file, checks its MIME type, and stores it in ir.attachment with db_datas. For images in notes, it extracts base64 data and attaches it as mail.message linked to the lead.