Migrate from Comarch Field Service Management to Odoo CRM

Comarch work orders map directly to Odoo project.task records. The task name becomes task title, work order description maps to task description, priority maps to Odoo priority (1–4 stars), and status maps to kanban stage. Parent/child work order hierarchies become subtasks in Odoo using project.subtask or nested task structure.

Work orders representing customer-initiated service requests that have not yet been dispatched map to Odoo crm.lead as leads, preserving the originating contact and service-type classification. This split mapping keeps pre-dispatch work order requests in the CRM pipeline for opportunity tracking. Once dispatched, the crm.lead converts to a project.task representing the scheduled job.

Comarch customer accounts map to Odoo res.partner records. The primary service address becomes partner address fields. Billing address, if separate, is stored as a second partner contact with type='invoice'. Customer tier/SLA classification migrates as a custom selection field on the partner record.

Comarch contact persons associated with customer accounts map to res.partner records linked to the parent customer account partner record. Email, phone, mobile, and job title fields map directly to corresponding Odoo partner fields. The primary contact flag is preserved, and additional contacts receive type='contact' with appropriate subtype tagging for categorization.

Comarch asset registry entries map to Odoo stock.lot records when tracking serialized or lot-controlled equipment, linked to the customer partner. Asset metadata (make, model, serial number, install date, warranty expiry) map to lot fields or custom fields. Equipment catalog entries without serial tracking map to product.product records.

Comarch technicians map to Odoo res.users records with user type set to internal user. Availability calendar (working hours, off-days) maps to resource.calendar entries. Skill certifications and certification expiry dates stored as custom fields on the user record. Unmatched technicians flagged for team assignment before migration.

Comarch work order parts-consumption lines map to Odoo stock.move records linked to the project.task. Quantity consumed and product reference preserved. If Odoo Manufacturing module is active, mrp.unbuild records track teardown operations; otherwise, stock moves against internal location represent parts usage.

Comarch technician time entries against work orders map to Odoo account.analytic.line records linked to the project.task and the assigned user. Hours, date, and description preserved. Time entries used for billing map to Odoo sale.order.line or invoice lines if invoicing module is active.

Comarch service location addresses map to address fields on the res.partner record. Geo-coordinates (latitude/longitude) stored as custom decimal fields if Odoo GIS modules are active; otherwise preserved as text for reference. Location-specific notes map to partner street2 or a custom field.

Comarch SLA configurations (response time, resolution time, priority escalation rules) map to a custom SLA field on project.task plus Odoo sale.subscription records if service contracts exist. Odoo does not have native FSM-specific SLA enforcement; this is handled via business rules post-migration.

Comarch work order status-change history and internal notes map to Odoo mail.message records attached to the project.task, preserving original timestamps and actor (technician or dispatcher) for audit trail continuity. Customer-visible communications map to Odoo chatters on the related res.partner contact record for unified customer communication history.

Comarch user-defined fields on work orders, assets, or accounts map to custom fields created in Odoo via Settings > Technical > Models. Field type translation follows: text fields to char, numeric values to float or integer, dates to date, and pick-lists to selection fields. All custom fields are created in Odoo before migration data lands so the target schema is ready for import operations.